Question 1

What exactly is a holm?

Accepted Answer

An isolated copy of your repository for one ticket: its own branch and folder (copy-on-write clone on APFS, or a git worktree), its own .env, database and preview URL, plus a coding agent that already knows the ticket. Archive it and it goes to drydock; the branch stays.

Question 2

Which coding agents does it drive?

Accepted Answer

Cursor, Claude Code and Codex — over ACP where available, otherwise in a terminal. The agent receives the full ticket, including images and attachments, and gets a small MCP for the in-app preview.

Question 3

Does Keelholm commit, merge or log time on its own?

Accepted Answer

No. The coding agent writes code inside its holm; Keelholm itself prepares the draft pull request, the time suggestion and the Jira actions, and you press the button. The Harbormaster only reads and reminds.

Question 4

Jira or GitHub?

Accepted Answer

Both. Jira Cloud tickets or GitHub issues. Time can go to Jira worklogs or Odoo timesheets.

Question 5

Where does my code go?

Accepted Answer

Nowhere new. Keelholm runs on your Mac; credentials live in the Keychain. The only outbound traffic is to the services you already use — your tracker, GitHub and the agents you pick.

Question 6

Which Macs?

Accepted Answer

macOS on Apple silicon and Intel. The app is signed and notarized and updates itself.