Use Plato Agent

User docs

Platonic 0.2.2 documentation: This page describes the current public release. Install its supported bundle through the release track before following the first-run journey.

Platonic is the self-hosted agent server. It owns workspaces, profiles, threads, provider calls, tools, policy, approvals, and ledgers. Plato Agent is the client distribution built on Platonic; its commands are plato and plato-tui.

Start a durable thread

Use the site’s single working model as the map for the terms below.

Part	What it means
Workspace	A named, registered directory with a server-minted id and one ledger. Registration is explicit; identity is not inferred from the directory name.
Profile	Configured data bound to one workspace: model, reasoning effort, approval policy, default toolset, and versioned instructions, memory, and skill references. It is not a process or plugin.
Thread	A durable conversation with immutable authority: profile revision, working directory, model, approval policy, and allowed effects. Each profile has one durable home; children remain in that profile.
Run	One submitted task driven by the server. Provider requests, tool decisions, results, and the final answer belong to that run.
Ledger	The workspace-owned durable record used for status, transcript loading, and offline replay. It is the audit record, not a cache of the TUI screen.

Profile defaults, thread authority

Each profile supplies defaults when a thread is created. Updating a profile appends a content revision and changes defaults only for future threads or turns. Existing thread authority is never rewritten. A child thread may receive a narrower toolset, path set, repository set, network grant, or approval policy than its parent, but it cannot use inheritance to widen the parent’s authority.

That split makes history interpretable: the profile answers “what defaults were offered?” and the thread answers “what was this conversation allowed to do?”

What survives

• Closing Plato Agent leaves the host server, thread authority, completed run, and ledger in place. Reattach while that daemon is running to see the thread transcript again.
• plato replay reads the committed ledger without a server, provider call, or tool execution.
• Restarting the server preserves registered workspaces, profiles, home and child authority, and completed ledger records. Live thread state is process-local, but opening the profile again resolves the same home and its next thread.send reloads execution for a new turn.
• If the server stops during a run, restart recovery records the interrupted run as failed. Partial streaming text is not promoted into a completed replay answer.

Follow the first productive journey to see each boundary and its exact checkpoint.

Continue with daily operation, approvals, and providers or the Developer guide for architecture and protocol internals.