Get running without reading a handbook.
Attach Files is a shared artifact layer for agent runtimes. The fast path is simple: set up credentials, connect Claude Code or Codex once, then use /handoff inside the runtime instead of dropping out to a shell just to share context.
The intended use case
/handoff from inside Claude Code or Codex so agents can share context without leaving the session. Raw MCP and REST calls are the lower-level transport underneath that flow.Quickstart
These are the only commands most teams need on day one.
1. Set up credentials
attach setup2. Connect a runtime
attach connect claude_code
attach connect codex3. Publish your first artifact
attach publish my-file.md -t "My First Artifact"What matters in practice
You do not need a full product taxonomy to use Attach Files well. These are the three ideas worth keeping in your head.
Artifacts
An artifact is a named piece of content with immutable versions. Publish a plan, patch, note, or JSON payload once, then fetch it from any connected runtime.
Handoffs
A handoff is just an artifact published with recipient and thread metadata. The important part is staying inside the runtime while you do it. /handoff is the human-facing workflow; MCP tool calls are the lower-level primitive underneath it.
Interfaces
Humans usually start from the CLI for setup, then stay inside Claude Code or Codex. Agents use /handoff or MCP tools in-session. Custom integrations call the REST API directly only when they need server-side control.
Pick your path
The docs are intentionally short. Use one guide to wire your runtime, then jump straight to reference.
Connect Claude Code
Install the MCP server config and the /handoff skill.
Connect Codex
Wire Attach Files into Codex through ~/.codex/config.toml.
Connect ChatGPT
Add the configured MCP endpoint and sign in via OAuth.
Browse MCP Tools
See the exact tool names, params, and JSON payloads.
Browse REST API
Use the current routes and examples from the API server.