Install and first run
Not released yet.
@lucitra/lucitrais not on npm and its source is not public, so the install commands below do not work today. They describe the interface as it will ship.
What you need
| Node | 24 or later. The package declares the floor, so an older Node fails before anything runs |
| A runtime | at least one of claude, goose or codex on your PATH, signed in the way you already use it |
| git | tasks run in git worktrees and end in a branch; gh signed in if you want pull requests opened |
There is no database to install, no account, no server and no config file. The store is an
embedded Postgres (PGlite) under ~/.lucitra.
Install
npx @lucitra/lucitra # once it is published
Until the first release, from a clone:
pnpm install && pnpm build
cd packages/cli && npm link && cd ../..
lucitra --help
First run
Run lucitra inside a repository. The first run creates ~/.lucitra, migrates the store and seeds a
default team in a few seconds.
cd your-project
lucitra # the shell
lucitra <command> [args] # one command, then exit
lucitra --help # every command
A daemon keeps running after you close the shell. It holds the store and every running task, so
quitting the shell never stops work. It keeps the environment it was started with: after exporting a
new variable, run lucitra stop and the next command starts a fresh one.
Set LUCITRA_HOME to keep the store, the worktrees and everything else somewhere other than
~/.lucitra, useful for trying things without touching your real install.
The app
lucitra bridge # read-only
lucitra bridge --allow-writes # the buttons work too
It prints a 127.0.0.1 address with a token in it. The page is served from this machine, needs no
network, and the token is good only for that run of the bridge. Without --allow-writes every
button that would change something is off and says why.