AI agents
Assign the ticket to an agent. Review its pull request.
Tolus exposes an MCP server. Claude Code, Codex or any compatible agent picks up the tickets assigned to it, works in your repository and hands back a pull request for review. Its time is logged against the retainer, under its own name.
Fix the contact form submission
Agent Claude Agent Internal note
Email validation fixed, test added. Review before merging.
Pull request #128
Handed back to Camille R. for review
Identity
One more teammate on the project
Create an agent, give it projects and assign it tickets as you would to anyone on your team. It carries the name you give it, for example “Agent Claude”.
An agent has no password and no reachable email address. It receives no notifications and connects only with its token, from your harness.
Its own identity
Its name appears in the ticket history, and its notes carry an “Agent” badge.
Limited scope
It only works in the projects you open to it. Removing a project unassigns its tickets there.
Revocable token
Read-only or read and write, revocable at any time, with its last use displayed.
The work
It does the work, then hands the ticket back
The agent reads the request, the discussion and the attachments, then works in your repository on a dedicated branch. When it is done, it hands the ticket back in a single call: an internal note, the pull request link, the move to the review step and the return to the person who assigned it.
If it cannot push its code, if there is nothing to code, or if it needs information only the client has, it says so in its note. Your team decides what happens next and talks to the client.
Any MCP harness
Claude Code, Codex or any MCP client that connects over HTTP with a token.
Scheduled runs
Run it on demand, or on a schedule if your harness supports scheduled tasks. It only works on what is assigned to it.
Configurable review step
Per project: a chosen step, or detection of a step named review, QA, test or validation. Otherwise the agent picks the most fitting step of the workflow.
The retainer
Its time counts against the retainer
The agent logs its time on the ticket, against one of the project’s work types. The entry flows into the report and the retainer’s used hours, like a teammate’s.
It picks from the project’s work types: add a dedicated one, for example “AI agent”, to keep its time separate. You then decide whether to bill it or waive it, since the entry can be edited or removed like any other.
Time under its name
The agent is the contributor on its entries in your internal report and in Insights.
Dedicated work type
A work type reserved for agents separates their time from your team’s in the report.
Billing is your call
You keep control of every entry before the client review.
Security
The guardrails
An agent works in your repository and reads text written by your clients. Tolus limits what it can do, whatever the harness.
Its own tickets only
It only sees the tickets assigned to it, in its projects.
Internal notes only
It never writes to the client. Its notes and pull request links stay inside your agency workspace.
Never closes a ticket
It never resolves or closes a ticket. Someone on your team reviews and decides.
Tickets are data
Ticket text reaches it as data to analyse, never as instructions to follow.
No deployment rights
Tolus gives it no access to production. It delivers a pull request, your team merges and deploys.
No writes without a subscription
If the subscription has ended, the workspace becomes read-only and the agent can no longer change anything.
Connection
Connected with one command
In Claude Code, one command is enough. Replace <token> with the agent’s token.
For another harness, register the server https://my.tolus.app/api/mcp over HTTP, with an Authorization: Bearer header followed by the token.
claude mcp add --scope user --transport http tolus https://my.tolus.app/api/mcp --header "Authorization: Bearer <token>"Tokens are created from the Agents menu in Tolus, available to owners and administrators.
Make the right choice
For teams that maintain code
Tolus is a good fit if
- You are an agency or IT services company working in git repositories.
- Your maintenance work is made of many small fixes.
- Your team already uses Claude Code, Codex or another harness.
Before you connect an agent
- If your contracts forbid any processing by a third-party model without the client’s consent, get that consent first.
Frequently asked questions
What to check before you choose
Which agent can I connect?
Any MCP client that connects over HTTP: Claude Code, Codex and other compatible harnesses. The agent authenticates with its token, in the Authorization header.
Can the agent ship to production?
No. It hands back a pull request for review. Deployment stays with you.
What does my client see?
The ticket moves like any other: the client sees its status, its history and the assignee, so the name you give the agent. The time appears in their retainer report, under the chosen work type, without a contributor name. The agent’s notes and pull requests stay internal to your agency.
How much do agents cost?
Nothing extra. They are included on every plan, with no limit, like your team members. The model runs on your own subscription.
Who pays for the agent’s time?
You decide. On a dedicated work type its time stays identifiable: bill it against the retainer, or remove the entry if you waive it.
What about my clients’ data?
The agent reads tickets from your harness, and the provider of the model you use processes them. This processing is covered by our terms, in the “Connectors, third-party tools and agents” section. Inform your clients when your contracts require it.
The agent codes, your team reviews, the retainer keeps count.
Create an agent, open a project to it and assign its first ticket. Your trial lasts 30 days, with no credit card.