Qwen Code sessions and token history, live

Download for macOSFree 3-day trial · Apple silicon
AgentPeek monitoring Qwen Code sessions and token history on a Mac
Sessions
Hooks, 18 events
Permissions
Approve, deny, always allow
Direct Chat
qwen --acp
Usage
Monthly tokens, daily history
Installs
~/.qwen/settings.json

Live sessions with the full transcript

Run qwen in any terminal and the session appears in the notch with its project, live state, current activity, tool calls, files, commands, and diffs. Expand it for the transcript Qwen records locally, with subagents grouped under their parent instead of flattened into separate runs.

Permission requests answered where you are

Qwen Code PermissionRequest prompts surface in the notch: approve with ⌘ A, deny with ⌘ N, or open the waiting terminal with ⌥ T. Always Allow appears only when Qwen includes a concrete allow suggestion. Qwen's ask_user_question interaction stays owned by its native terminal; AgentPeek shows the session waiting for input and Open Terminal takes you there instead of pretending it can answer through the permission channel.

Direct Chat through Qwen ACP

The session composer sends follow-up prompts into resumable Qwen sessions through qwen --acp. AgentPeek uses Qwen ACP session loading, prompt streaming, and cancellation, so replies and tool activity update in the session card and a prompt in flight can be stopped. ACP PermissionRequest approvals stay native in the notch; ask_user_question remains owned by Qwen's terminal.

Monthly tokens and daily history, never a guessed quota

AgentPeek reads the token counts in Qwen's local JSONL session records and shows the monthly total plus daily history in the usage panel. Qwen does not report a local rate-limit quota through those records, so AgentPeek shows the counts it can prove and no fabricated percentage or reset window.

Setup that follows Qwen home and runtime overrides

AgentPeek manages hooks in ~/.qwen/settings.json, or the equivalent under $QWEN_HOME, and Doctor checks and repairs the entries. Historical usage scans follow $QWEN_RUNTIME_DIR or Qwen's default runtime root. Live session lookup follows the exact transcript path Qwen reports, wherever Qwen wrote it, and otherwise scans the projects tree under that runtime root. Quick Routes opens the active Qwen skills, config, project logs, and root folder directly.

Questions

Yes. Qwen Code sessions appear in the Mac notch with live state, tool activity, transcripts, files, diffs, and subagents grouped under their parent.
Yes. Qwen PermissionRequest prompts support approve, deny, and Open Terminal from the notch. Always Allow appears only when Qwen supplies an allow suggestion. Qwen's ask_user_question interaction remains in its native terminal, where the session shows as waiting for input with Open Terminal available.
It reads token counts from Qwen's local JSONL session records and shows monthly totals with daily history. Qwen does not report a local rate-limit quota through those records, so AgentPeek does not invent a percentage or reset window.
Yes. The notch composer uses qwen --acp to load a resumable Qwen session, send the next prompt, stream the reply, and cancel a prompt in flight. ACP PermissionRequest approvals work in the notch; ask_user_question stays in Qwen's terminal.
In ~/.qwen/settings.json by default, or under $QWEN_HOME when Qwen home is overridden. Historical usage scans follow $QWEN_RUNTIME_DIR or the default runtime root. Live lookup follows Qwen's reported transcript path, wherever Qwen wrote it, and otherwise scans the projects tree under that runtime root.

Qwen Code is a product of its respective owner. AgentPeek is independent and not affiliated with or endorsed by them.

Keep reading

Keep your agents in view

Download for macOSFree 3-day trial · Apple silicon