Loading page…
New GitHub Actions tracking follows workflows after a merge, alongside reliability fixes for existing Visual answers and code reviews.
Choro 0.103 adds GitHub Actions tracking so you can follow workflows after a merge, plus reliability fixes for existing Visual answers and code reviews.
See GitHub workflow status alongside the Ship that started the work. Once runs are found for a merged pull request, Choro shows their progress beneath its Ship card and in the companion.
Keep chatting, start another task, or ship another change while workflows run. Agent activity and Git Actions have separate status rows, so you can follow both without leaving your work.
Check queued, running and completed workflows, including failures and runs that need approval.
Open workflow details on GitHub, refresh the status, or stop and resume tracking.
Keep tracking state across Choro restarts.
Draft a request for your agent to investigate a failed workflow, with relevant run links. Review and send it when you are ready.
Workflow status describes GitHub Actions results; it does not confirm that an app has been deployed.
Visual answers, introduced in 0.102, gets clearer agent guidance for ordinary comparison requests such as “show me four variations” or “compare two hero sections”. This improves routing to the existing feature without requiring you to name it.
Requests for image files, exports or another specific format keep their requested output.
Malformed answers are rejected before they can replace existing content. The agent receives actionable correction instructions and can retry, while the previous saved answer remains intact.
Review findings stay connected to the code snapshot being reviewed, with clearer attribution when Bandmates contribute.
Reviews can search larger snapshots in pages, and reviews with coverage gaps remain visibly incomplete. This helps distinguish a finished review from one that still needs attention.