Skip to content
Nrth Star
Apply for access
Dazza
GitHub

Stop operatingyour agent.Start managing it.

Dazza turns Claude Code or Codex into an engineer you manage. Brief it once. It plans the work on its own project board, gets on with it, and texts you when there's something to see.

git clone https://github.com/harrison-bbb/dazza && cd dazza && pnpm install && pnpm build && npm link
Read the source on GitHub
Drives
Claude Code or Codex
Plans on
A project board, run locally
Reports on
Slack or Telegram
Licence
MIT, open source

Same agent.
Different job.

Coding agents are brilliant and needy. Left alone they stall on a question or guess, so you end up sitting there feeding them. Dazza gives the agent you already use a manager: you.

Operator

  • Watching the terminal
  • Approving every command
  • Re-explaining the project each session
  • Finding out it went sideways an hour ago
  • Untangling its branches

Manager

  • Brief it once, like a new hire
  • Sign off on the plan, on a real board
  • Get on with your day
  • Hear from it when there's something to see
  • Approve the work, or send it back

Brief it. Sign off.
Walk away.

Brief it.

$ dazza

Talk it through like a first meeting with a new engineer. It reads the codebase, asks what's live and what can't break, and plays back what it'll build before it writes a word of the plan.

dazza — ~/code/tidepoolzsh
> add magic-link sign in, and let people export their notes as markdown. I'm out this afternoon.● Before I plan it: is Tidepool live? Real users, real data?> ~200 users. don't touch prod.● Noted as a guardrail. The plan's on the board: 5 tasks. I'll message you on Telegram when there's something to see.> /build

Sign off.

/approve

The plan opens on a project board in your browser: tasks, subtasks, what done looks like. Nothing starts until you approve it.

Dazza — Plan
  • T1Magic-link tokensplanned
  • T2Sign-in pageplanned
  • T3Export notes as markdownplanned
  • T4Export everything as .zipplanned
  • T5Rate-limit sign-in emailsplanned
Plan · draftApprove plan

Walk away.

/build

Each task gets its own branch and worktree, so your checkout is never touched. Leave Dazza running and step away: it messages you when there's something to see. Crashes and usage limits are its problem, not yours.

git worktree list
~/code/tidepool  yours, untouched
├─ dazza/T1-magic-link-tokens
├─ dazza/T2-sign-in-page
└─ dazza/T3-export-markdown

It texts you on
Slack or Telegram.

A good engineer doesn't make you chase them. Dazza messages you while it works: screenshots of what it built, the one question it's stuck on, a permission ask before anything risky, work that's ready. Reply from your phone and it carries on.

9:41
ChatsDazzabot
Today

Here's the export button on /notes. Does the placement work?

11:04
looks good 👍11:06
❓ T5 needs you: Rate-limit sign-in emails

There are keys for Resend and Postmark in the env. Which one sends sign-in emails?11:15
Dazza❓ T5 needs you: Rate-limit…postmark, resend's the old one11:18
✅ T3 is ready for your review: Export notes as markdown14:30
ApproveRequest changes
Message
Telegram. Link a bot in a minute. Reply to answer, tap to approve.
Search Tidepool
DazzaMessagesHome
Today

DazzaAPP12:40 PM

🏁 M1 reached: People can sign in without a password

T1 Magic-link tokens · T2 Sign-in page. Next up: T3 Export notes as markdown.

DazzaAPP1:02 PM

🔐 T5 wants to run a command that needs your OK: Rate-limit sign-in emails

curl -X POST https://api.postmarkapp.com/email

✅ You allowed it. Only this command, only for T5.

DazzaAPP2:30 PM

✅ T3 is ready for your review: Export notes as markdown

Adds an Export .md button to /notes. Tags come across as YAML.

3/3 subtasks · tests pass · 2 screenshots

ApproveRequest changes

2 repliesLast reply today at 2:30 PM

BIS🔗

Message Dazza

Slack. A DM from the Dazza app, a Home tab, and /dazza anywhere. Socket Mode, so nothing on your machine is exposed.

A project board.
Built in.

Dazza comes with its own project management board. It opens in your browser and runs on your machine: the scope, every task and subtask, what's moving, what's waiting on you and what's ready, updated live as it works. Comment on a task and the build picks it up.

Dazza — Tidepoollive

Sign-in and export

5 tasks · 14 subtasks · approved Tue 09:12

1 of 5 closed
planned
T4

Export everything as .zip

building
T5

Rate-limit sign-in emails

blocked · asked you

in review
T3

Export notes as markdown

T2

Sign-in page

closedyou only
T1

Magic-link tokens

01It moves the work.

Planned, building, in review. Tasks move on their own, in dependency order, each on its own branch.

02Blocked isn't stuck.

A task that needs you asks one question and waits. The rest of the plan carries on without it.

03You close it.

Every handoff comes with evidence and screenshots, and /try runs it for you. It never marks its own homework.

Everything a good engineer does.

It plans, keeps its work separate, shows you what it built, asks before anything risky, and doesn't fall over at 2am. It just doesn't need you watching.

  • Its own project board

    Scope, tasks and acceptance criteria on a board that opens in your browser and runs on your machine. Nothing changes until you approve.

  • A branch per task

    Every task is built in its own git worktree. Your checkout is never touched, and nothing merges until you say so.

  • Texts you back

    Slack or Telegram: the question it's stuck on, work ready for review. Reply from your phone and it carries on.

  • Shows its work

    It starts your app and screenshots what it built with the Chrome you already have, so a review comes with pictures.

  • Knows its limits

    Never pushes, deploys or touches credentials. Asks before remote databases, live APIs, machine-wide installs or containers.

  • Rides out the night

    Usage limits, crashes, overloads and hung sessions are handled. It waits, retries, and picks up where it left off.

Questions.

Anything else is in the README.

How is this different from just using Claude Code?

Dazza doesn't replace Claude Code or Codex, it runs them. What it adds is the management: a plan you approve, a board, a branch per task, safety rules, and a message when it needs you. You stop watching the work and start reviewing it.

What's the project board?

A project management UI that comes with Dazza. It opens in your browser, served from your own machine: a dashboard, the scope, the task list, and a page for every task with a comment thread you share with Dazza. It updates live as the work moves, and it's where you approve the plan and the work.

What does it cost?

Dazza is free and MIT licensed. It runs on the plan you already pay for: Claude Pro or Max, ChatGPT Plus or Pro, or an API key. On a subscription it strips stray API keys from its environment, so billing can't quietly switch.

Is it safe to point at a real project?

That's what it's for. Scoping asks what's live (real users, data, money) and writes guardrails into the plan. Separately, every command goes through a guard: it never pushes, deploys or reads credentials, and it asks you before anything that touches the outside world.

What happens when it gets stuck?

The task goes to blocked with one question, and it moves on to the next one. Answer in the terminal, on the board, or on Slack or Telegram, and the task goes back in the queue.

Does my code leave my machine?

No more than it already does with your agent. The plan lives in plain files in .dazza/, kept out of git. The project board runs on your machine, and Slack and Telegram connect outward, so nothing on your machine is exposed to the internet.

What do I need?

Node 22 or later, git and pnpm, and Claude Code or Codex installed. Once it's in, run dazza doctor and it checks everything else for you.

Be the
manager.

git clone https://github.com/harrison-bbb/dazza && cd dazza && pnpm install && pnpm build && npm link
Read the source on GitHub