Dashboard Guide

The FreeRide dashboard at freeride.dev is where the human steers the project. Everything your agents capture — in coding sessions and in chat — surfaces here for you to review, organize, and plan from: progress, ideas, decisions, documents.

Home

Your project at a glance. The home page shows:

Project Overview — a living document that your agent maintains and updates across sessions. Editable directly from the home page.
Recent Activity — a timeline of everything that's happened: completions, decisions, new documents, session starts and ends. Filterable and searchable.
Latest Session — a summary of the most recent conversation, what features were worked on, and what was accomplished.
Features — your in-progress features at a glance.
Ideas — critical and high-priority ideas waiting for attention.
Planned — items you've flagged for upcoming work.

Features

Your project's structure. Each feature represents a major area of work — Authentication, Dashboard, Search, API — with its own status, priority, ideas, decisions, documents, and progress history.

Feature statuses: backlog → planned → in progress → review → done. Status transitions happen naturally — when the agent starts working on a backlog feature, it moves to in progress automatically. You can also change statuses manually from the dashboard.

Click into a feature to see everything related to it: its story (description + completions timeline), documents, ideas, decisions, and file mappings.

Mentions. When something written on one feature matters to another, mention it. Type @ in an idea's description and pick the feature, or ask your agent to mention it. The mention shows as a chip that links to that feature. The record stays where it was written, and it also appears on the mentioned feature's Mentions tab and in its agent context, so whoever works there next sees it.

Features with parts

Some features are big enough to have parts of their own — a sub-product, or a set of clients. A feature with parts shows as one stacked card with the number of parts, their icons, and a status bar across them.

Open and close it in place — click the card, or the "parts" badge, and its parts slide into the grid right after it. Click again to fold them back.
Go to the feature itself — choose Open from the card's "…" menu. Its page has its own ideas, docs and decisions, plus the work done across all its parts.
Organize by hand — drag a feature onto another to group them, onto a feature with parts to add it, or onto empty space to take it out. You can also set Part of when editing a feature, or use the "…" menu to add a part or ungroup. On a phone, press and hold a card to drag it.
Or just ask your agent — "group these under Dunkman" works too. When your agent works on a part, it also sees the decisions and docs of the feature it belongs to.

In activity feeds, a part shows as Dunkman / Parser so you always know where it belongs.

Ideas

Every idea your agent captured during conversations, organized and actionable.

Filter by feature, priority, or status — find what matters
Sort by priority, newest, or oldest — surface what's urgent
Edit inline — change titles, descriptions, priorities, or reassign to a different feature
Plan items — mark ideas as "planned" to flag them for upcoming sessions. Your agent surfaces planned items at session start.
Dismiss — ideas that no longer matter can be dismissed without deleting. The history is preserved.

This is where your thinking becomes your roadmap. The ideas that flow naturally during conversations become the organized backlog you ship from.

Documents

All knowledge documents across your project. Your agent creates and maintains these during the workflow — implementation details, architecture notes, guides, project overview, vision docs.

Grouped by feature — or browse project-level docs that span multiple features
Read and edit — view documents with full markdown rendering, or open the editor to make changes directly
Seven document types — overview, implementation, architecture, guide, backlog, UX flow, vision

Documents stay current because the agent updates them as part of the work cycle. When you review them on the dashboard, you're reading documentation that reflects the actual state of your project — not something written three months ago and never touched.

Decisions

Every architectural and design choice your agent captured, with the reasoning behind it. Grouped by feature or viewed chronologically.

When you're wondering "why did we choose PostgreSQL?" or "when did we decide to switch to OAuth?" — the answer is here, with the alternatives that were considered and the context behind the choice.

Sessions

The history of every conversation. Each session shows when it happened, how long it lasted, which features were worked on, and a summary of what was accomplished.

Useful for tracking the arc of your project over time. You can see patterns — which features get the most attention, how often sessions happen, what the recent momentum looks like.

Learnings

Insights and discoveries captured during development. Concept explanations, debugging findings, technical knowledge worth preserving. Tagged and searchable.

The Dashboard Philosophy

The dashboard is where the human side of the workflow lives — see what's happening, steer what comes next, review what was decided. Most of the project knowledge accumulates automatically during your coding sessions, but the dashboard is fully editable: rename features, reprioritize ideas, change statuses, run whatever planning flow fits your work. The thinking happened in your conversations. The dashboard is where you organize, plan, and act on it.

How It Works → — the workflow that fills the dashboard
Tools Reference → — what your agent calls during sessions
Customization → — adjust what your agent logs