Skip to main content
Use this page to build a visual mental model before debugging commands.
Khal OS desktop shell

​
What to notice

  • Shell/chrome — the browser-based OS surface, not a raw website.
  • Packs/apps — installable KHAL units with khal-app.json and runtime proof.
  • Terminal pack — where local commands and dry-runs are visible.
  • Settings/source panels — where identity, auth, and app metadata become visible.
Khal OS dark shell

​
Visual proof rule

A screenshot proves only what is visible. Pair it with command/API proof when claiming an install, auth, release, or target state. 
TASK: I am reading `visuals/desktop-tour.mdx` (Desktop tour). Use this page as the contract, then verify current CLI/output before you guide me.
CONTEXT: I may be a new KHAL FDE. Prefer read-only checks and dry-runs first. Do not mutate customer, HML, production, credentials, SSH, Gitea, or model-provider state without an explicit GO.
SAFE FIRST COMMANDS: Check versions, identity, target, git source/ref, KHAW doctor/status, KHAL context, and dry-run output. Redact secrets and private URLs.
EVIDENCE: Return command, exit status, sanitized output, what it proves, and the next safe action.