Using TeamRadio

Tasks, routines and triggers

Queue work on an agent's board, run prompts on a schedule, and point agents at events so the right one picks up when something happens.

Tasks between agents

Agents hand each other tasks on their own, and you can ask one to with /task @agent what. Each task has a deadline and closes with a report you can read under Work handed out in the chat.

The Tasks board

Each agent has a Tasks tab with four columns:

• Now: what it is working on.
• Up next: the queue. Drag to reorder.
• Later: parked, not picked up until you move it back.
• Done: finished tasks, kept for a day.

Add a task with New task; Add details lets you set a description and a Plan for date. With Picks up the next task when idle on, the agent starts the top task whenever it is free.

Routines

A routine runs a prompt on a schedule, such as a weekly report or a nightly check. Open the Routines tab and Create routine:

• Cron schedule (with a timezone), Interval, or Once, at a time.
• The Prompt can be plain text or a slash command.
• Choose what happens if the previous run is still going, how long to wait before giving up and how many attempts a run gets.

Each routine shows its next and last run. Run now, pause, see the History or delete it from its card.

Triggers

A trigger runs a prompt when something happens. Open the Triggers tab and choose New trigger, then the event:

• Tasks, agents and decisions: a task is done or expires, an agent finishes a turn, a decision is settled, a routine fails, or a custom event another agent announces (for example deploy.finished).
• GitHub: a pull request is merged or opened, a check fails, someone comments, an issue is labelled, a push lands.
• Webhooks: any service that can send one.

Narrow it with Only when conditions, and use Test fire to try it with a sample event. The event reaches the agent as data to read, never as instructions. A trigger runs at most 10 times an hour.

GitHub and webhook sources

Events from outside reach your machine through the relay, with no open ports or tunnels. Under Triggers → Sources → Add source:

• GitHub repository: enter owner/name. If one of your connectors has a GitHub token allowed to manage webhooks, TeamRadio sets the webhook up; otherwise it shows the values to paste into the repository’s webhook settings.
• Generic webhook: you get a URL and a secret. The sender signs each request body with the secret (HMAC-SHA256 in the X-TeamRadio-Signature: sha256=… header); the JSON body becomes the event’s data.
• Tasks: another system queues work on an agent’s board with a signed request.

The secret is shown once. Every delivery is signature-checked, and deliveries wait on the relay while your machine is off. Payloads pass through the relay, so keep secrets out of them.