Introducing

Gremlin

Skip intro

Introduction

Gremlin is an AI developer that keeps working after you close the laptop. It replaces your day-to-day Claude Code with one conversation, on your desktop and in your terminal, and runs a sandboxed developer around the clock.

Local models do the cheap, high-volume work: drafting, testing and checking their own output. Claude plans the task and gives the final review. Every task ends as something you can read in a minute: a brief, a diff, the checks that ran and what it cost. Nothing is merged, deployed or posted until you approve it, from the desktop or from your phone.

Already have a .claude/ folder? Gremlin reads it as it is. Your skills, agents and settings come with you.

How it works

Each step goes to the cheapest model that can do it. Each role's model can be changed in settings; these are the defaults.

Who does each step of a task
Step Local modelThe gremlin ClaudeThrough the official CLI YouOne tap
PlanBrief and approach — Yesa call or two Answers questions
DraftCode, docs, fixes Yesas many tries as it takes — —
TestCompile, lint, tests Yesfailures loop back here — —
Self-checkReview its own diff Yes — —
Final reviewBefore it reaches you — Yesonce, at the end —
ShipMerge, deploy, post — — Approvedesktop or phone
gremlinone conversation

> fix the flaky login test and open a PR

Planning with Claude (brief, 1 call)

Brief ready. Handing to the local model.

Tinkering... edited 2 files. Running tests.

Tests pass. Lint clean. Local review clean.

Claude final review: looks good, one nit fixed.

Needs you: open pull request? [approve] [reject]

An illustrative session, not a recording.1

While you sleep

Every task is a saved state machine. A crash, a reboot or a usage limit only pauses it; it picks up from the last checkpoint. Gremlin spends Claude last, can spread work across several Claude accounts, and keeps the queue moving on local models while a usage window resets.

One night, four tasks

Illustration
22:00 01:00 04:00 07:00 Flaky test Docs Dependency Ticket APP-12

Claude appears twice per task: once to plan, once to review. Everything in between is local.

Safety

Default-deny sandbox. The agent runs where it can reach only the model endpoints and hosts you allow. No network, no secrets and no surprises until you open a door.

Keys stay home. Credentials live in your vault. The sandbox holds only a short-lived token for its own task, and never sees an API key or a password.

Approval first. Merges, deploys, external posts and ticket changes wait for a person, unless you wrote a per-project rule that says otherwise. A stop-all switch halts everything at once.

An audit trail. See what ran, which model did it, what it cost and who approved it.

Works with

What Gremlin runs on and connects to
Desktop macOS (Apple Silicon), Windows 10 and 11, Linux (Arch and Debian/Ubuntu)
Phone iOS and Android
Local models Any OpenAI- or Anthropic-compatible endpoint you add, on any hardware
Claude The official claude CLI, with your subscription login or an API key; several accounts at once
Trackers GitHub, GitLab, Jira, Linear
Extensions MCP servers, Agent Skills, Claude Code plugins, notifiers

Small core; everything else is an extension on one SDK.

Get started

Put a gremlin to work.

Installers are not released yet. Gremlin runs on your machine, with no telemetry and no analytics; your code goes only to the endpoints you configured.2

Download Coming soon Read the source

Footnotes

  1. The session is written to show the steps; real sessions show the same steps with your own task. ↩
  2. This site sets no cookies and loads nothing from other servers. ↩
  3. Gremlin is independent software. Claude is a trademark of its owner and is named here only as a supported model provider.