> CODEX CLI TIME TRACKING

    Track Your Time in Codex CLI

    AI coding agents are rewriting how developers work. But no time tracker was built for the agentic era. DevClocked tracks Codex CLI sessions automatically — so your AI-assisted hours are accounted for.

    Codex preview

    Agent sessions belong on the timesheet.

    Codex work is rendered as a tracked block with token and cost context, so AI-assisted implementation stops being invisible billing and planning overhead.

    Terminal

    $ codex ask devclocked session

    2h 34msession time
    92%focus
    14ticks
    VS Code0:00 - 0:52
    Chrome research0:52 - 1:14
    Terminal + agent1:52 - 2:22

    > alpha-service / feat/auth-v2 / local signals only

    > merged IDE, browser, terminal, and agent activity

    Agent Work Block
    Tokens84k
    Cost$4.82
    Hands-on18m

    Agentic Coding Is a Blind Spot for Every Other Tracker

    Codex CLI runs in your terminal, autonomously editing files, running tests, and iterating on code. Traditional time trackers have no concept of AI agents as a work source. The result? Hours of productive work that never appears on your timesheet — and revenue you never bill for.

    $codex "Add rate limiting to the API endpoints"

    Analyzing current API structure...

    Creating middleware/rate_limiter.go...

    Adding Redis connection for distributed limits...

    Updating all route handlers with rate limit middleware...

    Running test suite... 24/24 passed

    DEVCLOCKED_TRACKING

    Session: api-service | Source: daemon

    Duration: 1h 15m | Ticks: 28 | Branch: feat/rate-limiting

    Files changed: 6 | Lines: +218/-12

    How It Works

    01

    Install DevClocked

    Download the Mac app or install the daemon. One command, zero configuration. It runs silently in the background.

    02

    Run Codex normally

    Use Codex CLI to generate, refactor, or debug code. DevClocked detects the process and file changes automatically.

    03

    Sessions appear

    Every Codex session shows up in your dashboard — duration, files modified, repository, and branch. Ready for timesheets and invoicing.

    Why Track Codex Sessions?

    Bill for AI-assisted work

    Codex does the heavy lifting, but you're still driving the architecture, reviewing the output, and iterating. That time is billable — and now it's tracked.

    Measure AI productivity gains

    Compare time spent on similar tasks with and without Codex. Quantify the productivity multiplier AI agents give your workflow.

    Track across all AI tools

    Using Codex, Claude Code, and Copilot? DevClocked tracks them all. See your total AI-assisted time across every tool in one dashboard.

    Privacy-first by design

    DevClocked never reads your prompts or Codex output. Only metadata — duration, files, repo, branch. Your code and conversations stay private.

    Frequently Asked Questions

    Everything you need to know about DevClocked

    The DevClocked daemon monitors for the Codex CLI process and file system changes it generates. When Codex modifies files in your project directories, DevClocked automatically tracks the session.

    Yes. DevClocked tracks any terminal-based coding tool that modifies files — including OpenAI's Codex CLI. The daemon watches for process activity and file changes, not specific tool integrations.

    Yes. DevClocked tracks the source of each session. You can filter your dashboard to see Codex-specific sessions, compare AI-assisted time vs manual coding time, and track token usage per project.

    Never. DevClocked only tracks metadata — session duration, file names, repository, branch, and lines changed. Your prompts, code, and AI responses are never captured or transmitted.

    Start Tracking Codex Sessions Today

    Install once. Every AI coding session, captured automatically. Free tier — no credit card required.

    Start Tracking Free