CodeGaud · Vol I · Beta opens 2026
No. 001 Issued from a MacBook at 03:14

Describe what you want to build. Wake up to a shipped, hosted product.

CodeGaud is overnight autopilot for your development backlog. You describe the project. It interviews you, writes the brief, generates the ticket backlog, and ships tickets while you sleep — on isolated infrastructure, with your own Claude API key. You approve on your phone. The result deploys to your hosted app automatically. If it gets stuck, it waits.

It started on April 20 · 2026. A single operator — running a bash daemon on a MacBook, a PHP MCP server on shared hosting, and a mobile PWA — shipped three tickets autonomously, closed four as "work already done upstream," caught a five-deep escalation cascade, patched the daemon mid-flight, and re-shipped. All from a phone. All while making coffee, driving, eating dinner.

Today the same setup runs around the clock. The same single operator. Fifty to seventy tickets shipped or escalated every day. Approvals happen on the phone. Execution happens overnight, between meetings, on the way to the gym.

This is not a research preview. It is a production workflow that exists today, built by one person, on consumer-grade infrastructure, running daily.

The dominant failure mode in autonomous development is not the agent — it is ticket quality. Every re-queue loop traced back to the same root causes: external references the daemon could not resolve, forbidden paths in scope, ambiguous acceptance criteria, assumed infrastructure that did not exist.

CodeGaud's Brief Processing Module eliminates all of these at the source — before a ticket ever enters the queue. No competitor is building this. It is where the product lives.

§ 02 · The Loop

How a ticket goes from idea to live, hosted product.

Brief → backlog → build → approve → deploy → serve → iterate. One platform. One bill. One trust boundary. The loop that was always the promise — now closed.

01
Read the next eligible ticket
Control plane
02
Plan in an isolated container
Fly Machine · BYO API key
03
Push approval to your phone
Mission Control PWA
04
Execute on a codegaud/* branch
HMAC-signed audit log
05
Push back to your repo
PR or merge per config
06
Deploy to your hosted app
Zero-downtime · Cloudflare SSL
07
Wake to a morning digest
Files · Diff · Uptime · Done
§ 03 · Why this is different

Six wedges. Each one a thing nobody else has shipped.

There is no shortage of agentic developer frameworks. CodeGaud does not ship primitives — it ships a finished workflow with the rough edges already abraded.

01

Brief-to-backlog pipeline

Describe what you want to build. CodeGaud generates the entire ticket backlog — scoped, sequenced, risk-tagged, pre-flight validated. No ticket writing. No competitor has this.

02

Mobile-first approval UX

The phone is mission control. The approval card is the atomic unit of the product. Push notifications, haptic feedback, dark mode by default.

03

Build + host in one platform

Brief → build → deploy → serve → iterate without leaving CodeGaud. The loop that was always the promise, now closed in a single platform.

04

Customer brings their own API key

Margin structure is stable. No surprise bills. We never sit between you and Anthropic. Your key, encrypted in your container, decrypted only at runtime.

05

The approval matrix is the product

Auto-approve rules, trust graduation, risk gates, PANIC guards. Three weeks of production scar tissue become every customer's defaults on day one.

06

Opinionated for solo and small

Shaped for one to ten people. The product has a personality: it respects your sleep, your budget, and your timeline. It will not ship without your nod.

§ 04 · A common question

"Isn't this just /remote-control?"

Both put Claude on your phone. The similarity ends there. Anthropic's /remote-control is a synchronization bridge — your laptop has to be on, your terminal has to be open, and every decision still pauses for you. Their own PM frames it as "take a walk, see the sun, walk your dog without losing your flow." It's mobility for an active session.

CodeGaud is mode-different. You don't drive a session — you describe what you want to build. We write the brief, generate the backlog, and ship tickets while you sleep on cloud infrastructure your laptop has nothing to do with. Approvals are risk-tiered and budget-capped, not per-action. The result deploys to a hosted, running app you own.

/remote-control
Anthropic · Feb 2026
  • ModeSynchronous pilot
  • Where it runsYour laptop, on & awake
  • InputYou type prompts
  • Approval modelPer-action permission gate
  • Backlog systemNone
  • Brief → ticketsNone
  • HostingNone
  • Best forChecking in mid-flow
CodeGaud
The autopilot above it
  • ModeAsynchronous autopilot
  • Where it runsCloud Fly Machines
  • InputYou describe; we plan
  • Approval modelRisk-tiered auto-approve matrix
  • Backlog systemNative & first-class
  • Brief → ticketsThe Brief Processing Module
  • HostingIncluded on every paid tier
  • Best forGoing to sleep, waking to ships

Take a walk, or go to sleep. Different products.

§ 05 · One price. Whole stack.

Hosting included. Not as an add-on. Not as a bundle.

The price covers the complete CodeGaud stack: brief processing, autonomous build, hosting, and deployment. Bring your own Claude API key. Pay Anthropic directly for tokens.

Starter
$0forever
Trying it out
  • 1 project
  • 20 approvals / month
  • Brief Generator (1 brief)
  • Hosted on slug.codegaud.com
  • 14-day audit log
Studio
$149/month
Small teams & agencies
  • 10 projects · 3 seats
  • Ticket Portal
  • All adapters
  • Unlimited custom domains
  • 1-year audit log
  • 99.5% hosting SLA
Enterprise
Talkto us
Compliance & scale
  • Unlimited everything
  • SSO / SAML
  • Self-hosted plugin option
  • BAA & SOC 2
  • 99.9% SLA
  • Dedicated Postgres
§ 06 · Origin

An existence proof, not a pitch deck.

Shane is the sole developer of MyScribe, a Human-Hybrid-AI coaching SaaS. To ship the product on a solo founder's schedule, he built an autonomous development harness that runs overnight, takes tickets from Linear, writes code against his production codebase, and posts approval cards to his phone. He is productizing it because other founders kept asking if they could use it too.
Founder · Shane · April 2026
§ 07 · Application · By Invitation

Apply for the founding cohort.

We're hand-picking a small group of founding members before the public launch. We read every application. A select few will receive a direct reach-out with terms — founding membership is a tier of service we don't offer publicly, and we discuss it individually with each invited founder.

No spam · We reply only if it's a fit