FEATURE.GRAPH · MAC DESKTOP BETA
A codebase, organized by what it does.
A development environment for working with Claude Code and Codex: map a codebase, propose a feature, run the implementation, and review the change before keeping it.
I use Feature.graph for all my coding.
Watch the product tour
A six-minute tour of the workspace, from opening a project to keeping a working change. It covers the product map, planning, design previews, coding agents, file editor, terminal, testing, history, project questions, and GitHub controls.
Download the video → Read the timestamped transcript →
What the tour covers +
Product Home, opening a repository, new-app setup, and connections to Claude Code, Codex, and GitHub. The real Feature.graph repository is mapped into 120 features across 187 files, followed by focused views, feature evidence, and repository understanding.
In a demonstration app, I request a Completed filter, review its proposal and desktop/mobile design previews, then run a real Codex implementation. I inspect the changed files, try the working filters with the mouse and keyboard, review nine passing checks, and keep the change locally. The feature’s history retains the request, plan, build, and acceptance decision.
The tour also covers the interactive terminal, app preview settings and output, saved project conversations, map freshness and source assessments, suggested next steps, command logs, and GitHub repository visibility controls. Setup and publication controls are shown without creating a new app or GitHub repository.
Build and code views use an isolated demonstration app. Private source and private GitHub URLs are not shown.
Map an existing repository
This is Feature.graph running on its own source repository. The map groups code into product capabilities, with the source-file counts visible. The scan identified 120 features across 187 project files; this focused view shows the repository-mapping branch.

Inspect a capability
Selecting a feature opens its description and the evidence behind the mapping. Inferred capabilities are identified separately from work that has been built and reviewed.

Join the Mac beta waitlist
I use Feature.graph for my own development. Leave your email if you’d like to try it when beta access opens.
Request a demo →Read the project notes →