Docs

Flicker documentation

Flicker keeps a project's repository, tickets and documents searchable, lets you ask questions about them, and runs coding agents against that context. A project is the umbrella: it owns the repositories, tickets and sources, and, where your organization has hosting, its databases and apps. Agents open pull requests; a person approves every merge, and nothing here deploys on its own. One CLI and a REST API drive all of it.

These docs cover the developer surface end to end. New here? Start with Getting started — connect GitHub, add a model key, turn on Ask — and work down.

Getting started

Connect GitHub, add a model key, turn on Ask. Hosting walkthrough after.

Environments & secrets

The secrets model: environments, inheritance, managed vs user secrets, bundles.

Deploys

Push → Building → running, deploy history, and rollback.

Wiring dependencies

Dependency edges, auto-rewire, and one-click templated connection keys.

Volumes

Persistent storage that survives deploys and restarts.

Email

Transactional email: verify a sending domain, send via the API, and watch the message log.

Tickets

AI-native work units: the v1 workflow, versioned documents, local checkout, and searchable memory.

Notifications

The in-app inbox, optional email delivery, and per-type email preferences.

Agents & automation

First-party skills for Claude Code, Pi, and Codex that run the plan → ship workflow on Flicker Tickets.

Agent config

One library of rules, skills, and MCP servers — assigned per project, written into every harness.

Agent context

Public catalog of skills and groups. Pin exact versions into a private profile. Flicker does not host MCP or run those agents.

Software factory

Ticket-driven agent runs on branch environments: phases, gates, rosters, and the trace.

Assistant & RAG

A project-scoped assistant grounded in your own data — buckets, git repos, and tickets — with hybrid retrieval.

Assistant chat API

Put a published support assistant on your site: one public key, a streamed, cited answer, and a daily cap.

Platform health

Cached functional status for Flicker's six platform components.

CLI reference

Every command, flag, and example — mirrored from the CLI's own help.