Relay/integrations
DocsBlogGet started →
INTEGRATIONS

Meets your agent where it already works.

Relay doesn't ask your tools to change. Agents read the same files they already read (AGENTS.md, PLAN.md); signal comes in from the places it already lives. Today everything runs through the CLI. Login installs account-level tooling; repository integration is completed separately by running scriptonia init at each exact committed Git root.

Claude CodeAVAILABLE
Login installs the dedicated skill; a separate `scriptonia init` at the exact Git root writes AGENTS.md. Claude then reaches for `scriptonia plan` before user-facing work.
Codex · Cursor · OpenClaw · HermesAVAILABLE
AGENTS.md contract written by `scriptonia init` — execute PLAN.md exactly, respect Non-goals, stop on UNRESOLVED.
Any MCP-native agentAVAILABLE
Run `npx -y scriptonia mcp` as a stdio MCP server: get_context, link_back, flag_contradiction.
Files & pipesAVAILABLE
`scriptonia add notes.md call.vtt` or pipe anything: `pbpaste | scriptonia add -`. Text, markdown, .vtt/.srt transcripts.
Slack connectorPRO
Channel messages flow in as signal automatically.
Email forwardingPRO
Forward customer emails to your project's ingest address.
Web dashboardCOMING SOON
Review contexts and plans in the browser. The CLI came first — it's where the work happens.

Want one we don't have?

Tell us: sathwik07@relayevals.com. Integration requests are signal too — the most-asked-for one gets built next.