CLI projects and context

Projects are the container for stories and bugs. You create and list projects via the CLI (or MCP); the web app does not manage projects.

Listing projects

flik get projects

Returns all projects the authenticated user can access. With org context (FLIK_ORG or --org), only projects in that org are returned. The response includes count (number of projects) and projects (array).

Listing users

flik get users

Returns org members (name and user_id) for the key's organization. Requires FLIK_ORG (or --org). Use the returned user_id values with --assigned-to when creating or updating stories and bugs. The response includes count and users (array of { "user_id": "...", "name": "..." }).

Creating a project

flik add project "My Product Name"
  • The name must be at least 6 characters.
  • The acronym is derived from the first 4 letters of the name (e.g. “My Product” → mypr). It must be unique per org; the API returns an error if the acronym is already in use.
  • Org context is required. Set FLIK_ORG to the org slug, or the API will respond with an error and may list valid orgs.

Deleting a project

flik delete project mypr

Deletes the project and all its records. The CLI typically prompts you to type the acronym to confirm. This action cannot be undone.

Context (active project)

Many commands operate on a project (e.g. stories, bugs). You can:

  • Pass --project <acronym> on each command, or
  • Set the active project so you don’t have to repeat it.

Set context (e.g. for current shell or persisted in config):

flik context project mypr

Or set FLIK_PROJECT in your environment or .flik file. Commands like flik get stories then use that project when --project is not given.