Where work lives

A conversation ends; the work it produced stays. TALOS Desktop keeps it in a few places, each for one kind of thing, and the agent reads and writes them with the same tools you use from the sidebar.

Conversations

The list of sessions: each row is a piece of work, with its title, its model and its state. States are ordered by what needs you first:

• waiting for you — the agent stopped on a question;
• running;
• waiting for the first message — created, never started;
• interrupted — closed half way, or no longer run by anyone;
• stopped — you stopped it. Stopping is neither finishing nor failing;
• done;
• error — or, when the reason is known, the reason itself, such as “turns exhausted”;
• done · outcome not recorded — an old session with no saved outcome. It does not mean it succeeded.

Turns and model show only when the server counted or declared them. Click a row to open it, right-click it for its actions, or select several. A session can be resumed after you close and reopen TALOS.

Notes

Notes are documents for whoever reads them: what TALOS jotted down while working, and what you write. A note has no state and no assignee — that is what tasks are for. A note without a title takes its first line of text; a note without a date shows none.

Tasks

The to-dos of the work, each with a state — to do, in progress, done — and a priority — low, normal, high. The summary at the top counts open and done tasks, and those whose state was not recorded, apart. Tasks have no due dates or reminders. A task is also what an automation starts again by itself.

The Library

Where the files made during the work end up — documents, images, artifacts — each with its name, when it was made and with which model. There is no bin: deleting a file deletes it for real, which is why it is the only action that asks for confirmation. The model reads a Library file only when it searches for it or opens it; its content never enters the context by itself. See Work with the Library.

Memory

What TALOS must remember beyond one conversation. Each memory has a kind:

• Preference — how you want things done;
• Fact — something true about the project;
• Procedure — how a thing is done;
• Rule — a constraint to respect.

Memory is not a recording of the conversation: a memory exists because the agent wrote it, when it judged it useful, or because you did. It is not part of the preamble either: the model reads it again when it needs it, with its memory search. That is why reading memory counts as a higher risk than reading a note in the Tool Forge: a memory written today is read again in future conversations.

Deep research

A deep research produces a report, not a conversation: one question, many readings, and a document with its claims, steps, verdicts and sources. The report and its evidence are what you consult; the session is only how it was made. Its state says where it stands — running, paused, done, canceled, failed, without a report, blocked, turns exhausted — and only done means there is a report. See Run a deep research.

Projects

Projects groups sessions by project, not by folder: a project can live in several working folders. Each project shows its three most recent sessions and what it cost — turns and tokens — ordered by when you last worked on it. Sessions with no project still have a place. Projects are not created by hand: they come from the folders you work on.