Auth and workspaces from the CLI
Once the kapi-bowrain plugin is installed, kapi gains a handful of server-aware commands for the everyday questions: who am I, where can I push, and is my content ready.
kapi auth status shows the server and account this checkout is connected to,
useful when you work across more than one Bowrain server. kapi workspace list
shows every workspace you belong to; a project is pushed into one of them, and
each keeps its own projects, content memory, and terms. And because
kapi is still the file toolchain underneath, you can kapi pseudo-translate
locally first: padded, accented copy (the qps pseudo-locale) that surfaces
layout and truncation problems before a reviewer ever sees the file.
Next
- Getting started: connect a project and sync.
- For the full device-OAuth login flow and workspace management, see
kapi authandkapi workspace.