Daily operation
User docs
Unreleased 0.2.0 documentation: These pages describe the current
developbehavior. The public release is still 0.1.0; no released 0.2.0 bundle or bundle-install proof exists. The first journey was verified with binaries built from its exact source commit. Do not treat or publish this guide as release-current untilplatonic-v0.2.0exists.
Complete the first productive journey before using this section as the daily reference.
Plato Agent has several local client surfaces, but they all use one Platonic server on the same host. The server owns threads, provider calls, tools, approvals, and the durable ledger.
Choose a surface
Section titled “Choose a surface”| Need | Use | What happens |
|---|---|---|
| Work interactively | plato |
Ensures the host server, admits a durable root thread, and opens the TUI |
| Ask once | plato "QUESTION" |
Ensures the host server, runs one turn, and prints a replay hint |
| Continue the latest workspace session | plato -c "QUESTION" |
Appends one turn through the one-shot client |
| Return to a durable thread | plato --remote THREAD_ID |
Opens a TUI on that existing thread through the same-host socket |
| Inspect committed history | plato replay |
Reads the registered workspace ledger offline |
| Attach a terminal-only client | plato-tui |
Connects to an existing server; it never starts or supervises one |
--remote does not mean a remote host or HTTP gateway. It attaches another local terminal client to an existing thread through the host socket.
Pick up work
Section titled “Pick up work”A session groups conversational runs in one workspace. A thread adds durable, immutable authority such as its model, approval policy, working tree, and network grant.
- Use
plato -c "QUESTION"to continue the latest workspace session through the one-shot client. - Use
/threadsin the TUI orplato thread listto find durable threads. - Use
plato --remote THREAD_IDor select a thread in the picker to attach without creating another one. - Use
vfor the complete audit view andplato replayfor the committed offline record.
Closing a client does not stop the host server or delete a thread. Stop a thread only when you intend to finish its server-owned repository lifecycle.
Inspect status
Section titled “Inspect status”Use /status in the TUI for the selected session. It reads the effective provider and model, server identity, ledger, usage, approval counts, and session-scoped approval state without calling a model or changing the session.
For a shell-readable server result:
platonic status --workspace "$PWD"Use plato thread status THREAD_ID for a durable thread’s model, approval policy, working directory, and current loaded or active state.