1e8ef18e · zzmq.dev@gmail.com/zz
Commit
1e8ef18ec2d4704094510ee846ff5b04eed99fd5
Real UX fixes from live use: naming, token friction, Ask visibility Four fixes driven directly by actually using the thing: 1. "Agents you created" -> "Managed agents", with a line grounding it in governance.md's own credential framing ("issued, revoked, and rotated like any API credential") instead of ownership language -- per direct feedback that "created" read as a hierarchy the peer identity model shouldn't have. 2. Creating an agent now issues its first token in the same action (doCreateAgent returns {agent, token}) instead of a separate "New token" click -- per direct feedback ("shouldn't adding an agent just also create a token"). A first browser login does the same if the agent has zero active tokens yet. Minting an *additional* token (rotation, a second credential) stays its own explicit step, now labeled "Issue another token" to make that distinction clear. zz agent create and the web form both show the token inline. 3. zz repo clone <owner/repo> [dir]: embeds the stored credential automatically instead of expecting it typed into a git username/ password prompt by hand. Root cause this fixes, confirmed live: a real git push attempt failed with "remote: not found" because the natural thing to type at "Username for ..." is your own identity, not a bearer token -- even with a valid token already sitting in ~/.zz/credentials.json from `zz login`, nothing made it obvious or practical to actually use for a manual git command. 4. Ask/Lane visibility, previously nonexistent on any surface: GET /api/repos/:owner/:repo/asks, a new "Asks (root Lane)" section on the repo page, and `zz repo asks <owner/repo>` -- all three render the same root-Lane history (ASK/ANSWER/INSIGHT) via a shared getRootLane() helper. Verified live against the user's own real "shoes" repo and its already-posted Ask: zz repo clone + a real edit + git push succeeded cleanly (the exact sequence that failed before), zz repo asks and the repo page both show the Ask posted earlier via the web form, and agent creation via both the API and `zz agent create` returns a working token immediately. Test agents created for verification cleaned up after; the user's own repo/agents left untouched. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Troy Howard <thoward37@gmail.com> -- 2026-10-12T05:12:27.000Z