Working with your agent

Everything a connected agent can read and change in Frostbyte, and what the plugin adds.

View as Markdown View this page as plain text
When your agent finishes a task, its summary and the files it changed land on the task for the team to read.

A connected agent can read your Frostbyte project and change it while it works, with the same access you have. This page lists what it can do, so you know what to ask for. To set one up, see Connect your agent.

When to use it. Check here before asking your agent for something new, or when it says it can't. The MCP reference has the name of every tool behind the list.

What it can read

  • Projects: every project you can open, with progress and its product context.
  • Tasks: lists filtered by status, release, area or a search, and any task in full with its subtasks, implementation notes and attachments.
  • Releases and areas: all of them, and the active release with its progress.
  • What's next: the same ranking as your dashboard's What's Next, plus blocked tasks and recent activity.
  • Signals: the review queue, any signal in full, its screenshots and files, and your Feedback Portal settings.

What it can change

Area It can
Work in progress Start a task, add and check off subtasks, record a decision, flag a blocker, and finish the task with a summary and the files it changed
Tasks Create, edit any property, assign people (including you), move between releases and areas, put on the roadmap, delete
Releases Create, rename, keep the description current, write the changelog headline and release notes, set the active release, complete, delete
Areas Create, rename, recolour, delete
Signals Capture, correct, link to a task, mark reviewed, dismiss, hide from the portal, delete
Projects Create a project and update its product context (owner only)

Deletes are permanent, so each one needs an explicit confirmation from the agent. Deleting an area or release keeps its tasks.

Completing a release can email the people who asked for its work. See Releases.

A session in RollCall

Here's what a coding session looks like from Frostbyte's side when Claude Code picks up task #11, the reminder before a challenge closes:

  1. You ask "Pick up the reminder task." The agent finds #11 and starts it, so it moves to In Progress on the board.
  2. It splits the work into subtasks and checks them off as it goes.
  3. It chooses to send the reminder from the server instead of the phone, and records the decision on the task so you can see why later.
  4. Once the work and any checks you agreed are done, it completes #11 with a one-line summary and the files it changed. Mention #11 in the pull request and GitHub links them.

In Claude Code, the same session looks like this:

Claude Code~/rollcall

Pick up the reminder task.

frostbyte list_tasks(search: "reminder")#11 Reminder an hour before the challenge closes · To Do

frostbyte task_start(#11)Moved to In Progress

frostbyte task_spawn_subtasks(#11)Schedule the reminder job · Skip members who already posted · Write the push copy

I'll send the reminder from the server, so it still arrives when the app is closed.

frostbyte task_log_decision(#11)Send reminders from the server, not the phone

Reminders are scheduled per group, and members who already posted are skipped. Tests pass.

frostbyte task_complete(#11)Done · 3 files changed

#11 is done. Mention #11 in the pull request and GitHub will link it.

To hand over a specific task, choose Copy prompt in the task's ⋯ menu and paste it into your agent. It finds the task, starts it and tracks it the same way.

Its changes show in the task's activity, labelled Claude Code, so you can tell them from your teammates'.

What the plugin adds

The plugin for Claude Code, Claude Desktop's Code tab and Codex connects the same tools and adds guidance on when to use them:

  • Tasks: starts the task you're working on, offers a new task when work is big enough, and completes it with a summary.
  • What's next: answers "What should I work on next?" from your dashboard's What's Next, and dismisses or restores a recommendation when you ask.
  • Planning: turns a goal into tasks in the right releases and areas. It proposes the plan in chat and writes it once you approve.
  • Releases and Areas: reads and manages them when you ask, and drafts a changelog headline and release notes from what shipped, saving them only when you ask.
  • Signals: captures what users reported as you mention it, and goes through the review queue with you: correcting, linking, marking reviewed, dismissing or deleting.
  • Onboarding: picks the right project, and offers to link the repository to it. See Auto-tracking.
  • Docs: answers how-to questions from these docs instead of from memory.

With MCP alone (Claude chat, ChatGPT, Cursor and others), the agent has every tool above but uses them when you ask. Frostbyte still gives every app its core rules: look things up before changing them, put work in the release or area you named, keep a release's description in step with its tasks, delete only after your yes, and stop at a plan limit instead of working around it.

What waits for your yes

Asking for something directly counts as your yes, so "Create a task for this" or "Complete 1.1.0" happens without a second question. Otherwise the plugin tells your agent to ask before it:

  • creates a project, or a task you didn't ask for
  • decides what happens to a signal, such as linking it to a task or dismissing it
  • completes or creates a release it suggested itself

Deletes always wait for a yes in the conversation, after the agent says exactly what will go. Starting, updating and completing the tasks you're working on happen without a prompt, since they're the point of the connection.

Things to note

  • It acts as you. It can open every project you can, not only the one your repository is linked to, and its changes are labelled with the app's name.
  • No Frostbyte AI credits. The AI runs on your plan with Claude, ChatGPT or the app you use. See AI overview.
  • It can't configure your portal. Feedback Portal settings, invites and billing stay in the web app.
  • Turned off User Signals? Signal tools explain that it's off until you turn it back on.

Was this page helpful?

Last updated