New Error monitoring and feature flags, built in

The issue tracker your AI agents can actually use

Kanban boards for people, a first-class CLI for agents, plus error monitoring and feature flags. One hosted app for your team and its agents.

Request early access

See the CLI

itracker / Board

Todo 17

ITR-270 high

Fix defects found in the repo-integration audit

ITR-229 medium

Cut itracker's own error reporting over to itself

In Progress 1

ITR-271 high

Remove the 'server' flag key kind

Review 1

ITR-241 high

Restrict ingest CORS origins

Done 70

ITR-257 critical

UI redesign: uniform, responsive design system

ITR-267 high

Generate DSN keys as hex for Sentry JS SDKs

agent — zsh

$ itracker-cli issue list --actionable

ID TITLE STATUS PRIORITY TYPE ASSIGNEE PLAN

ITR-229 Cut itracker's own error reporting over to itself open medium task yes

ITR-271 Remove the 'server' flag key kind open high bug yes

$ itracker-cli issue move ITR-271 --status in_progress

Moved issue ITR-271 to in_progress.

Speaks the protocols your stack already uses

Sentry-compatible SDKs
OpenFeature · OFREP
Unleash frontend SDKs
Any coding agent with a shell

One app, three jobs

Track the work, catch the errors, ship behind flags.

Stop stitching together a tracker, an error monitor and a flag service. itracker keeps all three in one project.

Issues

A Kanban board with drag and drop, epics with subtasks, and bulk edit. Blocks, relates-to and closes links, with blocking enforced on status changes.

Errors

Point a Sentry-compatible SDK at a DSN to collect grouped error events. Filter by component, then mark a group done or silence it.

Feature flags

Flags with variants, segments and ordered targeting rules, evaluated per environment. Use OpenFeature (OFREP) and Unleash frontend SDKs.

Built for agents

Your coding agent gets a teammate's view of the backlog.

The CLI is a first-class client, not an afterthought. Agents pick up actionable work, attach a plan pinned to a commit, and move issues through review. All of it uses issue keys like ITR-241.

Actionable queue. Agents list unblocked, non-closed work other than epics and update it by key.
Plans pinned to commits. Tasks and bugs require an implementation plan, with an optional SHA recording the commit it was written against.
Per-user, expiring tokens. Per-user CLI tokens are hashed at rest, expire, and are revoked on password reset and user deletion.
One-command setup. integrate writes DSNs and flag keys into gitignored env files, never tracked ones.

$ itracker-cli issue list --actionable
ID       TITLE                         STATUS       PRIORITY  TYPE  ASSIGNEE  PLAN
ITR-241  Restrict ingest CORS origins  in_progress  high      task            yes
$ itracker-cli issue update ITR-241 \
    --plan "Exact-origin match, reject wildcards" \
    --planned-at-sha ccf7d785
Updated issue ITR-241.
$ itracker-cli issue move ITR-241 --status review
Moved issue ITR-241 to review.

$ itracker-cli integrate --env development,staging --env-file .env.local
Component:    1 web (pwa) .
Environment:  1 development (Development) [created]
Environment:  2 staging (Staging) [created]
DSN key:      1 web prefix=dsn_2b0d [created]
Flag key:     1 web-development prefix=fck_LQKF environment=development [created]
Flag key:     2 web-staging prefix=fck_ExQ4 environment=staging [created]
File:         .env.local (env)

$ itracker-cli flag create --key new-board-layout \
    --type boolean --default-variant on --off-variant off \
    --variant 'on=true' --variant 'off=false'
Created flag new-board-layout (id: 12).

Real-time board updates

Board changes sync to connected teammates in the app, with no refresh.

Works offline

Install the PWA. Edits queue locally while offline and sync when you reconnect.

Recoverable by default

Recoverable soft deletes across resources. Restore issues and projects from Trash.

Attachments and comments

Images and files on issues, with the discussion right beside them.

Security

Safe to hand to an agent.

Agents use per-user, expiring tokens, accounts are isolated, and integrate writes secrets only to ignored, untracked files.

Tokens SHA-256 hashed at rest
bcrypt passwords
Rotating refresh tokens, HttpOnly cookie
Account isolation for authenticated project resources
Exact-origin CORS per project
integrate writes secrets only to gitignored, untracked files

Early access

Give your agents a backlog they can work through.

Request early access to bring your team and its agents into one project.