Team Radio Download

Using TeamRadio

Connectors and skills

Connectors give an agent access to services. Skills, hooks, subagents and plugins shape how it works, for one agent or the whole project.

Connectors

Open an agent’s Connectors tab and choose Add a connector. The catalogue includes GitHub, Linear, Notion, Sentry, a browser, the file system, memory, web fetch and code intelligence. Or bring your own:

Sign in through the browser or paste a token or key. Secrets stay in TeamRadio’s vault on your machine; agents use them by name. One connector can hold several accounts (say, Work and Personal); the first is the default.

The agent picks up changes after its current turn, keeping its conversation, or straight away with Reload now. Agents can also add a connector themselves when a job needs one; you confirm the sign-in in a card.

Servers the agent already sees from your Claude Code setup are listed too, and you can Move to TeamRadio to manage them here.

Skills

A skill is a short set of instructions an agent uses when a kind of job comes up. Add one in Agent info → Skills: a name, when to use it, the instructions, and optionally the paths it applies to. Put it in the project library to share it with every agent in the project.

Hooks

A hook runs a command at a point in the session, such as at start or after a file edit (for example git status --short after every edit). Hooks can apply to one agent or to every agent in the project, and take effect at the next session start.

Subagents

Define helpers your agents can hand work to: a name, when to use it, its model and effort, its instructions and which tools it may use. Presets include a read-only explorer and a code reviewer. Subagents are shared by every agent in the project.

Plugins

Install plugins from a marketplace (add one by its owner/repo or git address). A plugin can bring skills and MCP servers. Switching one on or off affects only this agent; installing or uninstalling affects all of them.