Weekly Update #29

TL;DR

In this update, Pochi gets context-aware in two directions: tasks now maintain persistent memory that survives compaction, and custom agents that can precisely scope which files and domains they're allowed to touch.

More below!

🚀 Features

• Task Memory: Pochi now maintains a persistent memory file throughout a task — including across context compaction.

  A background agent extracts structured session notes into memory.md at regular intervals. When compaction kicks in, Pochi uses this memory file as the summary source instead of generating a fresh one from scratch.

  Most noticeable on long debugging or refactoring sessions where compaction previously felt like Pochi losing its place. #1480

• Scoped Tool Access for Custom Agents: Custom agents can now declare precise access policies for file operations and web requests — restricting which paths they can read or write, and which domains they can fetch from.

  Previously, custom agents had full filesystem and web access with no hard enforcement. Scoping was prompt-only.

  Use executeCommand(npm *) to whitelist commands, readFile(src/**) to limit file reads, or webFetch(domain:*.``example.com``) to restrict web access. Policies are enforced at the tool level.

  For the full list of supported configurations, check the custom agent docs. #1497, #1495

✨ Enhancements

• Microbatch Parallel Tool Execution: Tool calls now execute in micro-batches based on side-effect profile. Reads and git commands run concurrently; writes serialize automatically.

  Pochi already ran tool calls in parallel, but with no side-effect awareness — reads and writes could race, and a failed call wouldn't cancel downstream dependencies.

  Most noticeable on tasks that span multiple files and git history simultaneously. #1477

• Compact File Preservation: When compaction kicks in, Pochi snapshots the files you were actively reading and carries them forward — full content where they fit, file references where they're too large.

  Previously, compact summaries dropped file context entirely. After compaction, Pochi would re-read files it had already processed, burning tokens and losing step.

  Most useful for long refactoring or debugging sessions across multiple files. #1481

• Attachment Preview in Chat Input: File attachment previews now appear inside the chat input form rather than outside it.

  The previous placement made it easy to lose track of what was attached before sending — especially with multiple files queued. #1485

• Web Search Multi-Query: The webSearch tool now accepts up to 5 queries in a single call, batching related searches into one request instead of N sequential ones.

  Researching multiple facets of a problem previously meant chaining search calls, each waiting on the last. #1479

• Webview Performance: Message list rendering is faster on long sessions. Key components are now memoized and checkpoint calculation refactored from O(N²) to O(N).

  Long tasks with many tool calls and diffs caused noticeable slowdowns as the message list grew. #1494

🐛 Bug Fixes

• Tool Call Input Null Fix: Pochi no longer throws a Field required error when retrying an interrupted task.

  When a task was cancelled mid-stream, tool call inputs could be left as null. The Anthropic API requires a non-null object, so the next retry would fail immediately with a validation error. #1463

• Reasoning UI Display Fix: The reasoning block now shows the correct loading state during streaming and after completion.

  An incorrect isLoading condition prevented the reasoning component from re-rendering when its loading state changed. #1504

• VS Code 1.118 Task Panel Fix: Pochi no longer fails to open the task panel on VS Code 1.118.

  VS Code 1.118 changed how its webview service worker routes internal resource requests. Workers launched without a webview ID couldn't route requests back to the correct panel, causing it to error on load.

  Workers now carry the webview ID through their bootstrap URL so VS Code routes requests correctly. SQLite assets are also inlined to sidestep the same routing issue. #1508

🔥 Preview

• Auto Memory + Auto Dream: We're building persistent memory across sessions — a MEMORY.md file that Pochi maintains over time.

  Store context, preferences, and project notes that carry forward automatically.

  Tell Pochi to "remember" or "forget" anything, and it updates the file directly.