Stop paging code into your head

Unfault is a CLI and editor extension that leaves context breadcrumbs across your codebase.

See how your functions connect and where your logic flows, without leaving your editor.

unfault context
create_access_token()
Heads up No error handling, Missing request timeout
Reachable from POST /login
Call path
POST /login
impacts slo Avail 99.9% Error <1% p95 <500ms
└─ login()
   └─ app/auth.py:create_access_token() ← you are here
      └─ app/auth.py:validate_access_token()
Install Unfault Docs VS Code

We carry too much of the codebase in our head.

Unfault builds the context of your code. Functions, dependencies, routes, SLOs and how they connect.

VS Code

Follow
the route.
See the path.

This is the part nobody writes down. Traces show up long after the facts.

auth.py - Visual Studio Code
def create_access_token(data):
# Your code here
Context
create_access_token()
auth.py:27
POST /login · POST /register
← login() ← create_access_token() ← validate_access_token()
CLI

Ask once.
Stop
digging.

Deterministic graph traversal. Unfault maps the actual logic paths between your files, giving you ground truth, not an AI guess."

❯ unfault ask "what's the authentication flow?"
Traversing code graph...
→ Found 5 related modules
→ Tracing call paths from API routes...
Authentication flow
1. Request hits POST /login
└─ calls create_access_token()
└─ calls validate_access_token()
└─ uses fastapi, sqlalchemy, datetime
Graph context: 31 nodes, 26 edges traversed
VS Code + CLI

Edit with
eyes open.

Ambient Observations. Unfault bubbles objective facts about your code's neighborhood, like missing error handling or high-impact paths, so you can prioritize your focus.

auth.py - my-project - Visual Studio Code
Unfault: Context
File
Important file auth.py
Imported by 4 · Imports 5
6 files depend on this
Direct: 3
Symbol
create_access_token

Reachable from POST /login. Called from 2 places.

Impacts SLO
Avail 99.9% p95 <500ms
Worth a look
No error handling
A Note from the Builder
I've spent 25 years in OSS, and I still get lost in my own code after a few months away. I built Unfault to be the breadcrumbs I wish I'd had back then. It currently shows you the 'Facts' of your system. I'm still working on the part that recreates your past mindset. Hope it helps you keep a healthy relation with your code.
- Sylvain
Privacy

Your code
stays yours.

Your source code never leaves your machine. We sync only the structural graph (symbol names and relationships) to materialize findings and semantic facts.

Try unfault on your code
Read docs