Once Studio, the Git connection, a runtime, agents, and a project are all set up, take one small request through the whole workflow. Along the way you'll see how the agent team moves an issue forward and confirm that every part is connected before you invite your colleagues.
Before you start
- The project's "Initialize project" issue is done. See Create a project.
- At least two agents are enabled, and the coordinator agent has a first choice. See Enable agents.
- A runtime is online.
1. Raise the request
Open the project and click New issue. A session with an agent opens on the right, with the current project sent along as context.
Describe a small request in business terms, along with how you'll check it. For example:
Add a Suppliers table to the app with name, contact person, phone, and status (active or paused), and add a Suppliers page to the navigation where you can add, edit, and view suppliers. Acceptance: after signing in, open the Suppliers page from the navigation, add a supplier, and see it in the list.Send it. If the request is clear, the agent turns it into an issue right away. If anything is unclear, it asks you first.
Once the issue is created, click Start 1 issue in the session, or open the issue and click Start.
To skip the session, click Fill in manually and enter the title and description yourself.
Done whenthe issue is In progress and its executor is the coordinator agent.
2. Watch the agent team work
Open the issue. The Now line at the top always shows which agent is working on it, for how long, and on which runtime, with what comes next below it.
Activity shows every handoff the coordinator agent makes: who gets the step, what to do, what to read, when it counts as done, and why that agent. This request adds a table, so the coordinator agent first has an agent that is good at design write a short plan, then hands development to an agent that is good at building. The building agent writes the code and tests, takes screenshots in the running app, and opens a PR from the agent/<issue key> branch. Finally, the coordinator agent has another model review the code. Review findings go back for fixes, and the fix is reviewed again.
A small request like this one takes about half an hour from start to ready for acceptance.
Supplier scoring and tiers
- Now
- CXCodex · GPT-5.5 is running “Implement scoring and tiers per the plan” · 12 min · Server 02
- Next
- Once the implementation is done, an agent from another vendor reviews it, then it goes to acceptance.
Runs has the full record of every run, which helps when you need to dig into a problem.
3. Answer questions
When something isn't clear in the request, such as a choice between two approaches, the coordinator agent moves the issue to Blocked and spells out what you need to decide. It shows up at the top of My issues. Open it, click Reply in the Needs you card, and write your decision. The coordinator agent picks up from your reply.
If the request is written clearly, this step may never come up.
If CI isn't connected yet, it will come up: the PR has no check results, so the coordinator agent asks whether to set up CI first or accept without CI, based on the delivery report and screenshots. For a trial run you can reply "No CI this time. I'll accept from the delivery report and screenshots and merge myself", and it hands the issue to you for acceptance. Before real use, remember to connect CI.
4. Accept the result
Once the PR has passed review and its checks, the issue moves to In review and appears under Waiting for you in My issues.
- Open the issue. The Needs you card says what you're asked to accept, and below it is the delivery report: how it was before, what changed, how it was checked, open issues with recommendations, and finally the acceptance criteria and screenshots.
- Click View changes to see the PR.
- If CI is connected, open the preview from the issue page, sign in as the first administrator, and try it against the acceptance criteria.
- If it works as expected, click Merge. The confirmation shows the merge method (for example, squash into
main), the commit title, and that the issue will move to Done. Confirm it. Without check results, the button reads Merge anyway, and you can give a reason. Studio records the merge on the PR and in the issue's activity. - If something is off, click Send back for changes and say what needs fixing. The coordinator agent arranges the fix and hands it back to you.
Supplier scoring and tiers
- Up next
- Zhou Hang reviews the delivery report and accepts PR #31.
Zhou Hang: review the delivery report and accept the supplier tiers. If they pass, merge PR #31; if not, send it back.
How it was before
Suppliers had only basic profiles, with no score or tier. An order needed the purchasing manager’s approval only above ¥50,000.
What changed
- Suppliers now have a score and a tier, A, B, or C, recalculated every night from on-time delivery, quality pass rate, and price
- Every order to a tier C supplier now goes to the purchasing manager for approval when it is submitted, whatever the amount. Other suppliers keep the amount rule
- New suppliers start at tier B and are re-tiered after three months
How it was checked
Walked through all three acceptance scenarios in the preview. All tests and CI passed, and a model from another vendor approved the review.
Open issues
- Existing suppliers get a tier only after the first nightly recalculation. Recommend running it once by hand on release day.
Acceptance criteria
- The supplier list shows each supplier’s tier (screenshot 1)
- A ¥10,000 order to a tier C supplier goes to the purchasing manager for approval when submitted (screenshots 2 and 3)
Done whenthe issue is Done and the change is on the repository's default branch. If CI is connected, the change is deployed to staging, and the issue shows which environments it has reached.
Troubleshooting
The issue never starts. Look at the Now line on the issue page. It says what it's waiting for: no runtime online, all slots busy, or the agent exists only on someone else's personal runtime. If no runtime picks the work up within 24 hours, the run fails, and you're notified so you can retry.
"Initialize project" isn't done yet. New issues in the project wait until it is.
The agent says it couldn't take screenshots. The runtime has no browser. See the preparation section of Connect a shared runtime.
Once it all works, invite members.