Dashboard Chat
Dashboard Chat is the everyday conversation surface for Anyy. It streams active work, keeps persistent session history, and presents model, execution, clarification, attachment, and queue controls in the same view.
Start a Conversation
Open Dashboard and select Chat:
anyy dashboard
Select New session, type a message, and press Enter. Use Shift+Enter to insert a newline.
The session list separates:
- Chats — ordinary conversations; and
- Background — sessions running as background work.
Select an existing session to restore its history. Older sessions and messages load in pages when you request them.
Composer Controls
| Control | Action |
|---|---|
Enter / Send | Send while idle; queue the message while Anyy is working |
Shift+Enter | Insert a newline |
Escape when no local control handles it | Stop the displayed reply and keep pending inputs |
/ | Open the commands available for the current session |
| Attachment button/drop target | Add files to the next message |
There is one Send button. While Anyy is working, sending adds a follow-up above the composer. Each waiting message has its own controls:
- Steer moves that message to the next steering checkpoint. It leaves the queue rail and appears as pending in the conversation; it does not cancel a running tool.
- Edit opens that message's text and attachments. Save updates that item in place; Cancel leaves it unchanged.
- Delete removes only that waiting message.
Once Anyy has selected a message, it is no longer editable in the queue. If another view or the running agent changes it before your action arrives, Chat refreshes the queue and keeps your unsent draft and attachments. See Sessions for queue behavior and session controls.
Select a Model and Reasoning Level
The Chat header shows the session's current model and reasoning control. You can switch to another available provider/model and choose a reasoning level supported by that model.
These controls apply to the current session. The saved main model remains the default for new sessions; change that on Dashboard Models or with anyy setup model.
Provider reasoning modes can change latency and token use. Switching effort may invalidate an existing prompt cache, which can increase input-token charges. Start a new session when you want a clean context and predictable cache behavior.
Clarifications
When Anyy needs a choice or missing detail, Chat shows a Clarification needed card. Select an offered option or type an answer in the composer. While the clarification is active, that input answers the question instead of starting a normal turn.
Resolved clarifications remain in the conversation history so later messages retain the decision context.
Attach Files
You can add up to five files to one Dashboard message. Each file can be up to 50 MiB.
Dashboard classifies PNG/JPEG as image inputs; other uploads are files. Uploading audio or video does not automatically route it through speech or video understanding.
Pending uploads are scoped to the current session and expire after 24 hours if they are not sent. A failed send leaves the source file on your computer unchanged. Sent attachments can be previewed or downloaded when their type is supported by the browser.
When a model or tool needs an attachment, its contents may be sent to the configured provider or backend. Do not attach credentials or private files unless that destination is trusted and the task requires them.
Interrupt and Resume
Press Escape when no picker, preview or drawer is using it to stop the reply currently displayed and wait for it to settle. A delayed stop request does not cancel a later reply that has started in the same session. Already committed messages, tool events, and both pending queues remain. You can then edit queued inputs or send a new prompt in the same session. Stopping does not automatically start another invocation.
Dashboard can be stopped and reopened without deleting sessions:
anyy dashboard --stop
anyy dashboard
The resident Gateway and Profile database own session continuity; the Dashboard web process does not.
History, failures, and notifications
Reloading or reopening a session restores its recorded messages and tool activity. A failure belongs to the invocation that failed; a later successful turn does not replace it. The status area shows model/context usage and live progress for the displayed work.
Runtime notifications can appear alongside conversation history and return after reload. They are stored separately from canonical assistant messages; they do not become a new assistant answer or change the selected conversation branch.
Session tool selection, manual compaction and forks are available through their documented CLI/RPC entrypoints. Chat does not add a tool picker, manual compaction button, branch-tree picker or fork action. See Sessions.
Slash Commands
Type / to browse the live command catalog. The exact set can depend on the current session, runtime, installed Skills, and enabled capabilities. Common commands cover sessions, provider/model selection, status, usage, Skills and reasoning effort.
When skill_manage is available, ask Anyy to install a trusted local ZIP package by its host path. The installed Skill is also visible in Dashboard → Skills for the same Profile.
Prefer the menu over memorizing a static list: it reflects the commands actually available to the running Anyy version.
Tips
- Use one session per sustained topic so memory and tool history stay relevant.
- Start a new session after a large model, Role, or reasoning change when you want a clean context.
- Use Background for work that should continue independently of the current conversation.
- If a response appears stuck, inspect its live status before interrupting; tools and provider calls can have different latency.
Troubleshooting
| Problem | Fix |
|---|---|
| Send is unavailable | Verify the main model and provider on Models, then run anyy status |
| A model is missing from the selector | Refresh/test it on Models, or rerun anyy setup model |
| An attachment is rejected | Keep the batch to five files and each file at or below 50 MiB |
| A correction should affect the ongoing work | Send it, then choose Steer on that queued message; use Escape to stop the displayed reply |
| A session seems missing | Check Chats versus Background, then verify the selected Profile |
| Live updates stop | Reload the page; if it persists, check anyy status and restart Dashboard |