Enable dangerous tools in Telegram agent via ToolFactory injection

[Copilot]

Telegram agent dangerous tools support ✅

Implementation Complete

• Understand the issue: Telegram bot cannot use dangerous tools (bash, read_file, write_file, edit_file)
• Analyze heartbeat fix: HeartbeatRunner was fixed to accept ToolFactory callback for injecting CLI tools
• Modify run_telegram_bot to accept optional ToolFactory parameter (similar to HeartbeatRunner)
• Update BotState to store the tool factory
• Modify agent creation in handle_chat to extend tools using factory (similar to heartbeat at line 346-349 of runner.rs)
• Update daemon.rs to pass create_cli_tools factory when starting Telegram bot
• Document the changes and pattern used
• Fix cargo fmt formatting issues

Summary

Applied the same ToolFactory pattern used for HeartbeatRunner to the Telegram bot, enabling it to use dangerous tools (bash, read_file, write_file, edit_file) when running in daemon mode.

Changes Made

telegram.rs:

• Added ToolFactory type definition
• Added tool_factory field to BotState
• Modified run_telegram_bot() to accept tool_factory parameter
• Added tool extension logic in handle_chat()

daemon.rs:

• Created tool factory wrapping create_cli_tools()
• Pass factory to run_telegram_bot() call

Pattern Applied

Exact same pattern as HeartbeatRunner (crates/core/src/heartbeat/runner.rs):

1. Define ToolFactory type - boxed function Config → Vec
2. Accept optional ToolFactory parameter in public function
3. Store factory in state structure
4. Extend agent with factory tools after Agent::new()
5. Daemon injects create_cli_tools() via factory closure

Security

• Tools only injected when running via localgpt daemon start
• Mobile/web builds don't get dangerous tools
• All dangerous tools run in sandbox with restrictions
• Follows principle of least privilege

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Telegram agent also cannot use "dangerous" tools now?</issue_title>
<issue_description>Okay now that I've got my daemon up and running again that the heartbeat works, I tried to reply to tell it to download a link into a file for later reference... but it replied immediately saying no file tools... argh, this was all working back in v0.1 ... while I appreciate the focus on providing security, sandboxing, and all that... I run mine in an isolated low-priv user, and I very much want it to be able to do everything that that user can do at all times... can we just like have a setting for "Yes Please, let LocalGPT Do All The Things Its System User Can Do" back?</issue_description>

<agent_instructions>check what blocked telegram to use all tools, maybe the same issue as the core crate is refactered out, so need similar fix as have heartbeat back</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Telegram agent also cannot use "dangerous" tools now? #44

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[yiwang]

@copilot fix ci format error

[Copilot]

@copilot fix ci format error

Fixed in bdc7c90. Ran cargo fmt to apply standard Rust formatting to the function signatures and await expressions.