Summon agents from your forge.
Agents work where your team already does. Comment /ryph on an issue or pull request on GitHub or GitLab, or a Radicle issue or patch, to have an agent fix it, review it, or address the review, and ask it to keep your issues and pull requests in order.
Customers can't tell why a refund was issued. The order page shows the amount but not the reason.
- Issue #88
- Open
- PR #91
- None yet
- Issue #85
- Open
From a comment to a pull request
The thread is where the work is asked for, discussed and reviewed, so it’s where the agent reads, answers and delivers.
Commands in any thread
Comment /ryph, an agent’s name and a request on an issue or pull request. Ryph checks the commenter’s access before anything runs.1
Reads the whole thread
The agent reads the opening post, comments, reviews and inline remarks. Your command is its instruction; the thread is context.2
Fixes land where the review is
Asked to address a review, the agent pushes onto the pull request’s own branch. Never a fork, and never your default branch.3
One thread, one run
A follow-up /ryph joins the run already working on the thread, so you can keep steering it. Name a different agent meanwhile, and Ryph asks you to wait for the first to finish.
Stays with the pull request
The agent can merge in the latest base branch, take over an existing pull request, and keep shipping patches after one merges.4
Keeps your tracker tidy
Ask an agent to label and comment on threads, open or close issues, and post pull request reviews.5
Across several repos
Give a run several repos at once and deliver changes across them as a set of pull requests.6
- The commenter needs write access and a linked Ryph account, and in a workspace, write access to every repo in it. Commands from anyone else get no reply. On GitLab, write access means Developer or above. On Radicle, repo delegates or an admin-kept allowlist can command agents.
- Thread context includes the opening post, comments, reviews and inline remarks within size limits. Long threads and individual entries are shortened, with omissions marked.
- The forge gateway makes the push, fast-forward only, after checking that the pull request is still open and its branch is neither the default branch nor on a fork. Pull requests from forks aren’t supported yet. Repos that require approval hold the push until someone approves it.
- Updating from the base branch always merges; a conflict is left for the agent to resolve before its next patch. A run can only take over an open pull request from the same repo that no other run is working on. After a patch merges, further work continues on a new branch and pull request.
- Labels can be added but not removed, only issues can be closed, and reviews are comments rather than approvals or change requests. Each action is capped per run and limited by the agent’s forge policy.
- Pull requests follow each repo’s submission policy. A run addressing an existing pull request updates that branch; other changed repos get their own pull requests. Related changes are counted without exposing private sibling repo names or links.
More of Ryph
- Incident response An agent joins the incident chat, investigates and ships the fix.
- Automations Recipes that run on a schedule or when a webhook fires.
- Artifacts Reports and overviews agents publish as pages your team can open.
- Memory What agents learn, shared and kept current with the code.
- Agentic CI One CI for agents and the people working with them. Pull requests open already green.
- Security Keys stay behind gateways, and work leaves as a patch.
- Environments Images built for your repo, and services for every run.
- Deploy One binary on a laptop, or your own cloud.
Try it on your own machine.
One binary with the web app and database built in.
Get started