Hatch, from egg to flight.

Getting started

Download Hatch, install it and create an account. Onboarding creates your first project. Every project has a short key (e.g. HAT), so tasks are called HAT-1, HAT-2 … Use these refs in commits, notes and when talking to agents.

In the project settings, add the local folder of your code — then VS Code, Terminal, Claude Code and Codex start right inside the project (the Work button).

Quick capture

Press Ctrl Alt Space anywhere in Windows, type a thought, hit Enter. The AI decides what it is and where it goes:

💡Use # to pick a project directly. Offline? Captures are queued and sent when you're back.

Connect Claude Code

One click: in the app, open Agents → Claude Code → Set up automatically. Hatch creates a personal token, registers the MCP server and installs the hatch skill.

Manually (create a token under Settings → Claude & Codex):

claude mcp add --transport http --scope user hatch https://api.hatch.wisak.at/mcp \
  --header "Authorization: Bearer <YOUR_TOKEN>"

Then, in Claude Code: /mcp__hatch__work — or simply say “Check Hatch for what to do next, and do it.”

Connect Codex

One click: Agents → Codex → Set up automatically. Hatch adds itself to ~/.codex/config.toml and appends the workflow to ~/.codex/AGENTS.md.

Manually, in %USERPROFILE%\.codex\config.toml:

[mcp_servers.hatch]
url = "https://api.hatch.wisak.at/mcp"
http_headers = { "Authorization" = "Bearer <YOUR_TOKEN>", "X-Hatch-Agent" = "codex" }

The agent workflow

This is the loop every Claude or Codex session runs — so no session ever starts with “where were we?”

1. Find the project — hatch_resolve_project with the current folder.
2. Read the context — open tasks, the last handoff, notes, commits.
3. Start a task, build it, test it, commit with fixes HAT-12.
4. Complete the task, add follow-ups, write docs.
5. Always write a handoff — the next session picks up right there.

🥚Mark tasks For Claude, For Codex or Any agent — they jump to the top of hatch_next_tasks.

GitHub

Create a personal access token with repo and read:user and paste it under Settings → Connections. Then pick a repo under Project → Git. Hatch checks for new commits, pushes and PRs every three minutes. For instant updates, add a webhook to https://api.hatch.wisak.at/v1/github/webhook (content type application/json).

A commit containing fixes HAT-12 or closes HAT-12 checks the task off automatically.

AI (Gemini)

Get a free key in Google AI Studio and paste it under Settings → AI. It's stored encrypted on the server. The AI gives you a daily briefing, a chat that can act (Ctrl J), sorting of quick captures, auto-planning, task breakdowns, and commit & weekly reviews.

⚠️With a free key, Google may use your inputs to improve its services. For sensitive projects, use a paid key — or no AI at all. Hatch works fine without it.

Calendar

Hatch → your calendar app

Settings → Calendar → Subscribe. Apple Calendar on Mac: File → New Calendar Subscription. iPhone: Settings → Calendar → Accounts → Add Account → Other → Add Subscribed Calendar.

Your calendar → Hatch

Add an ICS link (iCloud: share a calendar → Public Calendar). Events show up in the calendar and planner, and auto-planning plans around them.

Shortcuts

API

Everything the app can do also works over REST at https://api.hatch.wisak.at/v1. Authenticate with Authorization: Bearer <token>. Quick reference: api.hatch.wisak.at/v1/docs.

# Create a task
curl -X POST https://api.hatch.wisak.at/v1/tasks \
  -H "Authorization: Bearer $HATCH_TOKEN" -H "Content-Type: application/json" \
  -d '{"title":"Prepare release","dueAt":"2026-11-10"}'

# Let the AI sort a thought
curl -X POST https://api.hatch.wisak.at/v1/captures -H "Authorization: Bearer $HATCH_TOKEN" \
  -H "Content-Type: application/json" -d '{"text":"test backups tomorrow #server"}'

Live changes stream as Server-Sent Events from /v1/events.