Someone files an issue: "the export button does nothing on mobile." Instead of triaging it into a backlog, a teammate replies: "@cloudaxis take a look and fix this." A coding session starts from that comment, reads the issue, makes the change, and comes back with a pull request and a mobile screenshot showing the button working.
It turns the issue tracker from a to-do list into a place where some fixes just get done.
How the mention works
CloudAxis listens for issue and pull-request comments on repositories where the GitHub App is installed. When a comment mentions @cloudaxis, the text of the request becomes the goal for a new coding session on that repo. The session runs the same loop as any other: isolated machine, edits, tests, proof, pull request — and it links back so the whole thread has the context.
Only trusted collaborators, never bots
A comment trigger is an untrusted surface — anyone might comment on a public repo — so it is gated. Only repository owners, members, and collaborators can summon a session; comments from bots are ignored; and the comment text is screened and clearly wrapped as data, not instructions, before it reaches the agent.
Requests that try to do something they should not — exfiltrate secrets, bypass the review gate — are refused outright at the door rather than started and audited after the fact. A GitHub comment can ask for a change; it cannot talk its way past the guardrails.
It closes the loop, not just opens it
If continuous integration fails on the change, CloudAxis can pick the session back up, look at the failing checks, and push a fix — a bounded number of times, not an infinite retry loop. And when it is ready, the same approve-to-merge flow applies: a human ships it. The issue goes from reported to reviewed-and-ready without anyone opening an editor.
Frequently asked questions
Can anyone on a public repo trigger it?
No. Only owners, members, and collaborators can summon a session; bot comments are ignored, and the comment text is screened and wrapped as untrusted data before the agent sees it.
Does it merge the fix automatically?
No — it opens a pull request with proof and waits for a human to approve the merge, same as every other CloudAxis Coding session.
How CloudAxis Coding works · Proof-of-work pull requests · CloudAxis Coding (beta)