Summary
The "Sling work" button on the rig page was built before the Mayor existed. It is currently styled as a primary CTA with its own model selector dropdown. Now that the Mayor is the primary way to delegate work, this button teaches users the wrong workflow and has configuration (model selection) that duplicates town-level settings.
Current Problems
- Too prominent — styled as a primary CTA (large button, prominent placement), implying it is the main way to create work. It is not — the Mayor is.
- Has its own model selector — this duplicates the town-level default model setting and can confuse users about which model is actually used. Model selection should be a town-level concern, not a per-sling-action concern.
- No mention of the Mayor — new users see the Sling button and think they need to manually create beads for every task. They miss the fact that they can just chat with the Mayor in natural language.
Proposed Changes
1. Add a Mayor prompt banner
Above or near the sling action, add a contextual hint:
Tip: You can ask the Mayor to do this for you. Just describe what you need in the chat — the Mayor will create beads, manage convoys, and coordinate agents automatically.
This should be dismissible (localStorage flag) so it does not nag repeat users.
2. Demote the button to a secondary/tertiary action
- Change from primary button styling to a secondary or ghost variant
- Consider moving it into a "..." overflow menu or collapsible "Advanced" section
- The button label could change from "Sling work" to something like "Quick sling" or just "New bead"
3. Remove the model selector
The model is determined by the town-level default (townConfig.default_model). Remove the per-sling model dropdown entirely. If the user wants to change the model, they go to Settings.
4. Simplify the form
The sling form should be minimal:
- Title (required)
- Description (optional, expandable)
- Priority dropdown (optional, defaults to medium)
- Submit button
No model selector, no agent selector, no advanced options. Just "what do you want done."
Files
Find the Sling Work button/form component — likely in the rig detail page or rig workbench view under src/app/(app)/gastown/[townId]/ or a shared component. Search for "sling" or "SlingWork" or "CreateBead" in the frontend code.
Acceptance Criteria
Summary
The "Sling work" button on the rig page was built before the Mayor existed. It is currently styled as a primary CTA with its own model selector dropdown. Now that the Mayor is the primary way to delegate work, this button teaches users the wrong workflow and has configuration (model selection) that duplicates town-level settings.
Current Problems
Proposed Changes
1. Add a Mayor prompt banner
Above or near the sling action, add a contextual hint:
This should be dismissible (localStorage flag) so it does not nag repeat users.
2. Demote the button to a secondary/tertiary action
3. Remove the model selector
The model is determined by the town-level default (
townConfig.default_model). Remove the per-sling model dropdown entirely. If the user wants to change the model, they go to Settings.4. Simplify the form
The sling form should be minimal:
No model selector, no agent selector, no advanced options. Just "what do you want done."
Files
Find the Sling Work button/form component — likely in the rig detail page or rig workbench view under
src/app/(app)/gastown/[townId]/or a shared component. Search for "sling" or "SlingWork" or "CreateBead" in the frontend code.Acceptance Criteria