Set up in your harness

An agent drives Smithers, not you. Ask your coding agent for an outcome; it runs the work, watches it, and clears approvals for you. Set up two ways: paste a prompt and let your agent wire everything, or run three commands yourself.

Fastest path: let your agent do it

Paste this into your harness (Claude Code, Codex, Cursor, Copilot, or any shell-capable agent). It installs the workflow pack, syncs Smithers’ generated CLI skill files where supported, registers the MCP server, and reports which starter fits your next task.

Setup prompt

Set up Smithers (a durable AI workflow orchestrator) in this repo for me.

1. Run `bunx smthrs init` to scaffold `.smithers/`.
2. Sync Smithers skill files where supported and register its MCP server:
   `bunx smthrs skills add`
   `bunx smthrs mcp add`
3. Read `bunx smthrs docs` so you know the CLI verbs and components.
4. Run `bunx smthrs starters` and tell me which workflow fits the
   task I describe next.

From now on, when I ask for multi-step, long-running, or human-in-the-loop work,
use Smithers to orchestrate it instead of doing it inline.

init prints what it scaffolds, the agents it detected, and next commands to try. skills add syncs every Smithers-owned skill to supported locations, both the generated CLI command skills and the curated smithers skill, with the same behavior in agent and CI sessions as in a terminal; skills list reports the status of both. mcp add registers an MCP server for detected agents: Claude Code, Codex, Cursor, Gemini, OpenCode, Amp, Windsurf, and more.

Or wire it by hand

# 1. Scaffold the workflow pack into .smithers/
bunx smthrs init

# 2. Sync every Smithers-owned skill (CLI command skills + the curated skill)
bunx smthrs skills add

# 3. Register Smithers as an MCP server in every detected agent
bunx smthrs mcp add

Scope the MCP install with --agent <name>, or the skills sync with --no-global to target the repo instead of home:

bunx smthrs mcp add --agent cursor
bunx smthrs skills add --no-global

No skills directory? Point it at bunx smthrs docs-full (prints the full docs bundle) or bunx smthrs ask "<question>", and add a few lines to AGENTS.md or CLAUDE.md so it remembers Smithers is available.

Pick your harness

Each page covers exact paths, config files, and harness-specific steps.

Harness	Setup page
Claude Code	agents/claude-code
Codex	agents/codex
Cursor	agents/cursor
GitHub Copilot	agents/copilot
Pi	agents/pi
Hermes	agents/hermes
OpenClaw	agents/openclaw

The full support matrix and three integration surfaces (skill, MCP server, standing instructions) live in Agent Support.

Verify it worked

Ask your agent to list the workflows; under the hood it runs:

bunx smthrs workflow list
bunx smthrs starters

If the MCP server registered, the agent can call list_workflows, run_workflow, watch_run, and resolve_approval. See the MCP Server reference for every tool.

Next steps

Quickstart runs a seeded workflow immediately.
Installation covers the .smithers/ layout in detail.
Agent Support is the per-harness hub.

Start

Articles

Learn

Capabilities

Build Workflows

Run and Operate

Workflow Pack

Components

Integrations

Agent Support

Examples

Contributing

Set up in your harness

Fastest path: let your agent do it

Or wire it by hand

Pick your harness

Verify it worked

Next steps

​Fastest path: let your agent do it

​Or wire it by hand

​Pick your harness

​Verify it worked

​Next steps

Fastest path: let your agent do it

Or wire it by hand

Pick your harness

Verify it worked

Next steps