Lific

Native MCP · one binary · self-hosted · free & open source

An issue tracker
for prolific agents.

Built for coding agents. Plans and issues live on your server instead of the context window, so work outlives the session.

$ cargo install lific $ lific init

or grab a static binary from the releases page (Linux and macOS, x86_64 and arm64, and Windows x86_64)

For agents

Pick up where the last session stopped.

opencode · ~/dev/app
An agent session on Thursday at 9:01 am: lific_get_briefing for project APP since the last session, then the reply 'Since the last session, APP-42 closed and APP-48 went active. Ship offline sync is 5/7 done. Step 4 is APP-43; APP-44 waits on you. Starting APP-43.'
  • list_issues(workable=true)

    Skips APP-44, which waits on @blake.

  • update_issue(status="done", evidence=...)

    Closes APP-43, ticks plan step #4 and records a verification comment.

  • edit_issue(old_string=..., new_string=...)

    Changes one string in the description without resending the rest.

31 tools in 5,781 tokens of context. lific connect sets them up in 11 AI clients.

For humans

See what needs you. Ignore the rest.

localhost:3456
Lific Home on Thursday morning, greeting Blake. Needs you lists APP-51 Pick the launch date as assigned to him, APP-52 Sign the vendor contract as for any person, and APP-44 Approve retry limits as waiting on him. Below it, five active issues in App.

Your agent asks with a checklist. You tick one from your phone.

APP-51 Pick the launch date on a phone. The agent's checklist offers Oct 20 (after the beta), Oct 27 (gives docs a week) and Nov 3, with Oct 27 ticked. Activity shows Blake changed the description just now, after opencode-blake created the issue and assigned it to him.

For teams

Every change has a name.

APP-42 · Conflict resolution
APP-42 activity, newest first: opencode-blake (agent) commented 'cargo test: 412 passed, 0 failed.', auto-completed a step (issue closed), and changed status from Active to Done, all via mcp; cursor-ada (agent) changed the description via mcp; ada changed priority from Medium to High via web. Below, comment #118 from opencode-blake, marked Verification: cargo test: 412 passed, 0 failed.
APP-PLAN-2 · Ship offline sync
Plan APP-PLAN-2, Ship offline sync, 5 of 7 steps done: schema migration (APP-39), write-ahead op queue (APP-40) and conflict resolution (APP-42) with both its sub-steps are checked off; retry with exponential backoff (APP-43) and feature flag and rollout notes are still open

  • Lead

    Manages members and settings, and decides whether the project is public.

  • Maintainer

    Creates and edits issues, pages and plans, and checks off plan steps.

  • Viewer

    Reads everything in the project and can comment.

Each AI tool connects as its own account under yours, so you can revoke one without touching the others.

For everyone

Feel less like a prompter and more like a director.

opencode · ~/dev/app
An agent session: lific_get_plan, then the reply 'APP-43 is next on the plan. Starting it.', then lific_update_issue setting APP-43 to active
localhost:3456/#/APP/board
The Lific board: APP-43 now in Active, labelled opencode-blake, and APP-51 just dropped in Done by blake's cursor
APP · activity
Activity: opencode-blake changed status of APP-43 from Todo to Active via mcp; blake changed status of APP-51 from Todo to Done via web

Two people's worth of work. One of them is an agent.

Issue trackers should be simple, right?

Star on GitHub$ cargo install lific