Quickstart

This guide has two parts. First you run the Demo pipeline, which uses the built-in Simulator harness and needs no agents, keys or repositories. Then you set up a real pipeline that works on a git repository and is started by issues from your tracker.

Part 1: the Demo pipeline

On first launch (when there are no pipelines yet), Jimothy creates a pipeline called Demo: Issue to PR (simulated). It runs in an Empty folder workspace and every agent step uses the Simulator, which fakes realistic agent output: tool calls, thinking, cost and tokens.

1. Open Dashboard. With no runs yet, it shows a welcome card. Click Run the demo pipeline. (Later you can use New run on the Dashboard or Runs page, or the ⌘K command palette.)

2. The Start a run dialog opens with the Demo pipeline selected. Enter a Task title, for example Add input validation to the signup form. Issue key, Issue URL and Description are optional; without a key, Jimothy assigns one like TASK-1. Click Start run (or press ⌘↵).

3. The run page opens. Watch the pipeline graph and the step list:

   • Triage and Plan run one after the other.
   • Implement runs next, then Unit tests and Lint & typecheck run in parallel, because both depend only on Implement.
   • Code review waits for both. On its first pass the Simulator reviewer ends with VERDICT: CHANGES_REQUESTED, which does not match the step’s pass pattern, so the step fails and the run loops back to Implement. Implement, the tests, lint and the review run again; this time the review approves.

4. The run stops at Human approval with status Needs approval. You also get a desktop notification. Read the message, optionally type a comment, and click Approve.

5. Open pull request runs (in the demo it only echoes a fake PR URL). The URL is detected and shown as a PR #… button in the run header. The run ends as Succeeded.

Click any step to see its Logs, Output, rendered Prompt/Command/Message and Details (duration, tokens, cost, attempts). Try Retry from here on a finished step to re-run it and everything downstream.

Tip

The Simulator’s behavior depends on the model you pick for a step: fast (short delays), realistic (multi-second, reviewers request changes on the first pass) and flaky (fails the first attempt, succeeds on retry). It’s useful for dry-running your own pipeline designs before pointing them at a real agent.

Part 2: a real pipeline

You’ll need a local git clone of a repository, at least one agent CLI installed and signed in (see Installation), and, to open PRs, the gh CLI.

1. Check your harnesses. Open Harnesses. Installed CLIs show as available; the rest show why they weren’t found. Click Re-detect after installing something. For the API harnesses, click Configure and add an API key. See Harnesses.

2. Create the pipeline. Open Pipelines → New pipeline and pick the template Feature: Plan → Build → Review → PR. It plans with Claude Code (opus), implements with Claude Code (sonnet), runs your tests, has Codex review (looping back on requested changes), waits for your approval, and opens a PR. If you don’t have Codex, select the Cross-model review step and switch its Harness.

3. Point it at your repository. In the editor, select Pipeline settings. Under Workspace, choose Git worktree and set Local repository to your clone (use Browse). Check Base branch (default main) and Branch name template (default jimothy/{{issue.key | slug}}).

4. Set the test command. Under Variables, change testCommand from npm test to whatever runs your tests, for example pytest -q.

5. Save (⌘S). Save is disabled while the editor lists problems; fix them first.

6. Run it manually. Click Run, give the task a title and description, and start it. Jimothy creates a worktree on a new branch in the workspaces folder, and the steps run there. Approve at the gate to push and open the PR.

7. Connect your tracker. Open Accounts and Sign in to Linear, Jira or GitHub. See Accounts.

8. Add a trigger. Open Triggers → Add trigger, choose Linear, Jira or GitHub, pick the account, what to watch (for example the label jimothy), and set Runs pipeline to your new pipeline. Click Preview matching issues to check the filter, then Save trigger. From now on, a matching issue starts a run. See Linear, Jira or GitHub, and Write-back to comment on and transition the issue automatically.

9. Get notified. Desktop notifications are on by default for run success, failure, approvals and trigger errors. Under Notifications → Add channel you can add Slack, Discord, Teams, ntfy (phone push) or a webhook. See Notifications.

Caution

Issue text becomes agent input, so anyone who can create or label matching issues can influence what agents do. Only point triggers at trackers where you trust who can do that, and keep an approval step before anything that pushes or deploys.

Where to go next

• How it works: what happens during a run, step by step.
• Pipelines overview: the editor and all pipeline settings.
• Templates: everything you can put in prompts and commands.
• Guide: Linear issue to pull request.