PicoClaw
PicoClaw users ask for session switching inside chat channels
A PicoClaw request says Telegram users can list and switch models but cannot inspect or change sessions without editing local JSON. Two related MCP requests seek OAuth 2.1 with PKCE and dashboard-managed authorization, pushing more operator state into remote chat and web surfaces.
sipeed/picoclaw issue #3307 is the inspected primary source: “[Feature]: session list/switch command for Telegram (and other chat channels).” The two related records below were inspected as supporting context, not treated as independent confirmation.
The facts
- sipeed/picoclaw issue #3307 was created 2026-07-30T18:51:06Z and was open at inspection; its title is “[Feature]: session list/switch command for Telegram (and other chat channels).” - sipeed/picoclaw issue #2546 was created 2026-04-16T10:16:18Z and was closed at inspection; its title is “[Feature] Support OAuth 2.1 + PKCE for MCP servers, addable from dashboard.” - sipeed/picoclaw issue #3302 was created 2026-07-30T13:59:44Z and was open at inspection; its title is “[Feature]Support OAuth 2.1 for MCP servers same as #2546.” - The repository reported 29785 stars, 56 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 issue #3307 reports: Problem The Web UI has a full session management system — users can list, switch, and delete conversation sessions via the history dropdown (session-history-menu.tsx). However, there is no equivalent capability from Telegram (or any other chat channel). Users on Telegram cannot: List their available sessions (/session list) Switch to a different session (/session switch ) Create a new ad-hoc session (/session new) Sessions are always auto-derived from inbound context (channel, chat_id, sender, etc.) via session.AllocateRouteSession, with no user-facing override mechanism. Expected Behavior A set of slash commands accessible from Telegram
sipeed/picoclaw issue #2546 reports: The Goal / Use Case Let non-technical users add OAuth-protected MCP servers from the launcher dashboard by pasting a URL — same UX as Claude.ai's "Add connector." Works on cloud VMs with public URLs, no shell, no Node.js. Proposed Solution Dashboard form to add an MCP by URL. Built-in OAuth 2.1 + PKCE with refresh token handling, reusing the launcher's own URL as the redirect URI so the browser flow completes inside the dashboard. Impact & Roadmap Alignment [ ] This is a Core Feature [x] This
sipeed/picoclaw issue #3302 reports: The Goal / Use Case Support OAuth 2.1 for MCP servers same as issue 2546 Proposed Solution Potential Implementation (Optional) Impact & Roadmap Alignment [ ] This is a Core Feature [x] This is a Nice-to-Have / Enhancement [ ] This aligns with the current Roadmap Alternatives Considered Additional Context
Why it matters
Session selection controls which history, identity and permissions a message inherits. Exposing it in chat is useful only if the command names the active scope and cannot cross accounts or agents accidentally. This is an operator boundary: persisted state, execution ownership and visible controls must describe the same event. A workaround that broadens access, deletes state or hides the symptom would trade a visible defect for an unmeasured one.
Current
The primary record was open when captured on 2026-07-31. The release baseline was nightly published 2026-07-02T01:26:53Z. Current 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/issues/3307. Supporting records are https://github.com/sipeed/picoclaw/issues/2546 and https://github.com/sipeed/picoclaw/issues/3302. Their source bodies, timestamps and states were captured 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. Issue closure would not by itself prove a deployed fix. Search residue, package mirrors and historically published source spines were excluded.
Operator take
Design list, switch and create operations around explicit channel/account ownership; require confirmation when context changes, and keep OAuth verifier state out of chat-visible transcripts. 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.