Conversations & Sessions

A session is Anyy's durable conversation boundary. It holds messages, tool activity, approvals, clarifications, the selected Role/model state, and the continuity needed for later turns.

Sessions are stored in the selected Profile, not in the Dashboard or terminal process. Closing a browser or terminal does not delete them.

Session history and durable Profile memory are different stores: sessions live in state.db and referenced objects, while cross-session user facts and assistant memory live in memory/USER.md and memory/MEMORY.md.

Conversation and Background Sessions

Anyy uses two user-visible kinds:

Kind	Purpose
Conversation	Direct chats started by you in Dashboard, TUI, CLI, or a Channel
Background	Scheduled work, delegated work, and resident reviews that run independently of the foreground chat

Dashboard Chat separates them into Chats and Background. Inspect both when looking for a scheduled or delegated run.

Automatic Session Lifecycle

Two model-assisted actions keep ordinary conversations usable over time.

Session titles

A new conversation begins as New session. After its first successful user/assistant exchange, Anyy asks the session's selected provider and model for a three-to-seven-word title in the first user message's primary language.

• Title generation runs separately after the foreground reply, with a 30-second timeout.
• It sends the first exchange to the selected provider and adds a model request, token usage, and possible cost.
• It never replaces a title that was explicitly supplied for the session.
• If generation fails or returns no usable title, the conversation remains New session; the completed reply is unaffected.

Context compaction

Before a new run, Anyy estimates the session context against the selected model's configured context length. At 50% pressure it can summarize the older prefix; if pressure has already reached 85%, the same check uses the higher-priority hygiene path.

Compaction keeps a recent message tail and stores a current context summary for later model input. It does not delete or rewrite the canonical transcript: Dashboard history, Session Search, backups, and audit evidence continue to use the original records.

The summary normally uses the session's selected provider and model, so it can add a model request, tokens, and cost. If model summarization fails, Anyy can use a bounded static fallback so the original conversation remains available. The 50% and 85% ratios are runtime safeguards derived from model context configuration; they are not “every N turns” schedules.

A summary is context management, not memory

Compaction helps the model continue one long session. It does not move personal facts into USER.md or MEMORY.md. Save cross-session context through Memory.

Use Conversations in Dashboard

Open Dashboard and select Chat:

anyy dashboard

Select New session, type a message, and press Enter. Use Shift+Enter for a newline. Select an existing session to restore its history; older sessions and messages load in pages on demand.

The composer provides these controls:

Control	Action
Enter	Send the current message
Shift+Enter	Insert a newline
Stop	Request interruption of the active turn
/	Browse commands available to the current session
Attachment button or drop target	Add files to the next message

The Chat header also exposes the current model, reasoning level, and execution mode. These values belong to the session. For their behavior, see Models & Providers and Approvals & ChangePlans.

Queue and Steer

When a turn is already running, a normal new message becomes a queued next task.

• Queue keeps it as a separate later turn.
• Steer redirects the active execution with the queued input instead.

Dashboard keeps queued items visible and lets you edit or cancel them before execution. Steering is available only while there is an active target execution. The TUI offers equivalent queue, edit, cancel, and steer controls.

Use steer for corrections, queue for new work

Use the CSV instead of the PDF is a steering instruction. After that, draft the email is a separate queued task.

Answer Clarifications

When Anyy needs a choice or missing detail, Dashboard 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 session history so later turns keep the decision context.

Attach Files

Dashboard accepts up to five non-empty files in one upload, with a maximum of 50 MiB per file. Unsent staged uploads belong to the current session and expire after 24 hours.

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.

For download, export, and retention behavior, see Artifacts & Deliverables.

Interrupt and Resume

Select Stop to request interruption of the active turn. Already committed messages and tool events remain in the transcript. You can then correct the task in the same session or start a new one.

Stopping and reopening Dashboard does not delete sessions:

anyy dashboard --stop
anyy dashboard

The resident Gateway and Profile database own continuity; the Dashboard web process does not.

Resume from the TUI with /sessions, or use a known ID:

anyy --resume SESSION_ID

If a session is missing, confirm the selected Profile or --home; Anyy does not search session IDs across Profiles.

Start from the Terminal or CLI

Open the TUI:

anyy

Then use /new for a new session. Choose its initial Role at launch when needed:

anyy --role scribe

For a single CLI turn:

anyy chat "Summarize my priorities"
anyy chat --session SESSION_ID "Add the new constraint"

Useful anyy chat options:

• --role ROLE chooses the Role only for a new session;
• --session ID continues an existing session;
• --json returns IDs, state, response text, and approvals; and
• --yes approves supported pending approvals for that invocation.

--role and --session cannot be combined. anyy chat requires a running resident Gateway.

Session Execution Mode

Each session stores its own approval or yolo mode, and the selection persists when the session is resumed.

Change it in the Dashboard Chat header or in the TUI:

/yolo on
/yolo off

Review Approvals & ChangePlans before using yolo.

Slash Commands

Type / in Dashboard Chat to browse the live catalog. The exact commands depend on the running version, current surface, session, enabled Skills, and capabilities. Prefer the live menu over memorizing a static list.

See Slash Commands Reference for the stable command families and surface differences.

Session Lifecycle

• Starting a new session does not modify older sessions.
• Interrupting a turn keeps already committed transcript and tool activity.
• Automatic title generation and context compaction may make additional provider requests.
• Context compaction changes future model input, not the stored transcript.
• Background work remains visible in its own session history.
• A normal Profile backup includes session data.
• Anyy currently has no public Dashboard, TUI, or CLI action for deleting an individual session.

Tips

• Keep one sustained topic per session.
• Start a new session after a major Role, model, or reasoning change when you want clean context.
• Use Background for work that should continue independently of the foreground chat.
• Treat approvals as a review step, not a routine click-through.
• Inspect live status before interrupting; tools and provider calls can have different latency.
• Use --json when another program needs session and execution IDs.

Troubleshooting

Problem	Fix
A recent conversation is missing	Check the selected Profile and Chats versus Background
Send is unavailable	Verify the main model and provider, then run anyy status
A queued correction ran as a later task	Use Steer while the target execution is active
An attachment is rejected	Keep the batch to five files and each file at or below 50 MiB
/sessions is unavailable	Wait for or interrupt the active TUI turn
anyy chat cannot connect	Start the resident Gateway with anyy gateway start
A resumed session uses an old Role or model	That state belongs to the session; start a new one for new defaults
Live updates stop	Reload Dashboard; if it persists, check anyy status and restart Dashboard

See Dashboard and Terminal Interface for surface startup and navigation.