Everything we've shipped

Session Handoffs and a New Agent

Your connected agent can leave a session handoff when you finish for the day, and it writes one itself when it stops with work unfinished. A handoff says what got done, what to do next and what to watch out for. The newest one pins to the top of Recent Activity on the dashboard for 7 days, and choosing it opens the whole thing.

The next session gets the handoff back with its first read of the project, so there's nothing to paste in. Frostbyte keeps the last three, so two agents working side by side don't overwrite each other, and the older ones open from Recent Activity.

For things that aren't tasks, such as how the app is put together, agents keep up to five notes under Context on the Product page. Any connected agent can look them up when it needs that background, and add to them as it learns more. Notes and handoffs are read-only in Frostbyte, any member can delete one, and they work on every plan.

A redesigned Frostbyte Agent

The Agent has a new look. Open it from the Agent button at the bottom right of any project page, or press ⌘J (Ctrl J on Windows and Linux). The panel grows out of the button and folds back into it, and closing it keeps your conversation. History and New chat sit in its header.

Before you type, it lists up to three things in the project that need a decision, most pressing first, such as an urgent bug, a blocked task or signals waiting for review. Select one and the Agent starts on it. The suggestions themselves don't use AI credits.

Area cards show the open work in each part of the product, what's blocked and who's on it, with the most recently active areas first. Choose Write description from a card's ⋯ menu and the Agent writes the area's description for you.

Moving from another tool is easier

Import reads exports from Linear, Jira, Asana, Notion, Trello, ClickUp and GitHub for tasks, and from Canny and Featurebase for feedback. Open the project's ⋯ menu, choose Import, and pick where the file's from to see how to export it from that tool. Frostbyte matches each column to a field and each status to what it meant there, and you can change any of them before you import.

Import as Tasks, Signals, or Signals and tasks. Releases and areas come across where the tool has them, such as Linear's cycles and projects. Imported signals stay off your Feedback Portal unless you tick Show them on your feedback portal, and only the project owner sees requester names and emails. Only the owner can import, and every task it creates counts towards your plan's limits.

Pull requests move your tasks

Write FB- and the task number in a commit or pull request, such as Fixes FB-13, or name the branch after the task, and it links to that task. Turn on Move tasks with pull requests under GitHub in Project settings, and opening a pull request moves its task to In Progress. Merging one that closes the task into your default branch moves it to Done.

The task's GitHub section shows each pull request's lines added and removed, how many files it touches and, while it's open, whether it's approved. When a reviewer asks for changes, the card turns orange with Changes requested. Reviews don't move the task.

Project Health, What's Next and Changelogs

Every project's dashboard has Project Health, which checks your open work for blocked tasks, stalled work, urgent bugs and whether the active release is on pace for its target date. Release pace compares how many tasks a week the release still needs with how many you closed over the last two weeks. Each check is a segment of the bar and a row below it, and a failing row names the task behind it so you can open it straight away.

The tag at the top sums it up as Healthy, At risk, Stagnant or Unhealthy, and hovering it lists every reason. Project Health follows fixed rules and uses no AI credits. Beside it, What's Next ranks up to five open tasks by priority, the active release, due dates and what users have asked for, with work assigned to you and work already in progress ranked higher.

Expand a row to see why it's there, press Start to move it to In Progress, or dismiss it for yourself. At most one piece of advice sits above the list, such as a release that's ready to ship or past its target date, and some offer Ask Frostbyte, which has the Agent look first and change nothing until you say. A connected coding agent gets the same list from the whats_next tool.

Set your product's stage and focus

The Product page is a four-line brief you edit in place, covering what you're building, who it's for, the problem it fixes and why your approach wins. Set up with Agent asks a few quick questions and writes it for you. Everyone on the project can read it, and so can the Frostbyte Agent and any agent you connect, before they plan or suggest work.

Pick a stage from Idea, MVP, Live and Growth, and the line under it says what that stage is about. It describes where you're aiming now, so nothing locks and nothing changes it for you. Current Focus is the one goal you're working towards now, such as "Get half of new signups to finish onboarding", and it shows on the dashboard.

The stage shapes the advice you get. At MVP, work already in progress in the active release ranks higher in What's Next, and a release much bigger than you usually ship gets flagged. At Live, bugs and requested work rise. If what you're doing doesn't match the stage, such as shipping releases while set to Idea, the owner gets a hint to move it.

Changelog posts with a headline and cover

Release notes are posts on your Feedback Portal's changelog. Each one has a headline, an optional cover image, images inside the notes, and your name as the author. A post's own page lists everything in the release, with a Built from your feedback card showing the requests and votes behind it.

Auto generate drafts the headline and notes from the release's Done tasks and the portal requests linked to them. The changelog is on every plan. Covers and images need Indie, and a release can hold up to 10.

The rest of the portal has a new look too, with one composer, a feed beside a sidebar, and request pages that show where each request is up to, such as Planned or Shipped. While the public roadmap is on, a task drafted from a public request starts ticked to appear on it. Untick it in the draft to keep it off.

Connect your agent on Free

Claude Code, Codex, Cursor, Claude chat and ChatGPT connect to Frostbyte on every plan, Free included. Open Settings → Connections → Connect your agent and follow the steps for your tool.

A Free project also holds three people, you and two others, and there's no limit on areas. Free includes 250 tasks and two open releases.

Quick Edit and Chat Connections

Claude chat and ChatGPT can now connect to Frostbyte without a token. Open Settings → AI agents, pick one, add the MCP URL as a custom connector in that app, then sign in to Frostbyte and approve access.

Each connection shows up in Settings next to your tokens, with the app's name, and you can revoke it there. Claude Code, Codex and Cursor still connect with a token, the same way as before. This launched on Indie and above and is now on every plan, Free included.

Quick edit covers more of the task

Quick edit now has the description, area and release alongside status, type and priority, so most small changes no longer need the full task modal. Saved changes show on the card straight away and don't flicker back while the save finishes.

It opens on whichever side of the card has room. On phones it's off, and tapping a card opens the task as usual.

Help while you write a task

As you type in New task, Frostbyte suggests a type, area and release as chips under the title. Tap one to use it. It never changes something you've already set yourself.

Polish task is in the New task modal too, so you can tidy the title and description before creating it. If you'd rather it happened every time, turn on Auto-polish tasks I create in Settings → Preferences. Each polish uses about one AI credit from the project.

Agent Setup and Task Activity

Settings → AI agents now starts by asking which tool you use: Claude Code, the Claude desktop app, Codex, Cursor or another MCP tool. Each one gets at most three steps with a copy button, and the token is already filled in for you.

The dialog waits for your agent's first call and then shows Connected. The Connect your agent step in the setup checklist opens the same dialog, and ticks itself off once your agent has been in touch.

Agents can also do more once they're connected. They can read task and signal attachments, clear a task's release or area, set a release's launch date, and delete tasks, areas or releases after you confirm in chat. Task, release and area names in their replies link straight to Frostbyte.

Comments and more than one assignee

Tasks have comments. Type at the bottom of Activity, press Enter to send and Shift+Enter for a new line. Your agent's decisions land in the same thread with an Agent badge, long notes fold to two lines with Show more, and the list of changed files folds behind a count.

A task can be assigned to several people. Their avatars stack on the card, and assignee changes sync to linked GitHub issues.

Find work and keep releases tidy

The Tasks page has a search box that narrows every lane to tasks whose title matches. A lane with no matches says so.

New tasks still join the active release by default. If you'd rather they start in the Backlog, turn off Add new tasks to the active release in Settings → Preferences. Completed releases are folded away in release pickers, and creating a release is one short flow.

Multi-select and Filters

Press Select on the Tasks board, or Cmd/Ctrl-click a card, and clicking picks tasks instead of opening them. Shift-click selects a range, and on a phone or tablet a long press starts a selection.

A bar shows how many you've picked and lets you move them all to a new status, release, area or type, or delete them, up to 200 tasks at a time. You can also drag any selected card into another lane and the rest of the selection goes with it.

The Tasks header has a Filter menu for type and area, and you can pick more than one of each. Sort sets the order: Manual keeps your drag order, Last edited puts recently changed tasks first, and Newest puts the latest additions on top. A task you create while filtered picks up that type or area, so it doesn't vanish from view the moment you save it.

User Signals is now optional

Not every project needs a feedback queue on day one. Project owners can switch User Signals off under Features in the project ⋯ menu. While it's off, Signals disappears from the sidebar, the dashboard and your tasks, your public portal shows "Feedback paused" on the same URL, feedback-shipped emails stop, and the MCP tools and in-app Agent decline Signals requests.

Nothing is deleted. Switch it back on and your signals, votes and portal are as you left them. New projects at the Idea stage start with it off, and once a project moves past Idea the dashboard offers to turn it on with one click.

A tidier task modal

Empty Implementation notes, Subtasks and Attachments sections no longer take up room on every task. They fold into small chips under the title. Click one and the section opens ready to type or pick a file, and if you back out without adding anything it folds away again.

You can drag files straight onto an open task to attach them. Drop them on the New task modal and they upload as soon as the task is created.

Public Changelog

Your Feedback Portal now has a Changelog tab, a public timeline of the releases you choose to publish. Each entry shows your release notes and the tasks that went out with it, grouped into new features, improvements and bug fixes with their area labels.

Nothing appears until you publish it. Complete a release that has notes and Frostbyte asks whether to put it on the changelog, or publish or remove any completed release later from its Changelog property. If a release moves back out of Completed, it comes off the page automatically.

Shipped emails link to the entry

When feedback ships and Frostbyte emails the person who asked for it, the email now links to that release's changelog entry.

On every plan

The changelog is on every plan, including Free. To keep it private, switch it off in your portal settings.

Images and Files

Projects can now have a logo and people can have a profile picture. Upload an image and Frostbyte resizes it and shows it everywhere that project or person appears.

Uploads are stored privately and served through Frostbyte, not from a public bucket.

Attachments on tasks and feedback

Tasks and Feedback Portal submissions now take attachments: images, PDFs, plain text and CSV files.

Task cards show a badge when something's attached, and clicking an image opens it full size instead of downloading it. People submitting to your public Feedback Portal can attach a screenshot too.

The navbar moved into the sidebar

The navbar is gone. Your account, your projects and your most-used quick actions are in the sidebar, and creating a project opens an overlay on top of the app instead of a separate page.

New projects open with a short guided setup and a Feedback Portal already provisioned, so you can share a link straight away.

Password reset and project limits

You can reset a forgotten password from the login page. If you hit your plan's project limit, you can archive a project from the Projects page to make room.

Signals

User Signals replaces the old Inbox and the separate feedback and bug queues with one page you review. Feedback Portal submissions, bug reports and your own notes all land there.

Capture a signal yourself from the page, or let your coding agent capture one over MCP while it works. Each signal shows its type and source, and public submissions show their votes.

Every signal gets a decision

Open a signal and choose Create task, Link to existing task, Save for later or Dismiss, which asks for a reason. Each decision records who made it, when and why, and stays on the signal.

Accepted work goes to your Backlog

Accepting a signal creates a task in your Backlog, not your active release, and Tasks has a new Backlog view to hold it.

The linked signals stay on the task with their votes, so you can see what people asked for when you plan the next release.

Setup and Settings

Settings is now grouped into compact rows instead of a long scroll of boxes, so your plan, email preferences and account controls are easier to find.

A popover in the sidebar shows your plan, what's included and how many AI credits you have left before the next reset.

The setup checklist moved to the dashboard

The setup checklist now sits on the dashboard instead of in a modal, and you can do each step from there. An empty project's dashboard also says what to do next.

Areas and releases explain themselves the first time you open them.

Emails that follow your setup

Lifecycle and billing emails were rewritten and there are more of them. They follow where you are in setup, and paid plans get notice before a trial ends and when a payment fails.

You now have to verify your email before you can use the product.

Frostbyte Agent

Every project page has a Frostbyte Agent button in the bottom corner. Open it and ask what's active, what's blocked or what to ship next. It answers from your project's tasks, areas and releases, and it can change them for you.

Replies stream in as it works. Minimise the panel and the conversation stays, close it and the conversation clears. Past chats are in the history menu, where you can reopen or delete them.

The agent runs on AI credits, which now go by usage instead of a fixed cost per action. A bigger job costs more than a small one. Your monthly usage and reset date are in Settings.

You approve anything destructive

Routine changes, like creating a task, moving a status or drafting a release, apply as you watch. Anything destructive, like deleting work, waits until you approve it.

A Product page for what the agent should know

The new Product page holds your product stage, One-line description, Target user, Problem to solve and Why this wins. Agent context is a free-form field for anything else an agent should know.

The agent reads this page before it helps, so the tasks and releases it suggests fit your product.

New projects start with guided tasks

New projects open with a short set of tasks: Enter product context, Create your areas, Plan your first release and Connect your coding agent, which covers Claude Code and Codex. You can hand each one to the agent if you'd rather not do it yourself.

These replace the setup checklist and the auto project setup from v1.7.0.

Custom Domains & Embed Widget

On Studio, your public Feedback Portal can now run on a subdomain you own. Point it at the portal, add the records Frostbyte shows you and verify.

If you'd rather not touch DNS, Indie and Studio projects can claim a name.getfrostbyte.dev subdomain in one field. Portals also moved to clean root-path URLs.

Embed feedback on your own site

On Studio, a new widget puts your bug, feature and general feedback forms on your own site with one script tag, copied from Feedback Portal settings. Your users can submit without leaving your app.

Remove the Frostbyte branding

Studio projects can also remove the "Powered by Frostbyte" branding from their portal.

New plan names and limits

Basic is now Indie and Pro is now Studio. Projects can have 1 collaborator on Free, 5 on Indie and 10 on Studio, and Free projects can have 100 active tasks.

Agent Auto-Tracking

Until now, you had to remind your agent which Frostbyte project it was working in at the start of every session. Add a small .frostbyte.json file to the repo, commit it, and new Claude Code or Codex sessions start with the right project.

The link file holds only the project ID. On session start, a hook reads that ID and tells the agent which project to use. The authenticated read still happens through the MCP server you already connected, so the hook never touches your API token or sends code anywhere.

Your agent keeps the task list current

Once the agent knows the project, it can update the task list while it works. It starts the task you asked for, suggests a new one when the work is big enough to track, adds subtasks to work in progress and marks finished tasks done with a short note on what changed.

New tasks go into the best-fitting existing area when there is one. Releases are left alone unless you ask. Creating a project, linking a repo, opening a task or creating an area still needs your explicit yes.

Onboarding, and a few MCP fixes

In a repo that isn't linked yet, the new onboarding skill offers to sort it out at a natural point. For a fresh codebase, it can create a Frostbyte project and seed the first tasks. For an existing one, it can match the repo to one of your projects and write the .frostbyte.json file.

We also corrected the plugin's area and release tool references so the agent calls MCP tools that exist, and added Auto-tracking docs with the Claude Code and Codex setup paths.

Auto Project Setup

New projects now open as soon as you create them. You can rename things, invite people and write tasks without waiting for AI setup, which is now an optional step.

If you want help, the AI setup flow opens once the project exists. Describe the product, review the generated areas, releases and starter tasks, then apply the plan.

A starter workspace you can edit

After setup runs, the project has scoped tasks, product areas and an active starter release. All of it is editable.

Setup can fail without breaking your project

If a setup run fails or has to roll back, the project stays usable and the modal tells you how to retry.

Before saving generated work, Frostbyte checks it against your plan's area and release limits and tells you if it won't fit.

Feedback Loop

AI-assisted setup can turn a product description and connected repo context into starter areas, releases and tasks, so your agent has a backlog before its first session. New MCP planning tools let your agent do this work too.

Releases are easier to start and write up

The New Release modal suggests the next name, and descriptions can be prefilled from completed task titles. Releases also have a public release notes field, and Auto generate drafts the notes from what shipped.

When an agent creates a release over MCP without a name, create_release suggests one too.

More ways to act on feedback

People can vote on your public roadmap. In your project's review queue, now User Signals, you can moderate submissions, rewrite them with AI, convert them into task-ready copy and link them to existing tasks. When linked feedback ships, the person who sent it gets an email.

AI actions now draw on a pooled credit balance with limits per plan. Setup, release and feedback actions show their cost inline, and Frostbyte tells you when you've run out.

CSV Import and Onboarding

CSV import and export now live in each project's settings dropdown. Bring tasks in from another tool, or export them with filters for type, release, area and status.

Import progress stays with the project you're working in, and how much you can import depends on your plan.

A setup checklist for new projects

New projects have a setup checklist that remembers what you've done. It replaces the old quick-start modal, and the new-project and onboarding modals were refreshed.

Emails for assignments, feedback and setup

Frostbyte now emails you when you're assigned a task or someone submits to your Feedback Portal. Lifecycle emails bring you back to unfinished setup and release work, and paid plans get billing emails. A new unsubscribe page controls what you receive.

Releases Upgrades

The Releases page now opens with your active release next to its in-progress and open tasks, in priority order. You can see what's left to ship without opening each one.

Each release card has a ⋯ menu to edit it, set it as active or delete it without leaving the page. Setting a new release as active demotes the previous one for everyone in the project straight away.

A list view for tasks

The Tasks page has a new list view. Switch between board and list from the toolbar, and it remembers your choice. Both views have collapsible sections, so you can fold away any status you're not working on.

Each section has a + button that adds a task with that status. The count in each section header updates as cards move.

Active release in the sidebar

The project sidebar now shows your active release with its name, target date and a progress bar that updates as tasks complete.

MCP Server

Frostbyte now has an MCP server. MCP (Model Context Protocol) is the open standard AI assistants use to connect to other tools, so Claude and any other MCP client can work with your projects directly.

Ask Claude to create a task, move one to Done, list what's in progress or set up a release. It reads and writes your Frostbyte data.

The server has 16 tools. They list and create projects, tasks, areas and releases, update them, delete tasks and read a project's activity feed.

Connect it with an API token

There's nothing to install. Go to Settings → API Access and click Generate token. The token is only shown once, so keep a copy.

Then point your client at https://getfrostbyte.dev/mcp with the token as a Bearer header. The docs have the full setup. API tokens are on the Basic and Pro plans, and Revoke token cuts off access at any time.

Feedback Portal & Public Roadmap

The Feedback Portal is a page you can share where people report bugs, suggest features and give general feedback. Submissions land in a review queue, now User Signals, where you accept them into tasks or decline them.

Each form asks for different things. Bug reports ask for severity and repro steps, feature suggestions ask for the use case and why it matters, and general feedback is open. Pro gets all three, and Basic gets bug reports.

A public roadmap

Turn on roadmap visibility for a task and it appears on a roadmap page in your Feedback Portal, grouped into Planned, In Progress and Completed.

Tasks move between columns when their status changes. The rest of your project stays private.

Send accepted submissions to a release

Accepted submissions can join your active release automatically, with separate switches for bugs and feature requests. New submissions appear in your queue in realtime.

Task Assignments and PDF Export

You can assign a task to a teammate when you create or edit it. Their avatar or initials show on the card and in the activity feed, and assignee changes sync with GitHub.

GitHub links in task modals

Task modals now show linked GitHub commits, pull requests and issues. The sync controls are clearer about what gets pulled in and when, and syncing existing tasks and releases shows its status as it runs.

Export a project to PDF

The new Export modal turns a project into a PDF, with filters and three modes: kanban, diagram and full. Diagram mode draws the project with Mermaid.

GitHub Integration

You can now link GitHub repos to Frostbyte projects and keep tasks in sync with issues and pull requests. Task badges now use a # prefix (#123), so you can reference tasks in commits and PRs the way you would on GitHub.

Set it up from Frostbyte

Install the GitHub app from your project or account settings, then use the GitHub integration modal in the project dropdown to choose which repos link to which projects. You can have more than one installation. GitHub features need a verified email.

Bug Reporter

Each project can have a public bug reporter, a simple page people can use to send you bug reports. The setup modal says where reports end up, you can switch it on or off, and the form no longer asks for fields nobody used.

Project members and a free plan

You can now invite people to a project, revoke an invite and manage members. There's also a free plan, with up to 3 projects.

Your account

Accounts now have email verification and Google and GitHub linking. There are new profile and settings pages, and you can delete your account from Settings after confirming.

Launch

The first version of Frostbyte is live. It's a lightweight project planner for developers and small teams, whether you're building a SaaS product, a mobile app or a game.

Tasks, areas and releases

Frostbyte is built around three things. Tasks are the work, whether that's a feature, a bug or an improvement. Areas group related work by system or component. Releases collect work into a milestone with a target date and progress.

A dashboard for each project

Each project has a dashboard showing its health, active release, current tasks and bugs and recent activity, plus a board view for its tasks. A Quick Start guide helps you set up the first areas and tasks.

You edit work in modals, changes show up for everyone in realtime, and you can sign in with email or Google.