pi-telegram-manager
Telegram bridge for Pi local coding agents: terminal-continuation and business manager modes
Install
pi install npm:pi-telegram-manager
Installs from npm into ~/.pi/agent/.
Add -l for project-local (.pi/). Manage with pi list / pi update / pi remove.
What this package can reach
Detected automatically from the source at
version 0.6.2.
This describes access, not safety — you decide whether it's appropriate for what
the package claims to do.
- Behavior — Changes how the agent thinks Modifies the system prompt, injects messages, or rewrites conversation context.
- Credentials — Handles your API keys Reads or passes provider credentials. Highest-trust capability there is.
- Files — Reads files outside your project Touches paths beyond the working directory, such as your home folder.
- Intercepts tools — Can block or rewrite tool calls Subscribes to tool_call/tool_result/input. Can change a command after you approved the one displayed.
- Network — Talks to the internet Makes outbound network requests. Check the destinations are ones you expect.
- LLM traffic — Sees raw model API traffic Reads or replaces provider requests, headers or responses — including your prompts.
- Subagents — Spawns agents or sessions Runs additional agents. Ask whether it caps iterations and spend.
- Tool control — Can switch pi's tools on and off Calls setActiveTools, so it can disable built-ins — including safety-relevant ones.
- New tools — Adds model-callable tools Gives the agent new abilities. Additive and visible, unlike an override.
- UI — Draws its own interface Renders widgets, footers, dialogs or full-screen views.
What it actually did when run
observedLoaded in a sandbox with no network, a read-only filesystem and a recording stand-in for pi's API. This is what it called — not what the source suggests it might.
Tools registered telegram_bot_abouttelegram_attachmanager_replymanager_silentmanager_remembermanager_skipmanager_identifymanager_forgetmanager_candidatesmanager_verifymanager_resolve_draft
Events subscribed agent_endagent_settledagent_startbefore_agent_startbefore_provider_requestcontextinputmessage_endmessage_startmessage_updatesession_before_compactsession_compactsession_shutdownsession_starttool_calltool_execution_endtool_execution_startturn_end
APIs called cwd.slicecwd.startsWithgetActiveToolsgetAllToolsgetAllTools.mapmodelRegistry.getApiKeyAndHeadersregisterCommandregisterToolsessionManager.getSessionIdui.notifyui.select
3 calls the source scan did not predict
cwd.slice · cwd.startsWith · getAllTools.map
Reached through a value the scan could not follow — passed as an argument, stored on another object, or returned by a helper.
Run against version 0.6.2 on 2026-08-02.
Registration-time behaviour under default settings; other configurations may differ.
Reviews
0 publishedSign in with GitHub to write a review, reply, or vote.
No reviews yet — be the first.
More in Bridges
- pi-roam — Post-hoc handoff of a live Pi session into tmux for remote continuation, with optional Tai…
- pi-tldraw — Pi extension that opens and persists a local tldraw MCP canvas.
- @qianhuan-lxs/pi-mcp-bridge — Pi Agent extension that bridges MCP servers to the LLM via two dynamic-context tools (Call…
- pi-codegraph-extension — CodeGraph MCP tools for the Pi Coding Agent — semantic code search, impact analysis, call …