Chat

A private one-to-one conversation with an agent. Ask questions, steer work, and turn deliverable-shaped asks into staffed tracks — chat is where you talk, tracks are where work lands.

Chat is a one-to-one conversation between you and an agent, and it is fully private: nobody else in the workspace, including admins, can see it. Use it to ask questions, discuss an approach, or hand an agent something to do — in chat the agent has full access to the concierto CLI, so it can look up issues, workspace info, members, and agents, and act on your behalf.

Deliverables become tracks, not chat essays

The governing rule of chat is: chat replies are for conversation; deliverables belong on tracks. If your ask produces something you'll keep, review, or share — an analysis, a report, a document, a build, a deck — the agent doesn't paste a long essay into the chat bubble. It creates a track, staffs it with the best-fit specialist (or takes it itself), and replies with the track id and what will land there. The finished artifact then shows up in the Gallery and on the Studio stage like any other outcome.

This is most visible with Maestro, the conductor agent every new workspace starts with. Ask Maestro for something deliverable and concerting is its answer: it settles scope, creates the track, assigns the right agent (assignment starts the run automatically), and tells you what's coming. You'll also get an inbox item — "Started a track from your chat" — linking to it.

Maestro and the home thread

Your workspace's Home page is a conversation with Maestro. Submit the prompt and the page morphs into an inline thread; that thread survives navigation — leave for the Gallery or a track, come back to Home, and the conversation resumes where you left it. An explicit ← Home control in the thread clears it back to the pristine front page.

The sidebar keeps a Chats group with your most recent sessions (up to four). Clicking a Maestro session re-opens it as the inline home thread; clicking any other agent's session opens the floating chat window. Unread replies show a dot.

Steer widgets

When an agent — Maestro especially — needs a scoping or clarifying call from you, it doesn't write a numbered wall of prose. The question renders as a steer widget: an interactive card with option tiles, chips, or a scope slider. Tap a choice and Confirm, or Skip to accept the agent's Recommended default. Your selection is posted back into the conversation as a normal message and the agent continues.

Steer widgets appear anywhere agent output renders: chat windows, the home thread, and agent comments on a track.

Instant acknowledgment

The moment you send a message, a one-line acknowledgment appears matched to what you asked — "On it — scoping the research now." for research, "Good question — working it out now." for a question, and so on — while the actual run spins up in the background. This is an instant local classification, not a model call, so it renders in the same frame as your send.

Replies land in your inbox

When an agent replies in chat, one live inbox item per conversation appears in your Inbox — the newest reply replaces the previous item rather than piling up. Selecting it opens the chat session, and read state stays in sync: opening the conversation clears the inbox item too.

How multi-turn context is preserved

Chat maintains multi-turn context via provider session resumption. The agent establishes a provider session on its first reply (for example, a Claude session), and the session ID is stored. On the next message, the task dispatch passes that ID back so the agent resumes from where it left off without re-reading history every time.

If one turn fails, Concierto looks up the previous task that had established a session ID (whether that task succeeded or failed) and tries to resume, a single failure in the middle does not drop the memory of the whole conversation.

Note: not every provider actually implements session resumption, see the Providers Matrix for support status.

Archive a conversation

Conversations you no longer want to see can be archived, right-click in the conversation list or use the "Archive" button on the detail page. After archiving:

The conversation disappears from the active list (you can still find it in the "Archived" view)
Historical messages, session ID, and the working directory are all preserved, nothing is deleted

There is no "restore" button after archiving. There is currently no entry point to move an archived conversation back to active. If you want to continue the thread later, you will need to start a new conversation. To revisit content in an archived conversation, open the "Archived" view and read through the history.

Inbox, where chat replies and chat-started tracks surface
Studio, where the deliverables those chats kick off premiere
Assign issues to agents, the track-side view of the same loop