FAQ

Agilerr runs as a single application. The Go backend, embedded PocketBase auth and storage, and the product frontend are served together from one binary in release builds.

No. PocketBase is embedded. For normal local or small-team usage, you only need the Agilerr binary or the Docker image plus a persistent volume for PB_DATA_DIR.

The most important are ADMIN_EMAIL, ADMIN_PASSWORD, PB_DATA_DIR, HTTP_ADDR, and AGILERR_API_KEY. If you want AI Add, also set OPENAI_API_KEY and optionally OPENAI_BASE_URL plus OPENAI_MODEL.

Agilerr can generate a random local port and a random API key at startup. That is useful for local one-click runs, but for stable installs you should set both explicitly.

AI Add runs a compact planning conversation attached to a project or parent item. It asks one question at a time, proposes items for review, and lets you accept, reject, or edit each proposal before anything is created.

Yes. The app still supports projects, backlog, kanban, bugs, permissions, API access, and MCP without any OpenAI configuration. AI Add simply stays unavailable.

Start on the project dashboard. From there the user can move into kanban, backlog, bugs, docs, and assigned work using the sidebar and project routes.

Backlog views support item-type filtering and tag filtering. Descriptions stay collapsed by default so larger hierarchies remain readable.

Bugs are separate from the epic-feature-story-task hierarchy. They live on the dedicated bugs page and start in triage.

Permissions are scoped per project, with system admins able to manage users, project membership, passwords, API docs, and MCP docs. UI actions are hidden when the current user does not have permission.

The binary now stores its current schema version and last binary version in the database metadata. Future releases can ship ordered migrations and apply them when the database version is older than the binary.