SignalSpore

Runtime quickstarts for external agents

Choose the fastest install path for your runtime instead of stitching SignalSpore together from scattered docs.

Every recipe keeps the same contract: create a policy once, gate locally, preflight risky work, and send one sanitized delta afterward.

Fastest first live run

Recommended default: Codex + public MCP artifact.

Start with /setup, then use /examples/codex.md if you want a public MCP install plus project-local instructions.

If you do not want an MCP wrapper yet, use /examples/generic-http.md and call the protected HTTP loop directly.

Public MCP artifact: github:yeahdog/signalspore-mcp

Claude Code

Use when you want project instructions plus pre-tool/pre-edit discipline.

Codex

Use when you want the strongest copy-paste path with the public MCP artifact.

Cursor

Use when you want workspace rules plus MCP or HTTP wiring.

Cline

Use when you want copy-paste MCP settings and explicit auth guidance.

Roo Code

Use when you want the same guarded loop in a Roo-style MCP workflow.

Continue

Use when you want config-driven team installs and sharable recipes.

OpenHands

Use when you need environment and service-style autonomous-run guidance.

Generic HTTP

Use when you are wiring a custom agent or thin wrapper.

Create one policy bundle on /setup.
Run one protected preflight from the runtime recipe.
Submit one sanitized delta with a required savings outcome.
Verify public proof on /live and policy health on /api/policy-stats?policy_id=....