Skip to content
codika-os

What is codika-os?

Overview

Section titled “Overview”

codika-os is Codika’s internal cockpit. It tracks per-project time, agent runtime, and token cost across every Claude Code session the team runs, so we can see whether AI leverage on client and internal work is increasing over time.

The single number every screen exists to answer:

leverage = agent_seconds / human_seconds

Per project (or rolled up by category). Per period. Rising = the agent is doing more for each hour of your attention.

How you use it

Section titled “How you use it”

The primary way to drive codika-os is the codika-os-plugin — a set of ten Open Plugin v1 skills that wrap the codika-os CLI. In Claude Code:

/plugin marketplace add codika-io/codika-os-plugin
/plugin install codika-os@codika-os-plugin
/codika-os:setup-codika-os

That last skill installs the CLI globally, runs OTP signup or login, and registers the five Claude Code hooks. The SessionStart hook triggers a background sync whenever last-sync is older than 20h. Once set up, anything you do in Claude Code is captured, classified, and shown on the dashboard.

See the quickstart for the full four-step flow, or plugin skills for the complete skill catalogue.

What happens behind the scenes

Section titled “What happens behind the scenes”
[Claude Code session]
   │  5 hooks  (SessionStart, UserPromptSubmit, Stop, SessionEnd, PostToolUse)
   ▼
~/.codika-os/events.db  (local SQLite, WAL)
   │  codika-os sync   (via SessionStart hook, or on-demand)
   ▼
POST /api/sync  →  Neon Postgres
   │
   ▼
SvelteKit dashboard at /tracking
  1. Hooks fire on every Claude Code lifecycle event and append one row of metadata to local SQLite. Under 50 ms, no network.
  2. codika-os sync parses the local DB plus ~/.claude/projects/*.jsonl transcripts, classifies each session into a project via longest-prefix path matching against project_path_prefixes (sessions that don’t match are left for on-demand classification by the operator’s agent via /codika-os:classify-sessions), computes human seconds, agent seconds, and token cost, and uploads to the dashboard.
  3. The dashboard at /tracking shows the leverage trend, category-level rollups, per-project breakdowns, and session-level drill-downs.

The four sub-repos

Section titled “The four sub-repos”

codika-os is delivered as four sibling repos that ship as one system. If you change something in one, mirror the change in the others.

RepoWhat it is
codika-os-appSvelteKit dashboard + /api/sync ingestion + /api/tracking/* aggregators
codika-os-cliThe codika-os CLI. Hooks, classifier, aggregator, sync
codika-os-pluginOpen Plugin v1 — ten skills wrapping the CLI
codika-os-docsThis site (Astro Starlight)

Who it’s for

Section titled “Who it’s for”

codika-os is internal to Codika. The CLI auth endpoints reject non-@codika.io emails with 403. There’s no public hosted dashboard; each team member runs their own setup against the shared Neon database.

Next steps

Section titled “Next steps”