Plan: what is done from the agent-first list, and what is next
1 file+14−450/1 viewed
| 766 | 766 | parity. Forge basics are done well enough; each item below should make the | |
| 767 | 767 | demo's story stronger. | |
| 768 | 768 | ||
| 769 | − | 1. **The outcome page.** One live view of a brief being converged: the issue | |
| 770 | − | graph lighting up as agents take, finish, revise and land work; who is | |
| 771 | − | blocked on whom; the queue draining into `main`; cost so far. The demo's | |
| 772 | − | centrepiece. | |
| 773 | − | 2. **Coordination you can see.** Agents use g1t's tools (opening issues for | |
| 774 | − | out-of-scope work, commenting on each other's pull requests); show those | |
| 775 | − | exchanges as first-class cards on the outcome page and in timelines, with | |
| 776 | − | handoff and question states. | |
| 777 | − | 3. **Steering a running agent.** Send a message to a working agent, pause it, | |
| 778 | − | or answer its question from the page; it picks it up at its next turn. | |
| 779 | − | 4. **Racing and comparing.** Several agents on one issue, compared side by side | |
| 780 | − | with checks and review, the winner merged and the rest superseded. | |
| 781 | − | 5. **Bring your own agent, recorded.** A CLI with Claude Code hooks so sessions | |
| 782 | − | from anyone's machine land on the pull request automatically. | |
| 783 | − | 6. **A visual identity that says "agents".** Isometric line-art of lanes, | |
| 784 | − | branches converging and agents at work; a palette and type system to match. | |
| 785 | − | 7. **The large run.** Dozens of agents on a real repository, end to end, for | |
| 786 | − | the video; g1t hosted on g1t. | |
| 787 | − | ||
| 769 | + | Done from this list: the outcome page (a plan's issues as a live graph with | |
| 770 | + | cost and a feed of what happened), coordination you can see (agents' issues | |
| 771 | + | and comments stand out in the feed; agents hold g1t's tools through a token | |
| 772 | + | scoped to one repository), steering a running agent (messages delivered | |
| 773 | + | between steps, and at the end), and recording sessions from anyone's own | |
| 774 | + | Claude Code (`curl -fsSL https://g1t.sh/install/claude.sh | sh`). Racing a | |
| 775 | + | set number of agents on one issue is dropped: choosing how many agents to | |
| 776 | + | use is not something people should have to do. | |
| 788 | 777 | ||
| 789 | − | Done: site with marketing page; separate docs site with API explorer; git | |
| 790 | − | over HTTPS; accounts with registration, email verification, password reset | |
| 791 | − | and device sign-in; an OAuth 2.1 server, so MCP clients sign in through the | |
| 792 | − | browser with no token to paste; workspaces with members, required before | |
| 793 | − | anything else, sharing one namespace with usernames, each with a page that | |
| 794 | − | rolls up its repositories and work in progress; access tokens owned by a | |
| 795 | − | workspace; issues with labels, checks and | |
| 796 | − | comments; pull requests in forks or from branches, with diffs and sessions, | |
| 797 | − | several per issue; acceptance checks run in clean sandboxes, gating the | |
| 798 | − | merge; a g1t agent's pull request seen through automatically, from checks | |
| 799 | − | and review to revision and catching up, to ready to merge, and merged by | |
| 800 | − | itself where the repository's settings say so; mission control showing | |
| 801 | − | every pull request in flight by where it stands; issues and pull requests assigned to people as well as to agents, | |
| 802 | − | reviewers requested, and every such step told in the conversation; agent | |
| 803 | − | usage charged to the workspace from prepaid credit; repository settings for branch protection, required | |
| 804 | − | approvals and how g1t's agents are reviewed and merged; line comments and review verdicts, including reviews written by a | |
| 805 | − | g1t agent; overlap between pull requests flagged from every push; catching | |
| 806 | − | up with `main` by a g1t agent that resolves conflicts; importing from | |
| 807 | − | GitHub; merging with a behind check, which resolves the issue and supersedes | |
| 808 | − | the rest; g1t agents in sandboxes, with the model routed by g1t rather than chosen; REST API, OpenAPI | |
| 809 | − | and MCP server; event bus; a speculative merge queue that tests each pull request together with those | |
| 810 | − | ahead of it and lands only states that passed, ejecting a failure back to its agent; agents told about | |
| 811 | − | the other work in flight, and a person's review outranking an agent's; a person asking for changes | |
| 812 | − | sending the agent back; why-blame from any line to the commit, pull request, issue and the agent's own | |
| 813 | − | account; commit pages and a diff view with a file tree, split view and viewed state; a sidebar app | |
| 814 | − | shell with a command palette. Every service and the API are in Rust. | |
| 778 | + | 1. **Handoffs and questions between agents** as states (offered, accepted, | |
| 779 | + | declined, done) on the outcome page, not only comments. | |
| 780 | + | 2. **The large run.** Dozens of agents on a real repository, end to end, for | |
| 781 | + | the video; g1t hosted on g1t. | |
| 782 | + | 3. **Polish for judges trying it in a minute:** a seeded demo workspace, the | |
| 783 | + | empty states, and the first-run path from sign-up to an outcome landing. | |
| 815 | 784 | ||
| 816 | 785 | Earlier items still open, after those: | |
| 817 | 786 |