Jimothy
Download
Your desktop dev crew

Any trigger. Any agent.
You approve what ships.

Jimothy chains Claude Code, Codex, your tests and your shell into pipelines that run on your own machine. Start one from a Linear, Jira or GitHub issue, a schedule or a webhook, and nothing ships until you approve it.

Download for freeTry it in your browser

macOS · Windows · Linux · Free

Example · Issues → pull requests

LinearENG-142Add CSV export to the reports pagejimothy
Pipeline
  1. Plan Claude Code · opus
  2. Implement Claude Code · sonnet
  3. Run tests npm test
  4. Review Codex · ↻ 1
  5. Human approval you
Pull requestacme/app#318ENG-142: Add CSV export to the reports pageIn Review
See it end to end

From an empty app to a merged-ready PR

This is a recording of the real app. It sets up a project, builds a pipeline, connects Linear, adds a trigger, labels an issue and watches Jimothy do the rest.

Recorded from the real app · project → pipeline → Linear trigger → run

Recorded with npm run record-demo. To make the recording reproducible, the agent steps use Jimothy's built-in Simulator harness and Linear is mocked.

Use cases

What people build with it

Each one is a pipeline you can import today. Some ship code, and some never touch a repository: support replies, product updates and sales leads.

For engineering

Linear → Pull request

Issues → pull requests

Hand off a Linear, Jira or GitHub issue. Agents plan, build and review it, and you approve the PR.

See how it runs →Schedule → Pull request

Nightly maintenance

A schedule updates dependencies overnight, fixes what breaks, and opens a PR only if something changed.

See how it runs →GitHub → Comment

Specs from vague issues

A fuzzy issue gets a spec with acceptance criteria and open questions, posted back after you approve it.

See how it runs →

Beyond engineering

Webhook → Reply

Support reply drafts

New tickets are triaged and answered in your voice, within your policies. You approve before anything is sent.

See how it runs →Schedule → Slack

Weekly product updates

Every Friday the week’s changes become a customer-facing “What’s new” post, ready to approve and publish.

See how it runs →Webhook → CRM

Inbound lead research

Each contact-form lead gets a cited research brief, a fit rating and a first reply before you’ve opened the email.

See how it runs →
Any trigger → anything

Build your own

Agent, shell and approval steps in a DAG, started by an issue, a schedule or a webhook. Or describe it and let Jimothy draft the pipeline.

Pipeline docs →
How it works

Four pieces, set up once

An account connects your tracker. A trigger decides what starts a run. A pipeline says what happens to them. Runs do the work and report back.

  1. 01

    Connect an account

    Sign in to Linear, Jira or GitHub once. One account can feed any number of triggers.

  2. 02

    Add a trigger

    Choose labels, a JQL query, a repo, a cron schedule or a webhook. Preview matching issues shows exactly what will run.

  3. 03

    Pick a pipeline

    Start from Feature: Plan → Build → Review → PR or build your own out of agent, shell and approval steps.

  4. 04

    Approve & ship

    Watch the run live. When you approve at the gate, the result ships: a pull request, a comment, a message.

Interactive demo

Go ahead, label the issue

This is a click-through of a real run. Label the issue, watch the review loop send work back once, then approve or reject at the gate. Click any step to see its logs or the prompt it was given, rendered with Jimothy's own template engine.

Jimothy — Runs › #12
PipelineFeature: Plan → Build → Review → PR
Branch—
StatusWaiting for trigger
Cost$0.00
Plan
Logs stream here once the run starts. Click any step to inspect it.

More interactive demos →

Features

Pipelines, not a chain of prompts

Jimothy has what you'd expect from CI, like retries with backoff, timeouts, runIf conditions and continueOnError. The steps just happen to be agents.

Any harness, per step

Plan with Claude Code on Opus, implement on Sonnet, review with Codex. Every step picks its own harness, model and prompt, and custom CLIs plug in through an argument template.

Real pipelines

Steps form a DAG: tests and lint run in parallel and join afterwards. Reviewers that say CHANGES_REQUESTED send work back to the implementer with their feedback attached.

Human gates

Approval steps pause the run until you approve or reject, from the app, the tray or your phone. Your comment is passed to the steps that run next.

Isolated workspaces

Each run gets its own git worktree and branch, a fresh clone or an empty folder, so runs can happen in parallel without stepping on each other.

Triggers that write back

Linear, Jira, GitHub Issues, cron and webhooks. Jimothy comments on the issue and moves it, for example to In Review, when a run starts, succeeds or fails.

Watch it live

A live pipeline graph and streaming logs show tool calls, thinking and results. You can retry from any step, cancel the whole process tree, or open the workspace in your editor.

Notifications everywhere

Desktop, Slack, Discord, Teams, ntfy push and generic webhooks, filtered by event and pipeline. There is also an inbox, a tray menu and a dock badge.

Local-first

Runs happen on your machine with your tools. Secrets are encrypted with the OS keychain and your data stays in plain JSON files.

Harnesses

Use the agents you already have

Jimothy finds the CLIs you have installed, including ones on your login-shell PATH. Change a step's harness below to see the exact command Jimothy would run.

Claude CodeOpenAI Codex CLIGemini CLICursor AgentGitHub Copilot CLIAiderOpenCodePiAmpGooseClaude APIOpenAIOpenRouterOllamaLM StudiovLLMYour own CLI
Pipeline editor › Harness & model
1Plan
2Implement
3Review
What Jimothy runs for each step built with the app's own argv builder
Local-first
Your code never leaves your machine unless you push it
Agents run as your user, in folders you choose. Tracker tokens and API keys are encrypted with the OS keychain. Runs, logs and settings are plain JSON and JSONL files that you own.
  • The webhook server listens only on 127.0.0.1 by default, and Linear and GitHub payloads are HMAC-verified
  • Values interpolated into shell steps are quoted, so issue text can't inject commands
  • Worktree mode and approval gates keep changes from being pushed before you've looked at them
Read the security notes
# macOS: ~/Library/Application Support/Jimothy/factory
settings.json
projects.json
pipelines.json
connections.json   # secrets encrypted with the OS keychain
triggers.json
runs/
  <run-id>/
    run.json
    logs/plan.1.jsonl
workspaces/
  run-12-eng-142/   # git worktree on jimothy/eng-142
Let Jimothy dig through your backlog
Raccoons do their best work at night. Jimothy can too.
Download JimothyRead the quickstart