01
Settings change agent behavior
Operating rules are not labels for a future feature. Enabled focus areas alter which project evidence an agent considers; initiative changes whether it surfaces next actions proactively; attention controls escalation sensitivity; response depth changes the amount of context in its output.
Scheduled reports activeDaily report · 09:00
Ask the team
BlockersExpected datesSprint closeTell me
Schedule risksDaily digestClient attentionAllowed reactions
Notify meMove draftAcknowledgement02
Focus areas select evidence, not decorative topics
| Agent responsibility | Useful focus areas | Effect |
|---|---|---|
| Sprint planning | Sprint scope, due dates, blockers, acceptance, workload | The agent prioritizes delivery readiness and realistic commitment |
| Project management | Blockers, expected dates, overdue work, client questions | The agent collects missing status and surfaces meaningful changes |
| Billing | Open invoices, accepted work, milestones, anomalies | The agent reviews billable evidence and material payment conditions |
| Expenses | Approval status, prepayment, vendor notes, margin visibility | The agent focuses on spending decisions permitted for the current role |
| Capacity | Project allocation, role coverage, overload and delivery capacity | The agent highlights assignment pressure and ownership gaps |
03
Behavior controls change when and how the agent responds
| Control | Example options | Behavioral difference |
|---|---|---|
| Initiative | Proactive, Guided, On request | Whether the agent suggests next actions independently, only when useful, or after a direct question |
| Attention | Critical, Risks, Full review | How selective the agent is about changes worth surfacing |
| Response | Concise, Balanced, Detailed | How much evidence, context and next-step explanation appears in the output |
| Rhythm | Daily, Workdays, selected weekly pattern, Manual | When an eligible recurring review may run |
| Special instructions | Project-specific boundaries in plain English | Adds context without replacing access rules or enabled focus areas |
04
Examples of complete configurations
| Need | Suggested configuration |
|---|---|
| Quiet daily delivery oversight | Blockers + Due dates; Guided initiative; Risks attention; Concise response; Workdays |
| Critical launch week | Sprint scope + Acceptance + Workload; Proactive; Full review; Balanced; Daily |
| Invoice monitoring only | Open invoices + Accepted work + Anomalies; Guided; Critical; Concise; Daily or Manual |
| Manual expert assistant | Relevant focus areas; On request; Full review; Detailed; Manual |
05
Write useful Special instructions
- State the project-specific boundary or decision preference, such as escalating any launch-date movement before drafting a client reply.
- Name the intended audience when tone or confidentiality differs between team and client communication.
- Do not paste secrets, credentials or information that the agent does not need for the project responsibility.
- Do not use Special instructions to grant access, bypass approval or enable a disabled reaction; server permissions remain authoritative.
- Review instructions when the project phase changes so old launch rules do not control later delivery.
06
Save rules, then check state
- 1Choose the project object
Agent settings belong to one project-agent relationship.
- 2Configure focus and behavior
Keep only the signals that support this agent's responsibility.
- 3Save the rules
The panel confirms when the configuration is stored.
- 4Start or pause separately
The player-style controls govern whether scheduled work is active now.
07