Hero Chat and a connected AI agent use the same contest groups as the app. Each change goes through the same controls: Hero shows a card that you confirm, and an agent asks before it acts. See What are contest groups.
Plans. Hero Chat is on Essential and Power, with 5 new messages a day on Essential. Saving a playbook from Hero Chat needs Power. AI agents are part of Power.
Before you start
- Open the slate in the workspace, with the entries file uploaded. Hero reads the slate that is open.
- Run a build. See Build for a contest group.
Ask Hero Chat
| Ask | What Hero proposes |
|---|---|
| "Build my cash games on their own." | A New build for Cash card. Confirm opens a new build for Cash, and the build on screen gives Cash up. |
| "Make this build cover Cash and 150-max." | A card that gives the build on screen those groups. Another build that covers one of them gives it up. |
| "Make this build cover every other contest." | A card that gives the build every contest no other build keeps. |
| "Which contests does this build fill?" | No card. Hero reads what each build covers and names the contests outside the build on screen. |
| "Fill my entries." | A Fill entries card for the contests of the build on screen only. |
| "Swap only my cash entries." | A Run late swap on your filled entries in Cash. card. |
| "Create an NFL cash playbook built for Cash." | A Create playbook card with the Built for list. Power plan. |
Nothing changes until you click Confirm. A card that moves a group from another build shows the same message with Undo as the Build for menu. A new build has no lineups, so ask Hero to build it next.
Build advice from Hero reads the contests of the build on screen only. On a build that covers none of your entered contests, Hero says so, and a Fill entries card writes nothing.
Late swap with Hero Chat
When a build of the slate keeps a list of groups, Hero's swap runs in parts, as the Swap sheet does. Each part of a build with a list swaps under that build's settings. The rest swaps under the build on screen when that build keeps no list. Else it swaps under the one build for all other contests, or under Defaults. Each part counts its own Max Exp, Min Exp, and uniqueness.
Until the swap runs, a line on the card names the parts and their settings, for example 2 parts: Cash follows Cash build, All other contests follows 7:42 PM. When you ask for one group, only the entries of that group swap. The other entries stay as they are.
Hero stops before it swaps and changes nothing in these cases:
- "No entered contest is in 20-max. The entered groups are Cash, 150-max. Nothing was swapped." : you named a group you did not enter.
- "No entry in Cash has a slot left to swap. Nothing was swapped." : every entry of that group is locked.
- "DFS Hero could not load this slate's contests, so it cannot tell which contests each build swaps. Nothing was swapped. Try again in a moment." : ask again in a moment.
What a connected AI agent can do
A connected agent works with the same groups and the same rules as the app:
- Read what each of your builds covers, and the groups you entered on a slate.
- Change what a finished build covers: take a group, give one up, or cover every other contest. The entries keep the lineups they hold.
- Run a build for chosen groups on DFS Hero's servers. It fills only those contests, and every other build of the slate gives those groups up.
- Save a playbook with a Built for list, set it as the default for its groups, and run or schedule it.
- Schedule your default playbooks of a slate as one cloud build in parts. The agent never replaces a run you already queued.
- Late swap your entries in parts, or swap one group only.
- Read a cloud build in parts: each part with its status, and the entered contests that no part covered.
See What an agent can do.
Related articles
Was this article helpful?