The vision is yours.The work is Zivie’s.
Say what matters. Zivie ranks the work, runs an agent per issue, reviews every change, and keeps the project in your words.
Runs on the Claude Code and Codex plans you already have.
9:12 AM
Users keep losing their drafts on slow wifi.
Zivie
That's two bugs, so I filed two. #1: a draft is dropped when you switch pages before it saves. #8: it's lost when the page closes mid-save. Both P1, an agent on each already.
I closed #11 as superseded by #1. It's the same bug from the other side, and keeping drafts in the core fixes both.
IssuesAll open
Running 2
- #1Composer loses its draft when switching pagesReproducing· Writing a test that fails on mainBug
- #8Drafts are lost when the page closesStarting· Branching from mainBug
Closed 1
- #11A draft comes back empty after a crashSuperseded by #1Bug
9:40 AM
Anything that touches billing waits for my review.
Zivie
It's in your rules. #17 and #21 touch billing, so they'll wait for you at merge. Every agent at work has it with its next step, #21's mid-turn.
RulesShared · Learned
18Anything that touches billing waits for my review.Maya · today, 9:40 AMUndo
MergesIssues
- #17Invoices show taxZivie mergesYou review
- #21Checkout with StripeZivie mergesYou review
- #3GitHub sign-in with device flowZivie merges
Agents at work6 of 6 have it
- #1next step
- #3next step
- #8next step
- #12next step
- #17next step
- #21mid-turn
10:26 AM
Zivie
#1's agent drew three ways to show a draft saving. This one's yours, since it's how the app looks. I'd take A: it says what's happening without getting in the way.
While a draft saves, what should the composer show?
11:48 AM
Zivie
#8's first review asked for changes. Three findings, all real: a draft lost mid-save, two windows overwriting each other, a cleared draft that comes back after a restart.
#8Drafts are lost when the page closes
#8's agent· Opus 5.5
Fixed all three, each with a test that fails without the fix. Pushed a238e80; round 2 is reading.
Round 2 of 3 · one approves, one reading
1:20 PM
Zivie
#1's checks are back from this Mac. The perf gate passed; one UI check failed: the Issues row lost its tags, which #1 never meant to touch. Its agent is on it.
#1Composer loses its draft when switching pages
Checks on this Mac058c85b
the row shows its tagstests/issues.js
Checks on this Mac2 of 2
Checks on Linux box1 of 3
3:05 PM
Zivie
Merged #10 at 3:05: two approvals, checks green, PR 14. Its branch is cleaned up.
#10Release notes skip hotfixesMerged
- Two approvalsRound 2 of 3 · GPT-6.1 Sol
- Checks greenCI tests · UI checks · perf gate
- Merged by Zivie, by your rulesNot billing, so it didn't wait for you
- PR 14 squashed into main3:05 PM
- Branch deletedfeat-10-release-notes
4:20 PM
Zivie
#3, #5, #8 and #12 each failed the same perf check this afternoon. It's the test, not their changes: it fails one run in eight on main too.
Each merged once its rerun passed, and I filed #64 for the test, at P3. Nobody stopped to chase it, you included.
IssuesToday
- #3GitHub sign-in with device flowperf gate→Merged
- #5Search misses archived threadsperf gate→Merged
- #8Drafts are lost when the page closesperf gate→Merged
- #12Paste images into a threadperf gate→Merged
5:40 PM
When's checkout ready to ship?
Zivie
Thursday afternoon, from how the last thirty issues like these went. Four of the five left are moving; #21 waits on a secret from you.
IssuesCheckoutThu 3 PMThu noon to Fri 10 AM
- #17
- #22
- #24
- #25
- #21waits on you
6:45 PM
I'm off for the night.
Zivie
Good night, Maya. Six agents are still at it. I'll tell you what happened when you're back.
Overnight
While you sleep,
the agents keep going.
- #1 merged
- #4's tests failed on
447a9c6 - #6 merged
8:52 AM
Zivie
Morning, Maya. Two merged and one failed overnight. #4's agent is already on the failure. Two things wait on you.
While you were away8:52 AM
Merged2
#1Composer keeps its draft between pages
#6Runner logs keep their long lines
Failed1
#4Tests failed on 447a9c6 · its agent is on it
Waiting on you2
#9Where the unread count goes
#21Needs STRIPE_SECRET_KEY
8:53 AM
Zivie
#9's agent drew three places for the unread count. I'd take A: it says how many without shouting, like the saving line you picked yesterday.
Where does a thread's unread count go?
8:54 AM
Zivie
#21 still needs STRIPE_SECRET_KEY to test checkout. It goes in your Keychain; agents only ever see its name. With it this morning, checkout ships this afternoon.
A secret for checkout's tests
STRIPE_SECRET_KEYStripe, test mode
Save to Keychain
Memory
It learns how you decide.Then makes the calls you would.
First how you like software built, then your taste, how much risk you take, when polish can wait. What you tell it becomes a rule for every agent; what it notices, it keeps.
Memories
How you build
Ships the small version first; polish is its own issueFrom #2 · last week
Won't trade a failing test for speedFrom #8's review · Wednesday
Your taste
Picks from options drawn, not describedFrom #1 · Wednesday
Likes a quiet UI: a line in gray over a bannerFrom #1's pick · used on #9 today
Risk
Bold in the UI, careful anywhere near moneyFrom your rules · Wednesday
Your day
Reads the digest first thing, around 9Monday to Thursday
The project
The perf gate is flaky under loadFrom #3, #5, #8, #12 · filed as #64
Rules · Learned
- 14No new dependency without asking me.Maya · Monday
- 15Times in Pacific.Maya · Monday
- 16Error messages say what to do next.Maya · Tuesday
- 17Every pull request gets a line in the changelog.Maya · Tuesday
- 18Anything that touches billing waits for my review.Maya · Wednesday
Stats
Zivie is built with Zivie.So we asked it how it's going.
Its own repo, read from its Stats on .
How's it going?
Zivie
A bug is hours of work, median: its agent, its reviewers, its checks. The other hours on its clock are waiting, on plan limits, for a slot or on you.
Time
h
of work in a bug
% pass the first review round. An issue takes rounds on average, and pull requests had a failing check caught before they merged.
Quality
%
pass the first round
merged of filed, of them bugs. built of them, and reviewed .
Throughput
merged of
Time
Where an issue's clock goesmedian, merged issues
A bug h work · h waiting
Every merged issue h work · h waiting
- Work its agent, its reviewers, its checks
- Waiting on plan limits, for a slot, on you
Most of an issue's clock is waiting, so the work is the number to watch.
Quality
A failing check caught before mergeeach square a merged pull request
of
review rounds · test runs, % failed
In Zivie today
- One conversation per project
- Issues filed, ranked, split, parked
- Automatic prioritization
- Dependencies
- Agent per issue, in its own worktree
- Multiple reviewers, each its own model
- Rounds until approval, or Zivie decides
- Merges by your rules
- Main merged in when needed
- Agents pick up after a restart
- Tests take turns on your Mac
- Local or cloud runners
- Digest when you're back
- Questions as cards
- Mockups you click
- Slash commands
!runs a shell command- Paste an image
- Memories
- Rules
- Secrets in the Keychain
- Stats: throughput, time, tokens, code, quality
- Cost per merged issue, at API prices
- Spend by role and by model
- Burndown with a finish date
- Estimates from your own history
- Where the time went
- Many projects open at once
- Your window's color, or a world
- Light and dark
- ⌘K
- Shortcuts throughout
- Updates itself overnight
- Claude Code and Codex
- Model and effort per role
- Waits out usage limits