Dashboard manual

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. One rule holds everywhere: switching dashboards changes only the view. Opening a dashboard never connects a VPN, turns Tor on or changes your route by itself.

6322 walkthrough steps3276 distinct controls219 screensAuto-play or clickReal interface, nothing runs

Startup screens

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

294 steps179 distinct9 screens4 chapters

AutoShield

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

191 steps186 distinct1 screen10 chapters

Circle

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

44 steps43 distinct1 screen1 chapter

Lite Classic and its islands

The main workspace: 19 pages and their sub-tabs, covering routing, Tor, DNS, hardening, monitoring, AI, workflows and settings.

4469 steps2260 distinct139 screens12 chapters

ColonyOps

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

102 steps97 distinct22 screens10 chapters

SOC monitor

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

32 steps30 distinct1 screen1 chapter

Vitals

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

229 steps222 distinct2 screens6 chapters

Settings

Four groups: dashboard preferences across seven tabs, dashboard protection, encrypted backup and Tor bridges.

256 steps153 distinct10 screens4 chapters

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.

280 steps207 distinct15 screens4 chapters
reference 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.

96 rowsreference, not a walkthrough

Shared controls

The chrome every dashboard carries: top bar, command search, output, queue, notifications, help, About and updates.

425 steps353 distinct19 screens4 chapters

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.