StillPointHomebase keeps StillPoint local first.
StillPoint vaults live on your filesystem. When you want sync across devices, Homebase is the remote option: local copies first, synchronized through a server without turning the server into the source of truth.
One vault model on disk, with Homebase for sync.
Local vaults
Your vault is a normal local folder full of Markdown pages and attachments. That keeps the model simple and makes the files usable from StillPoint, editors, scripts, and the terminal.
Homebase Vaults
Homebase adds sync on top of that same local vault model. Each device keeps a full local copy and synchronizes through the Homebase server.
Zero-trust direction
The server stores encrypted blobs and sync metadata while your local device remains the place where plaintext work happens.
Why Homebase fits StillPoint
Homebase preserves the filesystem-first workflow instead of replacing it. You keep a real local vault, work offline when needed, and sync later.
Offline first
Work locally and let sync catch up when the network is available.
Multi-device continuity
Use the same vault on your laptop, desktop, or travel machine.
Conflict aware
StillPoint can surface sync conflicts instead of silently overwriting work.
Use terminals, TUIs, and agents directly against the vault.
Because the vault stays local, StillPoint's optional multi-terminal manager can run shells, full-screen TUIs, scripts, and CLI agents at the actual vault root. Open more than one session, keep tools running, and use the terminal docked or detached.
StillPoint can seed AGENTS.md so compatible tools understand page folders,
colon links, and editing rules. Token-free client configuration can connect agents to
a session-scoped MCP bridge without writing credentials into the vault.
Open the vault in a terminal
Run local tools against the actual vault root, not a cache or export copy.
Work through StillPoint MCP
Give agents structured search, page context, links, tasks, journals, safe patches, recent changes, and dry-run page moves.
Let Homebase sync it
After local work lands, Homebase can synchronize those files to your other devices.
Start local, then add Homebase when you need sync.
1. Create or open a local vault
StillPoint works directly against a normal folder on disk.
2. Work locally first
Use StillPoint, your editor, or the terminal to build out the vault.
3. Enable Homebase
Authenticate, pair the vault, and let sync handle multi-device continuity.
Passphrase trust choice
StillPoint does not store your Homebase encryption passphrase by default. You can opt into storing it on a trusted device, but passwords are still not stored.
After first login, StillPoint can reuse Homebase access and refresh tokens. It also writes non-secret recovery metadata into the vault under .stillpoint/homebase.json so the server URL, SSL mode, vault ID, and vault name can be rediscovered later.