seamless docs

Reference

The complete Seamless surface - every MCP tool, both CLIs, every configuration key, every hook, the console, and the on-disk file formats.

This section is the contract: the complete enumeration of every surface Seamless exposes, with the parts that are generated straight from the code so they cannot drift from it. The MCP tool reference is rendered from the same catalog the server registers, and the configuration reference from the same defaults the daemon loads - adding a tool or a key makes stale docs a build error, not a doc bug.

Agents mostly care about the MCP API: the endpoint and auth model, the scope rules, and every tool grouped by area - sessions, memory and recall, notes and projects, tasks, and the research lab. Humans get the two CLIs: seam, the short handle an agent or owner types, and seamlessd, the daemon and operator commands.

Deployment behavior lives in Configuration (every key, type, and default, plus the four layers that resolve them) and Hooks (what install-hooks writes per client, the transports and timeouts, and the fail-open contract). The two compatibility matrices - Claude app and Codex - hold versioned, platform-specific evidence rather than assumptions, and record how to re-verify each claim.

The remaining pages describe what you can see and touch directly: Console documents the observability UI at /console and the complete list of what it can change, Storage and file formats specifies the ~/.seamless tree and every frontmatter field, and the Glossary pins the vocabulary - including the distinctions that actually matter, like memory versus note versus finding, and archive versus supersede versus delete.

MCP API overview

The endpoint, the auth model, the scope rules, and an index of every tool Seamless serves.

Sessions, memory & recall

The eight tools an agent uses most - open a session, write and read memory, and search the store.

Notes, projects & capture

Work artifacts, project scope, and SSRF-safe URL capture - the eight tools around the edges of memory.

Tasks

The six task tools - the dependency-aware ready queue and lease-based claiming that lets parallel agents divide work safely.

Lab, gardener & usage

Research trials, the propose-only gardener, the usage summary, and favorites - the nine tools for keeping the store honest.

seam CLI

Every seam subcommand - agent loop, tasks, plans, observability, hooks - plus the flag-order rules and what each one rejects.

seamlessd CLI

The daemon and operator CLI - serve, doctor, import, install-hooks, uninstall, update, map-repo, family, console-open, start/stop/restart/status, and version.

Configuration

Every configuration key, its type and default, plus the annotated example file and the four layers that resolve them.

Hooks

The hooks Seamless installs per client - six for Claude Code, five for Codex - their transports and timeouts, the fail-open contract, and what install-hooks writes.

Claude app compatibility matrix

Versioned evidence for the Claude app's two surfaces - embedded code sessions (hooks, MCP, runtime skew) and the chat surface's stdio MCP bridge.

Codex compatibility matrix

Versioned, platform-specific evidence for the Codex hooks, MCP transports, trust gate, output limit, and the contract-recapture procedure.

Console

The read-mostly observability UI at /console - the complete list of what it can change, how sign-in works, and what each page shows.

Storage and file formats

The ~/.seamless tree, memory and note frontmatter field by field, what lives only in SQLite, and the rules for hand-editing.

Glossary

The vocabulary, with the distinctions that actually matter - memory vs note vs finding, briefing vs recall, archive vs supersede vs delete.