Open source · Apache 2.0

Run coding agents through your real engineering loop

A self-hosted, chat-driven IDE for Claude Code and Codex — the whole loop, from running app to merged PR, in one place.

Get started →View on GitHubGitHub

Docker · self-hostedClaude Code / CodexRunning app → merged PR

FIG. 1 — THE ENGINEERING LOOP

Build

Verify

Preview

Merge

Deploy

commit · a1f9c2e

▸ Build · writing code

edit limiter.ts +13
edit window.ts +21
edit config.ts +4
✓ 3 files · +38

▸ Verify · self-check

↻ screenshot
nudge → fix
✓ matches ×2

▸ Preview · live app

localhost:4123

Todos

✓ Write tests

✓ Add rate limit

Ship release

Add a task…+

▸ Pull request

#214 Add rate limiter
feat/limiter → main
+38 · 3 files

▸ CI · checks

lint · tests · typecheck

▸ Merge

#214 → main
squash · 1 commit
✓ merged

▸ Deploy

deployed · v1.4
live · healthy

Build → Verify → Preview → PR → CI → Merge → Deploy

All inline

SShipIt

Your real engineering loop.
Inline.

Build, preview, merge, deploy — the whole loop, without leaving ShipIt.

FIG. 2 — WHY SHIPIT EXISTS

The premise

Coding agents are the easy part

You already have Claude Code or Codex. The hard part is everything around them — the isolated environment, the running app to test against, the parallel branches that never collide, the whole PR → CI → deploy → review loop. ShipIt is the surface that ties it all together, so you build, review, and ship in one place instead of stitching it together yourself.

FIG. 3 — CAPABILITY SCHEDULE

What you get

Everything the agent needs to ship real software

§01

Real app feedback

Every session runs its own instance of your full app stack, so the agent can build, run, and fix before you preview and merge.

PER-SESSION STACK

§02

Bring your own agent

Claude Code or Codex, on the subscription or API key you already have. Connect several accounts and ShipIt rolls to the next before a usage limit stops you.

AGENT-AGNOSTIC

§03

Parallel & isolated

Many agents at once, each in its own sandboxed container, branch, and workspace — concurrent work that never collides.

SANDBOXED · N-UP

§04

Self-hosted

On an always-on server you own, or local on your laptop. Docker end to end, so previews and follow-up work keep running after you close the lid.

DOCKER · ALWAYS-ON

§05

The GitHub loop, inline

Work with PRs, CI, deploys, reviews, and issues without leaving ShipIt — branches, checks, and merge state render right in chat.

PR · CI · DEPLOY

§06

Ship from your phone

Mobile-first, with first-class voice. Dictate prompts and hear spoken summaries when the agent finishes a turn or needs you.

MOBILE-FIRST · VOICE

FIG. 4 — DEPLOYMENT PROCEDURE

Install

Run it locally, then host it for real

Try it on your laptopOne command, local Docker

§INSTALL · LOCAL DOCKERTARGET → http://localhost:4123

$ bash <(curl -fsSL https://raw.githubusercontent.com/nikzlabs/shipit/stable/deployment/local/setup.sh)

Runtime

Docker + Compose v2

Credentials

Claude / Codex sub or API key

Then host it always-onWhere ShipIt is meant to live

Recommended

§DEPLOY · ALWAYS-ON VPSUBUNTU HOST · ROOT

$ ssh root@<server-ip>

$ sudo bash -c "$(curl -fsSL https://raw.githubusercontent.com/nikzlabs/shipit/stable/deployment/vps/setup.sh)"

Stays up when your laptop is closed. The provisioner installs Docker, tunes host limits, and optionally wires Cloudflare Tunnel and Tailscale — no open inbound ports. See the VPS guide →

FIG. 5 — THE CLOSED LOOP

The build, review, ship, and debug loop stays in the conversation

Get started →See all features View on GitHub