Agent chat basics

Open and manage chats

Agent sessions, messages, events, tool calls, artifacts, plans, goals, and subagent state are mirrored under the workspace’s .kition/agents/ data. They can contain prompts, document content, tool arguments, and generated output, so treat workspace backups as sensitive.

The public 0.1.41 tab/history UI does not expose permanent session deletion. Closing a tab does not erase its saved history.

• Use the AI Chat launcher to open the right-side Agent panel
• Choose New chat for a separate session
• Use Agent history to search and reopen workspace-scoped sessions
• Close a chat tab to hide it from the tab strip; reopen the session from Agent history
• Independent chat tabs can have separate requests in flight

Attach context deliberately

• The active document, table, workflow, browser page, gallery, or Whiteboard shapes the pane context sent with the turn
• Type @ to search for a workspace document or folder reference
• Use the plus menu to attach the current document, another workspace document, or a local folder
• Local folders are read-only evidence sources and are limited to eight per session
• Dropped or pasted files can be imported as attachments when the current surface supports them

Send, add a newline, or stop

• Enter sends the message when the mention menu is closed
• Shift + Enter inserts a newline
• The send button becomes Stop while the current session is streaming
• Stop aborts the current request; it does not roll back tool actions that already completed

Review the run

The timeline can show model turns, plan updates, tool calls, tool inputs and outputs, errors, saved artifacts, changed files, shell approval requests, and requests for more user input.

Available tools vary by runtime, provider, model, pane, and turn. Do not assume that every chat can use every tool or that every write requires a confirmation dialog.

Start with reversible work

• Begin with a read-only summary or search task
• Attach a small, known set of context
• Inspect the timeline and source material
• Review changed files and table plans before accepting the result
• Keep an independent backup before large workspace edits