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
Section titled “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.
-
Open Dashboard. With no runs yet, it shows a welcome card. Click Run the demo pipeline. (Later you can use New run at the top of the sidebar, ⌘N, or the ⌘K command palette.)
-
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 likeTASK-1. Click Start run (or press ⌘↵). -
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.
-
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.
-
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.
Part 2: a real pipeline
Section titled “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.
-
Check your harnesses. Open Settings (the gear at the bottom of the sidebar, or ⌘,) and the Harnesses tab. Installed CLIs have a green dot and show their version; select one that’s missing to see why it wasn’t found. Click Re-detect after installing something. For the API harnesses, click Configure and add an API key. While you’re there, switch off models you don’t want to see in the model pickers. See Harnesses.
-
Create a project and the pipeline. Click the + next to Projects in the sidebar. The new project’s Settings tab opens: give it a name, set its Workspace to Git worktree with Local repository pointing at your clone, and Save. Then click + on the project in the sidebar (or New pipeline on its Pipelines tab) 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. -
Check the workspace. The pipeline uses the project’s workspace. In the project’s Settings tab, check Base branch (default
main) and Branch name template (defaultjimothy/{{issue.key | slug}}). (Without a project, set the same fields under Pipeline settings → Workspace in the editor.) See Projects. -
Set the test command. In the pipeline editor’s Pipeline settings → Variables, change
testCommandfromnpm testto whatever runs your tests, for examplepytest -q. (Or set Commands → Test on the project before creating the pipeline; the template then uses that.) -
Save (⌘S). Save is disabled while the editor lists problems; fix them first.
-
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.
-
Connect your tracker. Open Settings → Accounts & integrations and click Sign in under Linear, Jira or GitHub (or type
sign inin the ⌘K palette). See Accounts. -
Add a trigger. Open the project’s Triggers tab, click 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. (To collect issues and run them in an order you choose instead, set When it finds an issue to Add to a board; see Boards.) See Linear, Jira or GitHub, and Write-back to comment on and transition the issue automatically. -
Get notified. Desktop notifications are on by default for run success, failure, approvals and trigger errors. Under Settings → Notifications → Add channel you can add Slack, Discord, Teams, ntfy (phone push) or a webhook. See Notifications.
Where to go next
Section titled “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.