Chats and turns

Chats

A chat (also called a session) is one conversation. Its history is kept on your Crewdesk server, so the same chat is there in the app and in the terminal. The app groups your chats in the sidebar (Today, Yesterday, Previous 7 days, Older); the CLI shows the same list, and crewdesk --resume picks one to continue.

A chat remembers:

• its messages and the tool calls behind them;
• the folder it worked in, if any;
• the assistant it was started with, and its model tier;
• the files and pages its replies saved.

Turns

A turn is one message of yours and everything Crewdesk does to answer it: call tools, stream the reply, propose writes, save the result. A turn ends in exactly one of three ways: done, stopped (by you; what had streamed stays) or failed (with a reason).

Inside a turn the agent works in a loop: think, call a tool, read the result, decide what's next. Some limits keep a turn bounded:

• a number of tool rounds per turn, with more when a folder is open;
• a time budget of about five minutes, after which the agent is told to stop and say what's left;
• a tool that fails three times in a turn is blocked for the rest of it.

Plans and to-do lists

For a bigger job, the agent can propose a plan as a card for you to approve before it starts (/plan asks for one explicitly). While it works, it keeps a live to-do list beside the chat, so you can see where it is.

Short follow-ups

A short "yes" runs what the last reply proposed. A request that needed a folder continues when you open one. You don't have to repeat yourself.

Proposals

When a turn wants to write, it ends on a proposal: an approval card waiting for you. It survives restarts. Your answer, a button or a word, starts the next turn, which runs exactly what the card showed.