Persistent responsibility
A named job the team can rely on.Worktree Agents
One business role. A defined agent behind it.
A Worktree Agent is a durable, connected working role, not a blank chat. It receives known work, uses approved systems, follows a defined routine, includes people when judgment is required, and records what happened.
WT
Role activeIllustrative agent roleCustomer review coordinator
- Responsibility
- Prepare customer reviews and surface decisions
- Starts when
- A review is requested or reaches its scheduled date
- Approved context
- Customer records, project status, and team notes
- Human authority
- Commercial changes and unresolved exceptions
Current request
Prepare the Northstar review and flag decisions.
- ContextGathered
- DraftPrepared
- Pricing exceptionApproval required
A durable business role
The job exists before the conversation starts.
The agent's responsibility, working context, operating standard, and authority are defined with the workflow. A teammate can ask for the job by name because the process does not live inside their prompt.
See how Worktree finds the right workflowApproved context
Known sources connected to that job.Operating standard
A routine and acceptance criteria.Visible history
Evidence from completed work and exceptions.A reviewable agent run
One request moves through a controlled routine.
The workflow gives each step a purpose and each decision an owner. The agent can move routine work forward without hiding where human judgment entered the result.
- 01Received
Request received
A known request starts the defined routine.
- 02Complete
Context gathered
Only the sources approved for the role are checked.
- 03Complete
Work prepared
The agent follows the accepted operating standard.
- 04Human included
Decision routed
An exception pauses for the person with authority.
- 05Ready
Outcome recorded
The accepted result and material context remain reviewable.
Product surfaces
The agent is more than its answer.
The useful product is the complete operating surface around the work: how it starts, what it can use, where people decide, and what remains available for review.
A familiar way to ask for work.
The team starts a known job from the interface agreed for the workflow. The agent does not need a new prompt that reconstructs the process every time.
Sources tied to the role.
The agent gathers the records, documents, and messages its assigned responsibility requires, without treating every connected system as open context.
Judgment stays with people.
Ambiguity and consequential actions can pause with the supporting context, proposed action, and reason a decision is required.
A run can be understood later.
Relevant sources, actions, approvals, outputs, exceptions, and status form the operating evidence for review and focused improvement.
Role-based control
Access follows the job.
An agent does not receive unrestricted access to the business. The deployment defines the systems, information, actions, approvals, and exception paths appropriate to its assigned responsibility.
Explore Product Security- Systems
- Which applications and data sources belong to the job.
- Actions
- What the agent may read, prepare, update, or submit.
- Approvals
- Which steps require an authorized person before they continue.
- Exceptions
- Where the workflow stops instead of improvising beyond its role.
01
02
03
04
From role to production
The product begins with a workflow your team can define.
Worktree maps the current work, configures the role and its controls, connects the required systems, tests representative cases, and launches the workflow with an agreed operating standard.
See how Worktree implements the agentStart with one responsibility
Bring the work that still depends on the same person.
A Worktree engineer will help determine whether it can become a defined, controlled agent role and what the deployment would require.