Dashboard
See how the project is doing, what to work on next, and what just changed, on the page every project opens on.
Every project opens on its dashboard. It answers three questions in three columns: how the project is doing, what to do next, and what just changed. Everything on it comes from your tasks, releases and signals, and it updates as your team and agents work.
When to use it. Start here when you sit down to work, or when you come back to a project after a few days. To plan or change work, open Tasks or Releases.
What's on the dashboard
| Column | Cards |
|---|---|
| Left | The project card with the pitch and stage, then Project Health and User Signals |
| Middle | Current Focus, then What's Next |
| Right | The active release, then Recent Activity |
The project card shows the logo, name, stage and pitch. Edit the pitch on the Product page.
Set up a new project
A new project shows a setup checklist under the project card. Only the owner sees it.
| Step | Ticks itself off when |
|---|---|
| Create your project | It's ticked from the start |
| Add your first task | The project has a task of its own |
| Plan your first release | The project has a release |
| Connect your coding agent (optional) | An agent is connected, or its setup task is Done |
| Import your tasks (optional) | You tick it yourself |
Your signup answers shape the list. If you named a coding agent, its step moves up and names your tool when it's Claude Code, Codex or Cursor. If you said you use nothing yet, or notes and TODO files, the import step stays hidden.
Select a step to do it, or tick its circle to mark it done by hand. When every step is done, the checklist says you're ready to build. Choose × to dismiss it. If required steps are left, Frostbyte asks first, then removes the checklist and its setup task.
While the checklist shows, Project Health and Recent Activity wait until setup is finished or dismissed. Members who join mid-setup see the normal dashboard.
Read Project Health
Project Health appears once the project has tasks and setup is finished or dismissed. It runs four checks on your open work. Each check is one segment of the bar at the top and one row below it: green passes, amber warns, red fails, and grey is a note that never fails.
| Check | What it looks for |
|---|---|
| Blocked | Open tasks with a blocker. Any is a warning. |
| Stalled work | In Progress tasks no one has updated in 14 days or more. Blocked tasks count under Blocked instead. Any is a warning. |
| Urgent bugs | Open bugs marked Critical or High. One critical, or three or more high, fails. One or two high is a warning. Open bugs that aren't urgent read N open, none urgent. |
| Release | Whether the active release is on pace for its target date. See below. |
Release pace. The check works out how many tasks a week the release's open work needs before its target date, and compares that with how many it closed a week over the last 14 days:
- On track when it's keeping up, Behind pace (a warning) at half the needed rate or more, and Well behind pace (a fail) below half.
- Overdue fails. Ready to ship passes when the release has no open work.
- No target date, or no active release, is a note.
- Until the project has a week of completion history, it reads Not enough history yet.
Open the evidence. A failing row names its first task under the label. If one task is behind it, selecting the row opens that task. If several are, it opens a list of them, and the bugs list links to every open bug. The release row opens the release.
The status tag. It sums up every check, worst first:
| Status | When |
|---|---|
| Unhealthy | Any check fails |
| Stagnant | There's open work, and no task has been updated in 14 days |
| At risk | Any check warns, or there's open work and nothing was finished in the last 7 days (once there's a week of history) |
| Healthy | None of the above |
Hover or focus the tag to see every reason, such as 1 blocked · 1 high bug. Project Health follows these fixed rules; it isn't AI and uses no credits.
Review User Signals
When User Signals is on, its card shows how many signals are waiting for review, the three newest from the last 30 days, and View all for the Signals page.
Rows expand like What's Next. Review signal opens the signal so you can accept or decline it. Dismissing a signal only hides it from your dashboard; it doesn't decline it. Restore it from Dismissed.
When User Signals is off and the project is past the Idea stage, the owner sees a one-click hint to turn it on.
Current Focus
Current Focus is the one goal you're working towards now. Set it on the Product page.
For the owner, selecting the card opens the Product page to edit it, and an empty focus shows a Set a focus prompt. Members only see the card once a focus is set.
Use What's Next
What's Next ranks your open tasks, so the top of the list is the most useful thing to do now. It weighs priority, the active release, due dates and what users have asked for, and it's personal: work assigned to you and work already in progress rank higher. The product stage adds a small lift too, such as bugs once you're Live.
- Up to five tasks. Expand a row to see its tags and why it's there. Start moves a to-do task to In Progress, and Open task opens it.
- One piece of advice can sit at the top: the active release is ready to ship, nearly there, past its target date, missing a date or big for an MVP, or, for the owner, a hint about the stage. Some offer Ask Frostbyte, which asks the Agent to look first and change nothing until you say.
- Setup rows. Once the project has a task, the owner gets a row for each of these that's missing: an active release (Plan a release, listed above your tasks), the product description and areas. Draft with agent hands it to the Frostbyte Agent; Do it myself opens the page.
- No-assignee row. On a project with more than one member, a row flags open tasks with no assignee and opens the task list.
- Dismiss hides a row for you only; it doesn't change the task. Dismissed rows collect under Dismissed, where Restore brings them back. A dismissed no-assignee row comes back when more tasks go unassigned.
When nothing is left, it suggests the next step instead, such as creating a task or planning a release. If everything left is blocked, it lists the blocked tasks.
A connected agent asks for the same list with the whats_next tool, so "what's next?" gets the same answer in your editor.
The active release
The right column starts with the active release's card:
1.1.0
ActiveMake the feed worth opening: favourites, a proper reveal and premium limits.
- Target and the days left come from the release's target date.
- The bar counts Done tasks out of every task in the release.
- The numbers along the bottom split those tasks by status.
Select the card to open the release. With no active release, the card offers to create one. See Releases.
Recent Activity
Recent Activity starts with three totals for the past 7 days: tasks Done, Created and Updated. The feed below lists the latest changes and comments, newest first.
When one person or agent makes several changes in a row to the same item, such as an agent ticking off subtasks, they fold into one line. Choose its updates chip to see each change.
Things to note
- What's Next and User Signals are personal. Your dismissals hide rows for you only. The setup checklist, setup rows and stage hints are for the owner.
- Totals count tasks, not changes. Ten edits to one task count as one task updated.
- Health checks skip setup tasks. The Connect your coding agent task never counts as open work.
Related
Was this page helpful?