Code: from GitHub issue to merged pull request

See your repositories' issues and pull requests, launch a Claude Code session on an issue, and follow it as it works. GitHub stays the source of truth: review and merging happen there.

Needs a personal GitHub account, a passkey on your device, and paid GitHub (for private repositories) and claude.ai plans.

From issue to pull request

  1. Issue

    On GitHub, as written. The session works on the issue's text and its comments.

  2. Launch

    Choose a preset and press Launch. Your passkey approves the exact text that is sent.

  3. Session

    Live progress: its stages, its questions for you, its plan and its pull request.

  4. Pull request

    You review it and merge it on GitHub, once its checks pass.

What Code does

Sessions across repositories

One page shows every session you launched, in every repository, with notifications on your devices when a session asks a question, finishes or fails.

Launch presets

Save the steps and agents you launch with, each agent with its own model and effort, and pick a preset in one click.

Price checks for Work

With Work on, a session reads a project's private repository and estimates a client's request in hours, for you to price.

The setup app

Thistlewick Setup prepares each repository for sessions, on macOS, Windows and Linux. It shows every change and asks once before it writes.

What it never does

What you need

  • A personal GitHub account.
  • A passkey on your device.
  • A second GitHub account for the session bot.
  • A paid GitHub plan for private repositories.
  • A paid claude.ai plan.
  • Claude Code, once.
  • About 20 minutes once, then 10 per repository.

Not yet: organisation accounts, Copilot and Codex.

Free during early access.

Use Code on its own, or with Work beside it.