Why
An agent needs the same boundaries as a person: a workflow, permissions, a budget and someone to ask. That is why an agent in Volent is a member of the workspace, not a black box outside the tracker.
How it works
Added by an administrator
The Anthropic key is verified before it is saved and stored encrypted; the list shows only the last four characters. An agent does not take a paid seat.
Access by project
An administrator turns the agent on only in the projects that need it, with the permissions of a regular member.
Delegating means assigning
Make the agent the assignee and a session is queued. Without a connected repository the agent does not take the task.
Tools only within the task
Read the task, change fields, move the status (through the workflow with all its rules), write an update, ask a person a question, open a PR, finish.
Default limits
$5 per session, 2 concurrent sessions in the workspace, up to 4 hours of work; a question unanswered for 7 days stops the session. An administrator can change all of this.
A person stays in control
Answer a question, stop a session, raise the budget, add clarifications after it finishes. You can see who delegated, how much it cost and how long it took.
PRs go to a protected branch
Before turning it on, Volent checks the protection of the main branch; without it an administrator must agree explicitly. Session transcripts stay in your Anthropic organisation.
Good to know
- Works with repositories on GitHub and GitLab.com. Agents are not yet enabled for self-hosted GitLab and GitHub Enterprise.
Availability
Annual Pro billing is 20% cheaper. Questions about plans: [email protected].