Skip to content
stitch

Turn events into agent work

Connect your agents.
Keep work moving.

Turn repository events into agent workflows. Connect your tools, define the rules, and let Stitch coordinate the work.

FactoriesIssue to fixExample workflow
acme / platform

Fix empty search results

Issue #128 · labeled

agent:build
Trigger matched
Implement issue Succeeded
Harness
OpenCode
Sandbox
Vercel Sandbox
Pull request ready for review

Your event. Your rules. Your agent, in an isolated workspace.

From event to execution

Built around the way you work

Keep the tools you use. Automate the work between them.

EVENT STREAM Example events
Issue labeledJust now

agent:build → implement a fix

The right event starts the work.

Start runs from GitHub issues, pull requests, reviews, or custom webhooks. Use filters and run limits to keep automation focused.

CONNECTED TOOLS

GitHub
Linear
Webhooks
Stitch
OpenCode
Claude Code

Linear via custom webhooks · Harnesses run in sandboxes

Your tools, working in parallel.

Connect GitHub natively, or route Linear and your other tools through custom webhooks. Dispatch multiple agent runs, each with its own harness and sandbox.

Inside the workflow

Always-on agents. Ready when work arrives.

Stitch matches incoming events to your rules, then runs your chosen harness inside an isolated sandbox. The configuration lives alongside your code.

01 / EVENT SOURCES

Start where work happens.

  • GitHub

    Issues, pull requests, and reviews

  • Linear

    Issue updates via custom webhooks

  • Your tools

    Send a payload to a configured webhook

02 / STITCH TRIGGERS

Match. Filter. Dispatch.

Choose which events qualify, which agent should run, and where it should work.

Run limits & concurrency guards

03 / ISOLATED SANDBOX

Your agent. Its own workspace.

Your repository, setup scripts, and scoped credentials. The agent builds, tests, and reports back.

OpenCode Claude Code

Also supports Codex and Antigravity. Docker or Vercel Sandbox.

Defined in stitch-factory.yaml

Trigger excerpt. Define the referenced harness and sandbox in the same factory file.

triggers:
  - key: on-issue-labeled
    provider: github
    repository: acme/platform
    eventType: issues
    actions: [labeled]
    labels: [agent:build]
    harness: coding-agent
    sandbox: workspace
    initialPrompt: Implement the issue from the event context.
Read the configuration guide ↗

Give your agents a workflow.

Connect a repository and define your first trigger.