Files, Images & Outputs
Use Claw with screenshots, charts, and generated artifacts.
Image Input
Claw can work from Telegram image input, including screenshots and photo groups.
Useful examples:
- a chart screenshot you want interpreted in portfolio context
- a screenshot of positions or order flow you want summarized
- a tweet or market graphic you want turned into a decision-oriented read
You do not need to translate the image into a perfect prompt first. Send the image and describe the decision you want help with.
Generated Outputs
Claw is not limited to text replies. It can return generated artifacts directly into Telegram when the best answer is a file.
Examples:
- charts
- CSV exports
- reports
- generated images
- PnL cards
That includes visual outputs like generated charts, not just plain-text summaries.
Best Way To Ask
Ask for the deliverable directly:
- "Generate a CSV of my recent activity."
- "Make a compact PnL card for this position."
- "Turn this screenshot into a summary I can forward."
- "Create a chart and send me the file."
What Makes This Different From Normal Chat
Claw can create files inside its runtime and send them back into Telegram. That makes it useful for workflows where the right answer is:
- a document to review later
- a visual summary
- a shareable artifact instead of a conversational reply
In the example above, the user asks for transaction history as a CSV, Claw prepares it, summarizes what is inside, and sends the file back into Telegram.
Practical Limits
- Telegram output still has message length constraints, so long analyses may be split across messages.
- Artifact delivery works best when you ask for a clear output format.
- Some files may fail to send if they are too large for the current Telegram delivery path.
If you want to understand why these outputs can persist across a session, see Memory, Context & Sessions.