A platform for creating custom Telegram AI bots.
30-day usageAug 14–Sep 12, 2026
Data as of September 13, 2026 · About the data
Capabilities and verification
Reviewed against the HarnessRouter capability catalog on August 24, 2026. Every verified row cites its public source; rule-derived rows apply HarnessRouter's published classification rules to documented behavior. A “No public evidence” badge marks a gap in the public record, not a statement that TeleClaw lacks them.
Configuration & support
- Other modelsDirectly verified
- Custom instructionsNo public evidence
- SkillsNo public evidence
- Custom toolsNo public evidence
- MCPNo public evidence
- Sandbox & approvalsDirectly verified
- SessionsDirectly verified
- SubagentsNo public evidence
Execution & agency
- Workspace filesNo public evidence
- Structured actionsDirectly verified
Environment control
- Browser controlNo public evidence
- Computer controlDirectly verified
Observation & capture
- Screen observationNo public evidence
- Screenshot exportNo public evidence
- Recording exportNo public evidence
Artifact outputs
- DocumentsNo public evidence
- SpreadsheetsNo public evidence
- PresentationsNo public evidence
- ImagesNo public evidence
- VideoNo public evidence
- App deploymentNo public evidence
Sources: teleclaw.info
Machine interfaces
No public machine interface was documented at the August 24, 2026 review. This records what public documentation showed, not that no interface exists.
Want TeleClaw supported through UHPUnified Harness Protocol defines a shared contract for running agent harnesses through one interface. A compatible implementation lets HarnessRouter support this harness without changing your product integration.?
Join the HarnessRouter Discord and post an implementation request in #unified-harness-protocol. Tell us the real task you want to run. Do not include private task data.
Join Discord to request support