Skip to content

kaba:// URLs

Built-in apps live under the kaba:// scheme. Any of these can be typed in the omnibar, set as the Mod+Enter target under Settings → Keyboard, saved in a frame, or passed to kaba on the command line.

URLOpens
kaba://desktop/Desktop
kaba://terminal/Terminal on this machine
kaba://terminal/?peer=<node-id>Terminal on a peer
kaba://terminal/?container=<image>Terminal inside a sandbox image
kaba://files/File explorer
kaba://files/?reveal=<path>File explorer at a path
kaba://hippocampus/Hippocampus
kaba://hippocampus/memories?q=<query>Memory search
kaba://hippocampus/frames?q=<name>Saved frames, filtered
kaba://hippocampus/discoveryDiscovery
kaba://kaba/downloadsDownloads
kaba://kaba-projects/Projects
kaba://toolbench/Toolbench
kaba://search/Kaba Search
kaba://editor/Source editor
URLPage
kaba://settings/Settings
kaba://settings/?view=look-feelLook & Feel
kaba://settings/?view=keyboardKeyboard
kaba://settings/?view=devicesDevices
kaba://settings/?view=policiesPolicies
kaba://settings/?view=adaptersModels & Adapters
kaba://settings/?view=containersContainers
kaba://settings/?view=securitySecurity & Privacy
kaba://settings/?view=sitesSites
kaba://settings/?view=passwordsPasswords
kaba://settings/?view=general-logsSystem Logs
kaba://settings/?view=infoInformation
URLPurpose
kaba://loopbench/Benchmark scenarios for the tool loop
kaba://testbed/Test scenarios

Other kaba:// hosts serve the shell’s own surfaces (the omnibar, menus, dialogs and so on) and shared assets. They are not meant to be opened directly.

Chromium’s diagnostic pages are available, for example chrome://gpu to check graphics acceleration.

kaba:// pages are the only pages that receive the SDK. They are served from inside the application and cannot be reached or impersonated by a website. See SDK security.