Skip to main content
Agents investigate your project data and produce reports, content briefs, or actions for review. They can read only their listed project tools, and every output stays a draft until a person approves or keeps it.

​
Open Agents

  1. Open a project
  2. Select Agents in the project sidebar
  3. Use Grid view or List view to browse the roster
You need the project management permission to start runs, change schedules, review outputs, or create custom agents.

​
Agent roster

Each agent has one focused job and shows the project tools it can read and the draft type it delivers. The visible roster and model choices can depend on the agent features configured for your account.

​
Start a run

  1. Select Run on an agent
  2. Choose a Model
  3. Review Estimated per run when history is available
  4. Optionally choose a quick action or enter a focus instruction
  5. Select Start run
DevTune checks the account credit balance before queueing. If recent completed runs exist for the same agent and model, the dialog estimates the next run from that history. The first completed run provides the first measured estimate. The run detail shows the run log, tool steps, saved artifacts, model, trigger, timestamps, duration, and output. Status can move through Queued, Provisioning, Running, and Polling before reaching Ready for review or a terminal error state.

​
Review the output

An agent output does not publish content or change your live site.
  • Approve an action to select Add to Actions
  • Approve a content brief to select Send to Actions
  • Keep a report to retain it with the run
  • Select Dismiss when you do not want the draft
After a draft is ready, use Follow-up to ask for a revision or next step. Each follow-up starts a separate run in the same run thread, grounded in the preceding output, and consumes credits like any other run.

​
Schedule repeat runs

Select Schedule on an agent to configure:
  • Daily, Weekly, or Monthly cadence
  • Time and, when applicable, weekday or day of month
  • Model used by scheduled runs
  • Estimated monthly credits when enough history exists
Scheduled runs enter the same run history and review flow as manual runs. Their outputs still wait for review.

​
Run history

Run history combines runs across the project. Filter it by agent, then select a row to inspect its log and output. The history distinguishes manual, scheduled, and follow-up triggers and shows usage recorded for each run.

​
Next steps