A terminal guide to the code you didn't write

Understand your app.
Finally.

appwalk walks you through your own code — how it starts, what each folder does, what's risky, and the words to say it back to an AI. It taught its founder that `.js` means JavaScript. It'll do the same for you.

0Dependencies
No AI keyRequired
7Tools
Scroll
Guided TourFile TreeSafety Audit Ask About a FileFlow MapYour Setup GlossaryFree ForeverZero Dependencies
See it work

It's real. This is the actual tool.

Nothing on this page is mocked up. These are screenshots of appwalk running against a real project.

appwalk — guided tour
┌─ Guided tour · step 1 of 7 ────────────────────────────────────────────────┐

│   ▶  What this app is                                                      │
│                                                                            │
│   I can see 5 files. It looks like a Node.js app.                          │
│                                                                            │
│   That just means: it's an app written in JavaScript, and "Node" is        │
│   the program that runs JavaScript outside a web browser.                  │
│                                                                            │
│   The `.js` in file names stands for JavaScript — not JSON. JSON is        │
│   something different, and we'll meet it next.                             │
│                                                                            │
│   Any word you don't know — press g and I'll explain it.                   │

└────────────────────────────────────────────────────────────────────────────┘
tour                    ← back · Enter next · o = open · g = glossary · h = home
Tour

One concept at a time

It starts with your app and teaches the words as it goes — the `.js` = JavaScript lesson happens in your own project.

appwalk — tree
┌─ demo-app ─────────────────────────────────────────────────────────────────┐
│   ▾ api/   (1 item)                                                        │
│       routes.js         js · 161 B                                         │
│     db.js             js · 45 B                                            │
│   ▾ handlers/   (1 item)                                                   │
│       ping.js           js · 47 B                                          │
│   ● index.js          js · 202 B                                           │
│   ● package.json      json · 136 B                                         │
│                                                                            │
│   ▸ .env — location only                                                   │
│      why: holds secrets (API keys, passwords).                             │
│      Keep it gitignored — commit it and anyone can read them.              │
│                                                                            │
│   ● = entry point (where the app starts) · plain = a regular file          │
│                                                                            │
└────────────────────────────────────────────────────────────────────────────┘
tree                      ↑↓ move · ←/→ collapse · Enter open · a audit · q quit
Tree

Every file, plainly

Green marks where your app starts. Nothing hidden, nothing jargon.

appwalk — audit
audit: 3 of 5 clean (2 findings)
  .env .env file is present in the project tree
    — fix: .env holds secrets (API keys, passwords) — if it was ever committed, treat those as leaked. Rotate each key at the service that issued it, put the new ones in .env, add .env to .gitignore, run `git rm --cached .env` so it stops being tracked, then purge history (git filter-repo) so old commits stop exposing it. Gitignoring alone does NOTHING for a .env already committed.
  package.json no lockfile — installs are not reproducible
    — fix: Run your package manager's lockfile generator (e.g. `npm install`) to pin exact versions.
Audit

Leaks, junk, risks

A safety scan of the code you didn't write — every finding comes with a fix.

appwalk — flow
┌─ How it fits together ─────────────────────────────────────────────────────┐
│ ● start → index.js — starts the app                                        │
│ ├─→ api/routes.js — wires requests to handlers  (+1 more)                  │
│ └─→ handlers/ping.js — handles one request                                 │
│                                                                            │
│   depth 1 · 3 files mapped                                                 │
│                                                                            │
└────────────────────────────────────────────────────────────────────────────┘
flow                          ↑↓ move · Enter open · +/- depth · h home · q back
Flow map

How it fits together

Entry → routes → data → render. The whole app, as a map you can explore.

appwalk — your setup
┌─ Your setup — settings ────────────────────────────────────────────────────┐

│                                                                            │
│   ▶  package.json — the ID card + instruction sheet for a No               │
│      .env — where your secrets live — keys and URLs                        │
│      .gitignore — the list of files git should never track                 │
│                                                                            │
└────────────────────────────────────────────────────────────────────────────┘
config                   1 settings · 2 clean up · ↑↓ move · Enter open · q back
Your setup

Know your config

What each config file does, how yours is set, and how it could be different. Your `.env` is shown as a location — never its values.

0
Runtime dependencies
0
Tests passing
0
Tools, one CLI
0
It costs — forever
How it works

Understand your app in four moves

No setup, no signup, no AI key. Run one command and start learning.

01

Run it

`npx appwalk-cli` in your project. That's it — no install dance, no signup.

02

It reads your project

Locally. Nothing leaves your machine. No upload, no account, no AI key required.

03

It walks you through

Tour, tree, audit, flow, glossary — every word is one keystroke from a plain-English definition.

04

You get your code

You finally understand how it starts, what's risky, and how to tell an AI what you want.

Pricing

Free forever. Buy the build.

The CLI is free for everyone. Support the build if appwalk helps you understand your code.

Free

The full CLI. Everything on this page.

$0 forever
open source · no AI key needed
  • All 7 tools
  • Runs locally — nothing leaves your machine
  • Deterministic core, zero dependencies
  • The free web tier includes a number of project trials per account
Run `npx appwalk-cli`
One-time

Supporter

Buy the build. Keep appwalk free for everyone.

$25 CAD
one-time · a real thank-you
  • Everything in Free
  • One-time, no subscription — funds the free tool
  • Priority voice on what gets built
  • A genuinely warm feeling
Support the build

Web Pro

The evolution — coming soon.

Pro
unlimited · the growing edge
  • Unlimited project scans
  • AI explanations, no keys to set up
  • Saved reports
  • Every new feature we ship from here
Coming soon

Your app wrote itself.
Now understand it.

Run it in your project. In about a minute you'll know what your code actually does — and the words to say what you want next.

npx appwalk-cli

Free forever · open source (AGPL) · nothing leaves your machine