Skip to main content
KiwiFS supports four authentication modes. Choose the one that fits your deployment.

Auth modes

No authentication. Suitable for local development and trusted networks.
.kiwi/config.toml
Auth configuration is hot-reloadable — send SIGHUP to the server process to reload from disk without restarting.

Per-space token fields

When using perspace auth, each [[auth.api_keys]] entry supports:

Scopes

Managing tokens via CLI

The kiwifs token command creates and manages API keys stored in .kiwi/config.toml.

Create a token

The plaintext key is displayed once. Copy it immediately — it cannot be retrieved later.

List tokens

Revoke a token

Revocation removes the key from .kiwi/config.toml. Active requests with the revoked key are rejected on the next config reload.
Revoking a token does not require a server restart — KiwiFS watches the config file for changes.

Path-scoped access

Use the prefix field to restrict a token to a specific directory tree:
This token can only read and write files under onboarding/. Requests to other paths return 401.

Cloud authentication

KiwiFS Cloud uses a separate authentication system:
  1. API key — pass kiwi_sk_* as a Bearer token
  2. MCP OAuth 2.1 — browser-based login via WorkOS (PKCE)
Cloud credentials are stored at ~/.kiwifs/credentials.json. See KiwiFS Cloud for details.

Configuration

Full auth config reference.

API overview

Auth headers and error codes.

Multi-space

Per-space routing and access control.

CLI commands

Token create, list, and revoke commands.
Last modified on May 31, 2026