Accounts

Attention is all you need. And a Kaba account ;)

This page describes accounts in Kaba Personal. Personal is all local.

A Kaba Personal account lives on your device, in the engine’s database. There is no sign-up with Kaba Labs and no account server. The account exists so that your memories and saved logins can be encrypted with a key only you can unlock, and so your devices can recognise each other.

Fleet-managed devices are different

With Kaba Enterprise and fleet management, authentication is centralized. Your organisation issues and controls accounts, enrols devices, pushes policy and updates, and can revoke keys and data remotely. Everything on this page about there being no account server, about nobody else holding a key, and about there being no password reset describes Personal only. See what fleet control changes.

Note

Kaba Personal currently supports one local account per installation.

Avatar

In the top right corner of your Kaba system you can see your Avatar, which can be changed in Settings. Other resources in your Avatar:

• Downloads
• Hippocampus
• File Explorer
• Disable Blocker
• Settings
• Exit Kaba

The full menu, including Terminal, Saves, Discovery and Sites, is described under UI layout.

Password

To update or change your password, go to Settings > Edit Account.

Changing your password keeps all your data: the same encryption key is re-wrapped with the new password.

In Kaba Personal there is no password reset

Your password protects the key that encrypts your memories and saved logins. If you forget it, that data cannot be recovered, because nobody else holds a key. Choose a password you can keep, and store it somewhere safe.

Groups

Life is a single player game, and so is Kaba. But, we are all part of various groups, communities, and organizations. Same with Kaba.

Soon, we’ll introduce Groups to the Kaba experience. In the first instance, think corporate environments or large government organizations that want centralized policy control over employee Kaba systems.

Additionally, in the future, we’re planning all sorts of nice multiplayer functionality.

Today, Settings already shows the Group and Policy that apply to your account. Centralized control over accounts, groups and policy is what Kaba Enterprise’s fleet management provides; see what fleet control changes.

Create your account

On first run Kaba asks for:

Field	Used for
First name, last name	Shown in the Kaba menu and on your devices.
Email address	Identifies the account on this device. It is also the name you pass to kabactl ask --workspace and kabactl train --workspace.
Language	The interface language.
Password	Signs you in and unlocks your encryption key.

[todo: add screenshot of the create-account screen and of parts first name, last name, email address, language, password, Create Account button.]

Sign in

When Kaba starts, the Accounts screen lists your account. Select it and enter your password. Signing in unlocks your memories and saved logins for the session.

If the screen reports that the engine is not answering, choose Restart kabactl. This is safe: your account and data are on disk.

[todo: add screenshot of the Accounts sign-in screen and of parts the account tile, password field, Restart kabactl button.]

Lock

Window → Lock Kaba (Ctrl/Cmd+Shift+L) covers every window until you enter your password. Use it when you step away.

To drop the encryption key from memory without closing anything, use Settings → Passwords → Lock now. Saved logins stay locked until you sign in again.

Edit your account

Settings → Edit Account changes your first and last name and your password. You can also replace your avatar with an image of your choice.

[todo: add screenshot of Settings → Account and of parts avatar, Edit Account, Group, Policy, Logout.]

The account panel also shows the Group and Policy that apply to you. The policy decides which model and tools are used; see machine learning. For groups, see above.

Import from another browser

Settings → Import from another browser brings your existing data over. Kaba detects profiles for Chrome, Chromium, Brave, Edge, Vivaldi, Opera and Firefox.

What	Becomes
Bookmarks	Frames: one saved frame per bookmark folder, up to four pages each.
History	Visits with their original dates (the most recent 5,000).
Passwords	Logins in your vault, from the browser’s own CSV export.

For passwords, export a CSV from the other browser (Chrome: Passwords → ⋮ → Export; Firefox: Logins → ⋯ → Export), then choose Import passwords CSV…. The file is read locally and sent to your vault. Delete the export afterwards.

A new installation also offers this from a card on the desktop.

[todo: add screenshot of Import from another browser and of parts detected browser profiles, bookmarks → frames, history, Import passwords CSV.]

Sign out

Settings → Logout ends the session and returns to the Accounts screen.

Where the account is stored

The account row is in kaba.db in the storage directory. Your password is stored only as an Argon2 hash, next to a salt and your wrapped encryption key. See security.

To use the same account’s data from the command line, pass your email as --workspace. kabactl asks for the password, or reads it from KABA_WORKSPACE_PASSWORD.