Quickstart

Install Seamless with one command, start Claude Code or Codex in a repo, and confirm the first briefing lands.

This is the one happy path: install, start a session, and watch it open with a briefing. It is one command and a check - everything between them is automatic. Every fork in the road is a link, not a branch in these steps.

No CGO toolchain, no external database, no Node. The installer needs curl and tar; building from source needs Go 1.25+.

Install

curl -fsSL https://thereisnospoon.org/install | sh

On Windows, run the same install in PowerShell:

irm https://thereisnospoon.org/install.ps1 | iex

One command does the lot: it fetches the checksum-verified release archive for your platform (macOS, Linux, and Windows; amd64 and arm64), installs seamlessd and seam into ~/.local/bin, generates the bearer key, wires the detected Claude Code/Codex clients (hooks, MCP, and skills), and starts the daemon as a per-user service on 127.0.0.1:8081 with data in ~/.seamless - launchd on macOS, systemd --user on Linux, an at-logon Scheduled Task on Windows. Re-run it to upgrade. Install & deploy has the overrides, service details, and removal procedure.

Piping a stranger's script into a shell deserves a read first - it is one file, and every other route to the same place is on that page: brew install 0spoon/tap/seamless, prebuilt archives from GitHub releases, go install github.com/0spoon/seamless/cmd/...@latest, or make install from a clone.

On a true first run - no config file anywhere - the bearer key is generated and written to ~/.config/seamless/seamless.yaml. Nothing to copy, nothing to paste.

No LLM key is required either: without one, recall degrades to plain full-text search. Add OpenAI or Ollama in the configuration when you want semantic recall.

seamlessd doctor is the checkpoint: it validates the config, opens the database, applies migrations, and asserts the tool count. If it is green, the daemon will start.

Wire your agents

The installer already ran install-hooks for you, so there is no second setup step. Start either detected client in any git repo:

cd ~/code/myrepo && claude    # Claude Code
cd ~/code/myrepo && codex     # Codex

install-hooks selects the installed clients by default. For Claude Code it installs six hooks and registers Streamable HTTP through claude mcp add-json --scope user. For Codex it installs five hooks and registers the maintained seam mcp-proxy stdio policy; Codex itself also supports direct Streamable HTTP. Both profiles receive seam-onboard and seam-research. Installed by hand? Run seamlessd install-hooks yourself first, or select explicitly with --client claude|codex|all.

The hooks are what make sessions ambient: an agent gets a briefing without calling a tool. They also register the repo. On the first session inside a git repo, the SessionStart hook resolves your cwd to its git root, derives a project slug from that directory's name, and records the mapping - so agents inherit project scope without passing project on every call, and without you creating a project first. seamlessd map-repo --path ~/code/myrepo --project myrepo is the override when you want a slug that is not the directory name; see Projects & scope for the full precedence chain.

Restart the selected client once after installing so it reloads hooks, MCP, and skills. In Codex CLI, open /hooks, review the exact Seamless commands, and approve them; seamlessd doctor deliberately reports that trust as unverified. The desktop app does not expose /hooks, so confirm that a real repo chat receives <seam-briefing> before relying on it. See Claude Code setup or Codex local setup for the client-specific behavior.

Confirm it works

That session's context now opens with an injected briefing:

If you see that block, the loop is closed: the hook resolved your cwd to a project, the daemon assembled a briefing within its token budget, and the agent started with your knowledge already in context.

Open the console to watch it happen:

seamlessd console-open                               # opens pre-authenticated

Next steps

• Install & deploy makes the daemon a service that survives reboots instead of a foreground process.
• The installer already delivered seam-onboard for the selected client. Run /seam-onboard in Claude Code or $seam-onboard in Codex once to write a Seamless-awareness block into global or project instructions (CLAUDE.md or AGENTS.md). From a clone, make install-onboard-skill CLIENT=codex installs the Codex copy; the default is CLIENT=detect.
• Look up any tool, key, or command in the Reference.