The Kodachi dashboard, control by control
Five dashboards and a boot tool, one manual. Each page plays through the real interface and explains every control a user touches, or you click the control you are looking at and read about that one. Where two controls look alike and are not, a Know this card opens under the explanation and compares them: WireGuard against Hysteria2, plain WireGuard against its obfuscated variants, round-robin against weighted, the three panic tiers, what each hardening level breaks. Nothing here runs: these are renders of the dashboard plus its own help text. New to Kodachi? Read in this order. Startup first, because every session begins there. Then Circle, the dashboard a fresh install opens, then Lite Classic for the complete workspace and Shared controls for the top bar, the output drawer and the notifications that sit on every dashboard. SOC and Vitals only watch the machine, ColonyOps is for building multi-step workflows, AutoShield runs before any dashboard opens, and the tray menu reaches the same controls from the panel icon. Two rules hold everywhere. Switching between dashboards changes only the view. And no dashboard connects a VPN or sends your traffic through Tor by itself. Out of the box, the only actions that run without a click are the startup privacy actions, while the launcher is still on screen and only with automatic sign-in on (the default). By default they give the computer a random hostname and switch DNS to DNSCrypt, once after each boot; a random MAC and a random or synced timezone also run once per boot if you switch them on, while Restore MAC, Detorrify and Prepare Tor, if switched on, run every time the dashboard starts. The switches are in Settings under Dashboard, Startup, and also in Advanced setup under Launch Settings when your plan includes Advanced setup (the support page shows live which plans do). Others act on their own only once you set them up: AutoShield, if you arm it, whose steps can include connecting a VPN or sending all traffic through Tor; and the dashboard’s own protection in Settings, Security: auto-lock, the response to failed unlock attempts (which can cut the network or power the machine off) and a scheduled Destroy.

Startup screens
Terms, the Quick Launch picker, the Advanced setup screen and the loading screen: everything before a dashboard opens.

AutoShield
The boot automation system: choose what Kodachi does to protect you automatically every time it starts.

Circle
The simplest dashboard: one ring, seven protection segments, live status in the middle.

Lite Classic and its islands
The main workspace: 16 pages and their sub-tabs, covering routing, Tor, DNS, hardening, monitoring, AI, workflows and settings.

ColonyOps
The workflow operator mode: build, guard, preview and deploy multi-step privacy workflows on a visual map.

SOC monitor
The live security operations monitor: threats, exposure, the watcher and the world map.

Vitals
The live system monitor: CPU, memory, disks, network, processes and the Kodachi service rollup.

Settings
Five groups: dashboard preferences across seven tabs, dashboard protection, encrypted backup, Tor bridges and how the dashboard looks.

Guides and wizards
The four helpers that walk you through something instead of waiting to be operated: the Routing Guide, the Internet Recovery wizard, the guided tour every dashboard carries, and the About page.

The tray menu
The system tray icon carries a second, complete set of controls: connect, torrify, rotate identity, wipe, shut down, all without opening the window.

Shared controls
The chrome every dashboard carries: top bar, side rail with its Security Status card, command search, output, queue, notifications, help, About and updates.
How to read these pages: each one plays through the dashboard chapter by chapter with the control being explained lit up on the real screen, or you click any control, chip or table row to jump straight to it. Nothing on these pages runs: they are renders of the interface plus its own explanatory text, with no dashboard logic included.
Steps against distinct controls: a control that appears on several screens, the refresh timers and the tab strip for example, is explained on each screen it appears on. That is why every page counts more walkthrough steps than distinct controls.
On the version in the screenshots: the renders come from the project’s own test harness, which pins a sample build stamp, so a version legible in a screenshot is the harness’s and not the release you are running. Check your build on the dashboard’s own About page.