Clio Coder 0.5.7

Coordinator discovery and composition

• Main sessions attach read, write, edit, gateway, and dispatch when wired. Secondary builtin, extension, and MCP capabilities remain discoverable through the gateway; workers retain their recipe tool surfaces. Ordinary dispatch uses a compact schema, with advanced composition described on demand and canonical validation retained.
• Gateway discovery ranks task vocabulary and returns deterministic pages of 12 by default. The model-facing recipe catalog also accepts task vocabulary without loading workflow bodies or installing packages.
• gateway(op="chain") composes bounded dependency steps and structured result references. Eligible independent reads run in parallel; failures, cancellation, interviews, skill activation, and terminal results stop scheduling. Completed child receipts remain available to completion assessment, artifacts, handoffs, and path indexing after a later failure.
• Gateway and chain receipts retain capability identity, per-check verification, partial writes and denied operations. Historical skill instructions and continuation hooks remain available when secondary schemas are hidden.
• Optional fleet.decisionProfiles.harnessRouting binds an advisory intent and capability shortlist to the existing pre-turn decision batch. Unbound sessions do no additional catalog preparation or inference. Routing never grants authority or removes capabilities from discovery.
• Coordinator prompts guide intent understanding, bounded delegation, verification, user steering, and explanations of project state. Educational walkthroughs, reports, and knowledge checks are offered when useful and created when requested.
• Repository tours, architecture maps, and open-ended exploration go to the read-only Scout recipe before the coordinator surveys directories itself, with independent areas sent as one parallel batch. An undecided user receives two or three next steps grounded in bounded read-only workspace observations.
• Runtime guidance compiles reachable capability hints and schema-validated examples without enlarging the attached tool surface. Display, traces, ACP, and the browser application name the capability each gateway call ran; worker grounding, tool-call bounds, and the loop guard count each settled chain step once, as a direct call would.

Verification and execution evidence

• Repository quality policies in .clio-coder/quality.yaml select required checks by changed path. A valid policy selects high rigor unless overridden.
• Verification records source, check-declaration, and policy fingerprints. Completion assessment requires fresh evidence for the covered inputs and reports outstanding requirements in interactive and worker runs.
• Receipts distinguish executed checks, denied checks, result quality, and completion findings. Denied verification calls preserve their admission outcome without acquiring a validation result.
• Validation grounding recognizes equivalent npm, pnpm, and Yarn test-script invocations.
• Scout citation repair names the rejected path:line and the file's current physical line range. Empty root find and grep results name the internal directories they exclude and state that a miss does not prove a file is absent.
• Architect plan workers keep the artifact tool their contracted PLAN.md requires when a bound skill narrows the tool surface.

Project and session context

• The structural index is now a codemap, stored at .clio-coder/codemap.json. Existing schema-v5 indexes and legacy codewiki.json artifacts remain readable.
• Bounded project orientation includes declared purpose, commands, entry candidates, areas, counts, workspace scope, observation time, and input identities. code_nav project mode retrieves current Git and durable operator-task status.
• Foreground prompt assembly uses bounded state and root inputs. Incremental reconciliation shares dependency work, and dispatched workers receive orientation independently of handbook availability.
• CMake orientation handles comments, quoted examples, and literal preset names. Project status handles grouped Git rename/copy records and remains available during codemap rebuild failures.
• structural-v2 becomes the default working-set policy, protecting recent assistant steps and repeated recalls. The default, data-analysis, and web-design profiles tailor retained context to the task.
• Context pressure is checked before each model request, including tool continuations. A rearm band controls repeated automatic eviction and summary; /context displays the active profile and rearm percentage.
• Recall supports visible eviction-marker paths and historical references. Rereads preserve recall lineage, and recall-recording failures preserve successful file reads.
• Reviewed handoffs are bound to the active session, conversation branch, and decisions. Changes invalidate a draft before it creates the successor session.
• Session compatibility: format 6 records eviction reasons, reread triggers, and optional content hashes. Supported older ledgers are upgraded when opened; format-5 readers cannot reopen format-6 sessions. Upgrade clients sharing sessions together.

Browser application and ACP

• First-time browser users can connect a model through the shared configure wizard before opening a project, including masked key entry, supported browser sign-in, model inventories, passive checks, and review before Save. Existing configured users go directly to project selection.

• GUI Settings follows configure and the TUI's eight sections, control groups, and order. Connections replaces the old flat form; model defaults use Use connection default, and proactive memory offers Rules only. Terminal launch behavior stays the same.

• The browser application adopts the canonical cyan Clio mark, warm dark/light palette, and locally bundled IBM Plex and Newsreader fonts across navigation, installation icons, and offline recovery.

• Conversations use a compact input with attachment, message-options, model, thinking, and send/stop controls. Sessions switches the sidebar to conversations grouped by project, with expandable history and a return to application navigation.

• Sidebar controls for Settings, Library, Traces, Fleet, Evidence, Toolchain, and System keep the active conversation in view. Explicit viewer links open larger inspection pages. A collapsible right inspector presents recorded file activity, tool results, and linked evidence beside a compact conversation dashboard.

• Traces, Fleet, Evidence, Library, Toolchain, Settings, and System gain focused inspection, URL-backed discovery, reviewed operations, and clearer storage/error states. Recorded session traces open correctly, and unpriced model usage remains unavailable rather than displaying zero spend.

• The alpha browser application exposes session boards, operator tasks, plans, decisions, memory proposals, context inspection and recovery, conversation branches, and reviewed handoffs through ACP host capabilities.

• Fleet previews show waves, routes, write boundaries, gates, command arguments, and budget. Execution checks the approved recipes, resolved routes, and registered invocation bindings; bounded previews mark omitted details.

• Requests accept supported images, workspace @path references, and bounded UTF-8 text attachments. Model and thinking controls distinguish conversation settings from saved project defaults.

• Side questions and labelled alternative drafts run beside the main conversation. Draft comparison can use a configured decision model.

• Session usage, provider quota, extension eligibility and reload, and library updates are available to open browser sessions. ACP hosts also bind sharing, archive operations, advisor and council workflows, and transcript export.

• Bare clio-coder gui reuses the installation's owned background application or starts a private foreground server. Installed Linux background applications refresh launch paths after an upgrade while idle.

• Streaming Markdown keeps rendered nodes mounted as a response grows, matches deferred highlighting and Mermaid output to its current source, and updates artifacts independently of response text. Jump to latest returns immediately, reading history keeps its position, and viewport changes no longer stop stream following.

• clio-coder gui --open on Windows passes the loopback URL to the registered browser through the system rundll32 handler rather than cmd.exe. ACP builds its command catalog once per server instead of on every prompt.

Terminal interface

• A semantic presentation system gives the composer, menus, transcript, tool and worker activity, welcome screen, footer, and dashboard one ivory, cyan, and action-orange hierarchy with a distinct YOLO projection. Session and worker prompts prohibit decorative emoji, and displayed answers, worker summaries, side questions, and reasoning follow the authored-prose policy while code, quoted evidence, and scientific notation stay intact.
• The composer rail shows context occupancy and YOLO state, and the thinking effort indicator carries a brain glyph and accent. The compact footer shows the workspace path, Git branch and dirty marker, counters, notices, and active harness facts; thinking, verbosity, and autonomy changes are confirmed briefly in its value slot, and every footer row stays reachable on short terminals.
• Ctrl+G then y toggles the current session between default and YOLO autonomy. The action has no direct key by default.
• The footer dashboard samples local machine metrics only while its Status page is open.
• Live fleet activity appears above the composer, and tasks use grouped cards with empty states.
• /settings targets supports adding and editing targets inside the docked configuration wizard; /config opens settings.
• With an empty composer, ? opens quick help, left arrow opens fleets, and down arrow opens tasks.
• /usage opens an Activity workspace heatmap alongside Accounts, Session, Models, and Workers views. Price coverage and Git observation state are displayed from available accounting and status data.

Safety, providers, and diagnostics

• Git normalization handles quoted words, global options, combined flags, accepted long-option prefixes, and line continuations before policy matching. Forced checkout, whole-worktree operations, and force-prefixed push refspecs retain their applicable permission or block rules.
• Dry-run clean, leased pushes, and named-file restores use their respective Git rules. Proven inert quoted command text is excluded from destructive shell matching.
• Inception Mercury retains its required instant reasoning setting in chat and tool probes.
• Doctor distinguishes unavailable probes from failed health checks, repairs managed Yazi profiles, and checks Slurm controller configuration.
• Relocated Clio homes isolate sibling-CLI credential discovery unless the corresponding product home is explicitly configured. Local-runtime accounting appears when a local target is configured.
• Stored provider credentials become visible to the running session only after their storage write commits.
• ACP aside failures return host diagnostics summaries while provider response bodies remain in the diagnostic stream.

Documentation and distribution

• The safety model documents unattended analysis at yolo, temporary Python scripts, and the remaining damage-control and worker approval limits.
• Removed clio-coder docs, its documentation server, and the browser application’s native Docs reader. Help opens the public documentation and identifies the installed Markdown reference; offline clio_docs retrieval and bundled resources remain available.
• Product documentation describes the current architecture, configuration, context, verification, and delegation interfaces. Generated development wiki pages retain independent v0.1 versioning.
• Website documentation is linked to its release source. README and website include v0.5.7 terminal and browser captures in dark and light themes from a real temperature-calibration session, whose runnable source is in examples/temperature-calibration. Reusable media have checked hashes, dimensions, and delivery copies.
• The installed package contains authored product documentation and its corpus metadata; generated development wiki pages remain in the repository and GitHub Wiki.