Screens
Scan history
Keep a visual record of what changed across commits, branches, and release candidates.
fossil maps your app's screens, states, flows, and visual changes in one local interface.
See your interface clearly before choosing what to improve next.
Screens, states, flows, and changes stay visible together.
Spot stale states, awkward journeys, drift, and forgotten surfaces.
Return to evidence instead of memory or scattered screenshots.
Your target projects stay local by default. fossil analytics does not collect source code, project files, filesystem paths, command output, server logs, screenshots, secrets, license keys, or target-project content. If you connect an AI agent, fossil shares the bounded task context that agent needs for the workflow you started.
fossil is built for web projects you can open or run in a browser, whether it is your product, a client app, an internal tool, or another project you need to inspect. Point fossil at a project with a preview command or reachable URL, and it maps the screens and states it can access.
Yes, if the agent supports MCP. Codex has the most integrated flow in fossil, but you can also connect MCP-capable agents by adding fossil as a local stdio MCP server, then letting the agent request bounded project and exploration context.
Not silently. fossil can read your selected project, run the preview command you approve, and create or update fossil-owned metadata when you choose setup or scan workflows. Any agent-assisted writes are scoped and reviewed against fossil's write policy.
Yes. The first release focuses on the local desktop workbench, and a cloud subscription is planned for teams that need to sync fossil data across people, projects, branches, and review workflows.