Plans and issues live on your server instead of in the context window, so work outlives the session. Agents use it over MCP; you use the web UI.
31 MCP tools in 5,781 tokens, about one long file read.
One 25 to 32 MB binary with SQLite, the web UI and backups built in. No Docker, no Postgres.
lific connect writes MCP config for 11 AI clients.
, never UUIDs.
Local-first, lightweight issue tracker. Single binary, SQLite-backed, MCP-native.
Apache-2.0
ตรวจสอบล่าสุด
2026-11-14
ดาว
89
เครื่องมือ
—
อัปไทม์
—
Identifiers like APP-42
60-second setup
cargo install lific # or download a binary from Releases
lific init # config, database, admin account, background service on :3456
lific connect # MCP config for your AI clients
Restart your AI client. The web UI is at http://localhost:3456. lific doctor checks config, database, server and an MCP round trip, and exits nonzero if anything is broken.
lific init --here keeps config and database in the current directory.
lific init --no-service skips the background service; run lific start yourself.
lific service status | restart | stop | uninstall manages the service.
Each AI tool connects as its own bot under your account. The history says "OpenCode closed APP-42", and you can revoke one tool without touching the others.
lific connect # pick from the clients it finds
lific connect --client opencode --client cursor --yes # no prompts
lific connect --client claude-code --scope project # repo-local .mcp.json
lific connect --client zed --stdio # no server: direct SQLite over stdio
It merges into existing config, and leaves a file it can't parse alone and prints the snippet instead. OAuth sign-in from the client and lific login for headless machines also work: Connect agents.
Create a key with lific key create --name my-key --user <you>. A stdio session without LIFIC_TOKEN acts as the instance operator.
CLI
lific issue list --project APP
lific issue create --project APP --title "Fix login bug" --priority high
lific issue update APP-42 --status done
lific search "authentication" --project APP
lific --backend http --url https://lific.example.com issue list --project APP # after lific login
The CLI reads the database directly, or a remote server with --backend http. Output is JSON when piped. lific agents-md adds a short Lific section to a repo's AGENTS.md. Full reference: CLI.
When Lific is the wrong tool
You coordinate a large team and need SSO, sprints or Gantt charts. Use Linear or Plane.
You want issues stored in the repo itself. Use a git-native tracker such as beads.
You need several servers syncing with each other. One Lific instance is one SQLite file.
It's built for one person directing several agents.
Running it
Access. New installs check project membership on every call, reads included. Add people with lific member add --project APP --user sam --role maintainer. See Self-hosting.
Backups. Lific writes an archive every hour and keeps 24. For a one-off:
lific dump # database plus attachments, safe while running
lific restore lific_20260703_141500.tar.gz # stop the server first
Config.lific init writes lific.toml. Set server.public_url before exposing the server beyond localhost. See Configuration.