ChangelogWhat's new
Every Jimothy release, newest first. The app tells you when an update is ready, or grab it from the download page.
- Steps can now see everything earlier steps wrote:
{{steps.<id>.output}} is no longer cut to its last 20,000 characters. Long outputs show a preview on the run page, with Show the full output.
- Agent and shell steps keep the documents and images they create (design docs, mockups, screenshots, HTML, PDFs) as artifacts. Preview them on the step's new Artifacts tab, in its logs and details, and right on the approval banner, even after the workspace is cleaned up. Later steps get their paths as
{{steps.<id>.artifacts}}.
- Archive or delete notifications one at a time in the inbox. Archived ones move to an Archived view, where you can restore them.
- Integrations and notification channels now show their company logos (Linear, Jira, GitHub, Slack, Discord, Todoist, TickTick, ntfy).
- Slack triggers now only accept commands from the Slack members you list. Approving steps and answering questions from Slack is limited to the approvers you set on the trigger or the Slack account. Add the member IDs to existing Slack triggers to keep using them.
- Board/output fixes, settings & harness UI polish, window state
- EULA on first launch and opt-in usage analytics (ECH-213, ECH-218)
- Steps can move, label and comment on their issue in Jira, Linear or GitHub from "After this step", with statuses from the pipeline's project.
- Projects can set issue status rules (order, allowed steps back, statuses never to move into or out of) that every issue move follows.
- Collapsible sidebar: collapse the left sidebar to a slim rail of icons with the button at its top or ⌘B.
- Command palette: everything in Ask Jimothy is in ⌘K too: new chat, previous chats (search them by title), pop-up / side panel / desktop, and chatting about one project.
- Ask Jimothy: click the raccoon in the bottom-right corner (or press ⌘J / Ctrl+J) to chat with Jimothy. Ask why a run failed, have it retry or fix a step, or set up projects, pipelines, triggers, boards and accounts. It runs on your own Claude Code, Codex or API harness, and asks you before deleting or cancelling anything.
- Voice input: talk to Jimothy with the mic button. Speech is transcribed on your computer with Whisper (downloaded on first use), or with an OpenAI-compatible transcription API if you choose one in the chat settings.
- Put Jimothy where you want him: the new placement button in the chat header moves the chat between a pop-up, a side panel docked on the right of the window (resizable, and collapses to a slim bar), and on the desktop, where Jimothy floats on top of your other apps. Click the head to chat. You can also drag the corner button out of the window to undock him, and drag the head back onto the window's corner to dock him.
- Previous chats: every conversation is saved. Open the history to go back to a chat and keep going (Claude Code and Codex remember everything, even after a restart), rename it, or delete it.
- Chat about one project: pick a project under the message box and Jimothy sticks to that project's pipelines, runs, triggers and boards, or choose All projects.
- You can now drag to resize board columns and groups, the Runs table's columns, and the panes on the run page, pipeline editor, dashboard and settings. Sizes are remembered; double-click a handle to reset it.
- Fixed: the left sidebar now scrolls when you have more projects than fit in the window, and Inbox and Settings stay in view at the bottom.
- Boards: group branches. An in-order group can build up one branch: each card starts from the work of the cards before it, opens its pull request against the group branch, and is merged in when you approve it. When the group is done, open one pull request from the group branch to main. How it works
- Fixed parallel board cards sometimes failing to start with "could not lock config file".
- Use Jimothy from your AI assistant. Turn on Settings → Remote → MCP server and connect Claude Code, Claude Desktop, Codex, OpenCode, Cursor or Devin. Then ask it to start a pipeline, tell you what's waiting for approval, approve a step, or build a new pipeline or project for you. Setup guide
- Environment variable values are hidden from AI assistants. Click the eye next to a variable (in Settings, a project or a step) to let them read it. More
- New Appearance tab in Settings with 21 color themes, including One Dark Pro, Dracula, GitHub, Monokai, Solarized, Nord, Tokyo Night, Catppuccin and Gruvbox. Pick one for dark mode and one for light mode, and Jimothy follows your OS between them.
- New Boards page. Point a trigger at a board and the issues it finds wait for you to put them in order. Jimothy then works through them group by group, and each card waits for your approval before the next one starts.
- Projects in the sidebar. Dashboard, Runs and Boards stay at the top; each project lists its pipelines, boards and triggers, shows what's running, and opens with tabs for Pipelines, Triggers, Boards, Runs and Settings. Sections fold, the sidebar can be widened, and the arrow keys move through the tree.
- Settings is now a window (⌘,) with General, Accounts & integrations, Harnesses, Notifications and Remote tabs. It warns before you lose unsaved changes.
- Harnesses show their logos and list their models with a switch each, so you can hide models you don't use from the model pickers. You can pick a logo for harnesses you add, and update badges clear once you've updated a CLI.
- The command palette (⌘K) can create pipelines, boards, projects and triggers, open the inbox, and collapse or expand the sidebar.
- Pipeline flowcharts on the Pipelines page start collapsed.
- Slack tokens are now encrypted with your OS keychain, like other account credentials. Existing Slack accounts are encrypted automatically the first time you open this version. Saved credentials the keychain can't read (for example after moving your data to another machine) are no longer erased when the app saves.
- New Integration step: create, comment on or complete Todoist tasks from a pipeline.
- Every step can now run actions in other apps when it succeeds or fails ("After this step").
- New Todoist trigger: start runs from tasks matching a filter, then comment on them and complete them when the run finishes.
- Custom webhook notifications now include the step's name, status and output, ready for Zapier, Make and n8n.
- New TickTick integration: start runs from TickTick tasks, comment on and complete them when runs finish, and create, comment on or complete tasks from a pipeline.
- Two-way Slack:
- start runs with
/jimothy or @Jimothy;
- follow every run in one Slack thread;
- approve steps with buttons;
- post messages, or ask a question and wait for the reply, as pipeline steps.
- Mac app (installed from the DMG): updates now download in the background, and you restart to install them. No more re-downloading the DMG.
- Point a project at a folder that holds several git repositories: runs get a worktree of each, track which ones they change, and can run tests once in each changed repository with its own commands and base branch.
- Keep a repository's setup, test and lint commands in a
Jimothyfile committed with the code.
- New worktrees get your
.env files (or whatever .worktreeinclude lists) copied in.
- Fix a run in place: edit a step's harness, prompt or command for the rest of the run, or skip a step and carry on.
- Triggers can label the issues they've run, so removing the label re-runs an issue, and you can pick processed issues to run again.
- The Feature template creates an issue branch from the latest base before implementing.
- Fixed Codex steps failing immediately with newer Codex versions.
- The Feature template's implement step now stays on the branch the run checked out, instead of going looking for a different one.
- When a trigger moves an issue on start, success or failure, you now pick the status from a dropdown of your Jira, Linear or GitHub stages instead of typing it.
- Jira triggers can watch a project you pick from a list, with JQL as an optional extra filter.
- Triggers can belong to a project and appear under it in the sidebar, and the Pipelines and Triggers pages can be filtered by project.
- Run a pipeline inside another pipeline. The new Pipeline step starts another pipeline as part of a run, hands it values from earlier steps, and waits for it to finish. Build a shared "review and ship" pipeline once and reuse it everywhere.
- Branch with Condition steps. Check a step's output, for example "the triage says it's a bug", and send the run down a yes or a no path. The path not taken is skipped.
- See your data while you build. The pipeline editor shows real values from a recent run next to each step: the issue, what earlier steps produced, and your variables. Click any value to drop it into a prompt or command.
- Preview prompts before you run them. Switch a prompt or command to Preview to see it filled in exactly as the step will receive it.
- Catch mistakes as you type. A misspelled step or variable name, or a step that hasn't run yet at that point, is flagged with a suggested fix.
- See what each attempt got and gave. On a run's page, the Data tab shows each attempt's input next to its output, including every pass of a review loop. Edit with this data opens that step in the editor with the run's values loaded.
- The Mac app is now signed and notarized by Apple, so it opens without the "Jimothy is damaged" or "Open Anyway" warnings.
- Build a native Windows installer and run shell steps in Git Bash
- Let approvers pick options from an earlier step's output
- Keep harness models current and flag outdated CLIs
- Offer approval choices from a step's full output
- Check for new versions and point users at the right update
- Update the Homebrew cask on each full release
- Publish installers to stable latest/ paths on R2
- Fix Windows test failures
- Drop Windows from release builds for now
Release notes are on their way. Meanwhile, the download page always has the latest version.
