hey @mkesper, the VS Code extension and sqz stats are separate systems — the extension alone won't populate the stats.

here's how the pieces connect:

sqz stats reads from ~/.sqz/sessions.db, which gets populated by the sqz CLI hooks and MCP server.
the VS Code extension is a local compression preview — it shows savings when you open files, but doesn't feed into the stats database.
to get real compressions flowing into sqz stats, you need an AI agent that runs through the sqz hooks: Claude Code, Cursor, Windsurf, Cline, Gemini CLI, or OpenCode.

if you're using Claude Code, run:

sqz init --global

that installs the PreToolUse hook + MCP server. after that, any Bash commands the agent runs will be compressed and logged to sqz stats.

VS Code's built-in Copilot/intern chat doesn't have a hook integration yet (Copilot doesn't expose a PreToolUse-style API). the VS Code extension is more of a status bar widget that shows cumulative savings from other agents running on the same machine.

if you're primarily using Codex, make sure you also ran sqz init — it installs both the AGENTS.md guidance and the ~/.codex/config.toml MCP entry that Codex needs to see sqz.

lmk what agent you're using and i can point you at the exact setup steps.

Stats stay on zero #18

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions