Ask Pekan by voice, safer setup repair, and clearer agent sessions
The global voice control is now a single Ask Pekan entry point instead of a set of modes you had to understand before speaking. Pekan infers whether a request should navigate, search, dictate, or propose a board change from the words themselves. You can ask it to open Settings, Help, Activity, Workflows, Agent Actions, a project view, or a task by its display ID, and you can search tasks without first choosing the right mode. Navigation happens immediately when the destination is unambiguous. If a project or task name could mean more than one thing, Pekan presents a short choice instead of guessing. Board changes remain reviewable before they are applied, and the microphone control now uses clear start and stop states rather than requiring a press-and-hold gesture.
Codex telemetry is more complete and project setup is less fragile. MCP lifecycle runs can now be correlated with the Codex provider session that produced them, so exact model and token usage can reach the correct scoped or unscoped run after each completed turn. Cumulative usage reports are checkpointed, which makes retries, duplicate hooks, resumed threads, and out-of-order reports safe without double counting. On startup, Pekan also repairs its own project setup files when the fix is known to be safe, including managed configuration, the MCP proxy, agent instructions, and local capture hooks. Anything ambiguous, destructive, remote-managed, or dependent on fresh provider consent is still left for the manual Repair setup flow.
Agent work is easier to follow while it is happening. MCP lifecycle runs now publish the same temporary working presence shown for other agent activity, and a new Security pass action gives task-level reviews a focused way to look for concrete security problems without changing code. The Agent Panel also stops showing a previous conversation while a newly selected session is still loading. It displays an explicit loading or unavailable state, clears stale transcript content between sessions, and only shows the composer when the selected session can actually accept a message. Together these changes make the board's activity signal, session history, and available controls reflect the work that is really active rather than the last state the interface happened to render.
Highlights
- Ask Pekan now infers voice intent and can open views, projects, tasks, and searches without a mode selector.
- Codex usage reports correlate with the correct MCP lifecycle run and remain safe across retries and resumed sessions.
- Pekan safely repairs its managed project setup files on startup while leaving ambiguous changes for manual review.
- Agent Panel session switches show accurate loading, history, and composer states instead of stale conversation content.
- MCP lifecycle work publishes task presence, and Security pass is now available as a built-in Agent Action.