Current release boundaries

Compatibility notes

This page describes what the current published build supports and where its evidence falls back.

Runtime

The Dashboard requires the Microsoft Edge WebView2 Runtime, already installed on most Windows systems. Dashboard HTML, artwork, and default settings are embedded in the EXE and extracted locally when needed. Updates require manually replacing the EXE. Archived standalone executables retain their .NET 9 requirement.

AI coding tools

ToolIntegrationWhat Discord can show
Codex CLI & DesktopBuilt in: process and window signals, local session JSONLReasoning summaries, MCP, files, model, effort, tokens, party
Claude CodeOpt-in: observational hooks and a statusLine wrapper in ~/.claude/settings.jsonModel, effort, MCP, files, spinner labels, Claude Design, party, cumulative tokens, observed usage and reset countdown
Antigravity CLIOpt-in: official statusLine payloadModel and effort, plan and quota usage, tool activity, reported subagents

Claude Code and Antigravity CLI are enabled from the Dashboard. Selection considers current activity, freshness, and project evidence through a shared switching gate; fresh activity from another project can participate. Claude Code settings changes keep a local backup, preserve terminal output, and restore the original statusLine while removing only owned hooks when disabled.

Claude and Codex use the same five-second waiting cycle for Token and Usage. Claude tokens come from main-session transcript usage; five-hour usage, reset time, and estimated session cost require matching statusLine evidence. Missing values remain unknown, and cost is not an actual subscription charge.

Codex profiles

ProfileDetection sourcePurpose
DesktopCodex process and window signals, local session JSONL, Codex configurationDefault desktop launch flow
CLICLI command-line signatures, local session JSONL, Codex configurationSeparate CLI launch flow via start-cli.cmd

Evidence behavior

Current structured Codex session events and direct tool targets take precedence. Current reasoning, MCP, file, command, waiting, and completed states are resolved from that evidence when available. If direct evidence is unavailable, recent edited-file and timestamp evidence can be used as a fallback. The fallback is not a claim that the app observed a current tool action.

Not currently promised

Download the latest release →