CLI

The Flik CLI lets you manage projects, stories, and bugs from the terminal. It uses the same API as the MCP server; you authenticate once with an API key from the web app.

Install and authenticate

  1. Build or install the CLI (see repo README).
  2. Get an API key from the Flik web app (Keys page).
  3. Run flik auth login [api-key] — or set FLIK_KEY and run flik auth login. The command validates the key and prints JSON (ok, user_id, key_id, name).

Use FLIK_API_URL to point to a different API (e.g. http://localhost:8080). Config can live in a .flik file (env-style); search order: current directory, parent directories, $HOME/.flik. Environment variables override file values.

What you can do

Area Commands
Projects flik get projects, flik add project <name>, flik delete project <acronym>
Users flik get users — list org members (name and user_id). Requires FLIK_ORG.
Context flik context — set active project (e.g. FLIK_PROJECT=mypr). Required for story/bug commands when not passing --project.
Stories flik get stories, flik add story <title>, flik update story <id>, flik delete story <id>
Bugs flik get bugs, flik add bug <title>, flik update bug <id>, flik delete bug <id>
Unified object flik get object <id>, flik update object <id>, flik delete object <id> (story or bug by id, e.g. mypr-1)
Audit flik get logs — API transaction log (default: today; use --all for full history)
Version flik version, flik version open (release notes), flik upgrade

List responses (projects, users, logs, stories, bugs) include a count field with the number of items returned, plus the array (projects, users, logs, items).

Org context

For project list, project create, and user list (flik get users), org context is sent via FLIK_ORG (or --org if supported). Project create and get users require org context; if missing, the API returns an error and may list valid org slugs.

Next steps