Tell each session how its CI ended
Track GitHub Actions runs and check runs for the commits each session pushed. When the runs conclude, the pushing session gets one notice with the conclusion, failed jobs and the runner’s error lines. Frozen sessions get it after they resume.
github.com only; GitHub Enterprise Server, GitLab CI and other forges are not polled. Tag pushes, other remotes, linked repositories and checkouts shared by several sessions are not attributed. Native notices reach Claude and Codex sessions; other agents see results in the CI section only.
How it works
Attribute runs to the pushing session
Pushes are recorded by the session’s push hook or, in managed checkouts, by Git’s own push log. Several sessions can push to one repository; each hears only about its own commits.
Read runs in the CI section
CI lists repositories with their recent runs, status, branch, duration and session. Open a run for its failed jobs and steps, the log excerpt and how it was attributed.
Choose when to notify
Notify on failures only or on every conclusion. The log excerpt comes last, redacted and fenced as untrusted CI output.
Try the interface
Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.
Put your server to work.
Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.