PicoClaw
PicoClaw routes context through the agent that owns it
PicoClaw’s routed agents were reading, summarizing and bootstrapping the default agent’s session store, leaving dispatched chats without history or compaction. A proposed repair resolves the owning agent for four context paths; adjacent reports cover private Telegram topic isolation and WebUI lag on longer histories.
sipeed/picoclaw PR #3316 is the inspected primary source: “fix: routed-agent context management not respecting history, summarization, compression, and seahorse bootstrap.” The related records below were inspected as supporting context rather than independent confirmation.
The facts
- sipeed/picoclaw PR #3316 was created 2026-08-03T21:51:43Z and was open at inspection; its title is “fix: routed-agent context management not respecting history, summarization, compression, and seahorse bootstrap.” - sipeed/picoclaw PR #3315 was created 2026-08-03T20:42:22Z and was open at inspection; its title is “Support topics in private bot chats.” - sipeed/picoclaw issue #3281 was created 2026-07-21T06:17:57Z and was open at inspection; its title is “[BUG]Web UI chat input is very laggy when history has a little bit long.” - The repository reported 29810 stars, 52 open issues, default branch main, and last push 2026-07-30T18:32:36Z. - The latest tagged-release baseline checked was nightly published 2026-07-02T01:26:53Z.
What changed
sipeed/picoclaw PR #3316 reports: Description Bug: I set up dispatch rules to route an agent to a specific discord channel, and noticed it wasn't remembering anything from previous messages, and auto-compaction never triggered regardless of the number of messages or tokens used in the session for that agent & channel. This PR fixes routed-agent context management so that per-agent context (history, summarization, compression, and seahorse bootstrap) operates on the **owning agent's** session store instead of the default agent's. For sessions owned by a routed (non-default) agent, three code paths incorrectly used registry.GetDefaultAgent(): **context_legacy.go — Assemble**: read history/summary from the default agent's store, so routed agents always saw empty history (the bug reported in #3301). **context_legacy.go — maybeSummarize / forceCompression**: summarization and overflow compression ran against the default agent's
sipeed/picoclaw PR #3315 reports: Description Fix Telegram topic handling for private chats with bots that have forum topic mode enabled. PicoClaw previously recognized topics only when Chat.IsForum was true. That works for forum supergroups but not private bot chats, where Telegram instead provides IsTopicMessage and MessageThreadID. This change: recognizes both forum-supergroup and private-chat topics preserves the thread ID in the composite chat ID and InboundContext.TopicID routes replies to the originating private topic isolates conversation history between private topics preserves existing behavior for non-forum group reply threads adds regression tests for inbound metadata, outbound routing, and session isolation Type of Change [x] Bug fix (non-breaking change which fixes an issue) [ ] New feature (non-breaking change which adds functionality) [ ] Documentation update [ ]
sipeed/picoclaw issue #3281 reports: Quick Summary Environment & Tools **PicoClaw Version:** 0.3.1 **Go Version:** 1.25.11 **Channels:** PicoClaw Web Steps to Reproduce 1. Open a session in web ui. 2. Make more chat history in one session. 3. Keep try to input something in input box, it will be very laggy. Actual Behavior The input box is very laggy, like stuck. Expected Behavior Input is very smooth like a new session. Additional Context
Why it matters
Multi-agent routing is not complete when only message dispatch changes. Context, compression, clearing and bootstrap must follow the same owner, or the interface presents one agent while state mutates another agent’s files. The operator test is whether persisted state, execution authority and the visible user outcome describe the same event after retries, restarts or delegation.
Current
The primary record was open when captured on 2026-08-04. The release baseline was nightly published 2026-07-02T01:26:53Z. Repository metadata, pull requests, issues, release records, Google News discovery, Hacker News discovery, Lobsters, Metamesh and the rendered ClawCharts row were checked. ClawCharts selected the subject; it did not prove the claim.
Evidence
The primary URL is https://github.com/sipeed/picoclaw/pull/3316. Supporting records are https://github.com/sipeed/picoclaw/pull/3315 and https://github.com/sipeed/picoclaw/issues/3281. Source bodies, timestamps and states are preserved in the daily evidence bundle. Test counts, reproductions and deployment observations remain attributed to their authors unless explicitly identified as independently rerun.
Source boundary
Open work is described as open, closed work as closed, and operator reports as reports. A pull request is evidence of proposed or reviewed direction, not proof of a shipped release. Search residue, package mirrors and historically published source spines were excluded.
Operator take
Exercise every context operation through non-default dispatch rules, inspect filesystem ownership after clear/compress, and profile the WebUI separately from backend context growth. Preserve a before-state receipt, make the smallest reversible change, and verify the original failure independently after intervention.
Caveat
Public project records are mutable. Status, scope and evidence can change after publication. This brief records the inspected state and does not authorize changes to a reader’s deployment.
Source inspected; source state, environment and release boundary remain explicit.