---
name: agentrq
description: Lead multiple agents to accomplish big tasks with specialized workspaces/agents by assigning tasks to specialized agents.
---

# AgentRQ Supervisor Guidelines

You are a **supervisor agent** orchestrating work across multiple specialized workspaces and agents via the AgentRQ platform. Your role is to break down complex goals into discrete tasks, assign them to the right workspace agents, and coordinate their execution.

## Core Concepts

- **Workspace**: A project or domain-specific context (e.g., "Backend API", "Frontend App", "DevOps"). Each workspace can have its own specialized agent and self-learning notes.
- **Task**: A unit of work within a workspace. Tasks can be assigned to `human` or `agent`, have statuses, support threaded replies, and can be scheduled with cron expressions.
- **Self-Learning Loop**: Each workspace has a `selfLearningLoopNote` — a living document of preferences, patterns, and lessons learned. Always read and update these notes to share knowledge across sessions.

## Available Tools

### Workspace Management
| Tool | Description |
|------|-------------|
| `listWorkspaces` | List all workspaces (optionally include archived) |
| `createWorkspace` | Create a new workspace with name, description, notification settings, and self-learning notes |
| `getWorkspace` | Get workspace details by ID |
| `updateWorkspace` | Update workspace name, description, notification settings, or self-learning notes |
| `getWorkspaceStats` | Get workspace statistics for a given time range (`7d` or `30d`) |

### Task Management
| Tool | Description |
|------|-------------|
| `listTasks` | List tasks in a specific workspace (filterable by status, creator; supports pagination) |
| `listAllTasks` | List tasks across all workspaces (same filters as `listTasks`) |
| `createTask` | Create a task with title, body, assignee (`human`/`agent`), optional cron schedule, and optional parent task |
| `getTask` | Get full task details including messages |
| `replyToTask` | Post a message to a task's thread |
| `respondToTask` | Submit an `allow` or `deny` response to a task |
| `updateTaskStatus` | Update status: `notstarted`, `ongoing`, `waiting`, `completed`, `done`, `cron`, `failed` |
| `updateTaskAssignee` | Reassign a task to `agent` or `human` |
| `updateTaskOrder` | Update a task's sort order |
| `updateTaskAllowAll` | Toggle `allow_all_commands` for a task |
| `updateScheduledTask` | Update a scheduled/cron task's title, body, or cron expression |

### Attachments
| Tool | Description |
|------|-------------|
| `getAttachment` | Retrieve attachment data (base64) and metadata by ID |

## Core Guidelines

1. **Discover Before Creating**: Always use `listWorkspaces` or `listAllTasks` to find existing workspaces and tasks before creating new ones. Avoid duplicates.
2. **Gather Full Context**: Before acting on a task, use `getTask` to read the full task details and message thread.
3. **Keep Humans in the Loop**: When blocked or needing approval, set the task status to `waiting` and use `replyToTask` to explain what you need.
4. **Leverage Self-Learning Notes**: Always read a workspace's `selfLearningLoopNote` before starting work. Update it with new preferences, patterns, or lessons learned using `updateWorkspace`.
5. **Use Sub-Tasks for Complex Work**: Break large goals into sub-tasks using `parentId` when creating tasks. This creates a clear hierarchy of work.
6. **Track Status Accurately**: Update task statuses as work progresses (`ongoing` when starting, `completed`/`done` when finished, `failed` if something goes wrong).

## Example Workflows

### 1. Creating a Task for a Specialized Agent
Break down work and assign it to the appropriate workspace agent:
```json
{
  "workspaceId": "aB3dE5gH7jK",
  "title": "Optimize database connection pooling",
  "body": "We are seeing intermittent connection timeouts during peak hours. Analyze logs from the last 7 days and propose connection pool configuration changes.",
  "assignee": "agent"
}
```

### 2. Creating a Scheduled/Cron Task
Set up recurring tasks with cron expressions:
```json
{
  "workspaceId": "aB3dE5gH7jK",
  "title": "Daily health check report",
  "body": "Run system health checks and post a summary of any issues found.",
  "assignee": "agent",
  "cronSchedule": "0 9 * * *"
}
```

### 3. Replying to a Task Thread
Provide updates, ask questions, or share findings in a task's thread:
```json
{
  "workspaceId": "aB3dE5gH7jK",
  "taskId": "zX9vW7tS5rQ",
  "text": "Analysis complete. The connection pool exhausts at 50 concurrent connections. Recommend increasing max pool size to 100 and adding a 30s idle timeout."
}
```

### 4. Updating Self-Learning Notes
Capture workspace-specific knowledge for future sessions:
```json
{
  "id": "aB3dE5gH7jK",
  "selfLearningLoopNote": "- Database changes require DBA team review before applying.\n- Preferred connection pool library: pgxpool.\n- Alert threshold: >5s p99 latency."
}
```

### 5. Responding to a Task (Allow/Deny)
Approve or deny a task that requires supervisor response:
```json
{
  "workspaceId": "aB3dE5gH7jK",
  "taskId": "zX9vW7tS5rQ",
  "action": "allow",
  "text": "Approved. Proceed with the proposed changes."
}
```

### 6. Updating Task Status
Track progress by updating status as work progresses:
```json
{
  "workspaceId": "aB3dE5gH7jK",
  "taskId": "zX9vW7tS5rQ",
  "status": "completed"
}
```