TgWitnessDocumentation / 01
Work the archive
Find the message. Check the source. Build the case.
These tools are available from the current main branch. The 0.7.0 portable preview predates them; use a source checkout for this workflow.
Load past messages from your enabled sources into the workspace.
Search the archive and open the saved message behind each result.
Save your analysis separately and export the signed evidence beside it.
Load past messages
- Open Sources, review the enabled chats and start observation.
- Choose Load full history. The run uses the source list selected at that moment.
- Use Pause history and Continue history as needed. After a restart, resume explicitly.
- Check the per-source result and attachment queue. Save the signed progress report with the evidence export.
This fills the workspace with available messages. A per-chat HTML/JSON export is a separate operation. History and recovery details.
Search first, then decide about AI
- Open Ask the archive. Choose a workspace, chats and observation period.
- Search a phrase, domain or message ID. Open the matching record and its saved versions.
- For AI analysis, the administrator first configures a provider. Review Data sent to the model and uncheck unwanted excerpts before approving the request.
- Check the returned citations. Save the answer as a report and add your own revision or notes.
Search runs locally without AI. Analytical reports keep source references and revision history; they are separate from the signed journal. Provider setup and reports.
Choose the connection you need
| Task | Open | Setup |
|---|---|---|
| Read selected chats from an AI client | Integrations → MCP | Install the MCP extra, issue a scoped token and connect the client |
| Recognize text in saved media | A media.saved record → Recognize attachment | Set up the local Docker worker and required language/model files |
| Send events to n8n or a SIEM | Integrations → Outgoing webhooks | Add a receiver, verify HMAC and deduplicate event IDs |
Which access token goes where?
Panel access is for people reviewing the case. MCP connections get separate read-only archive tokens. A webhook receiver uses its own HMAC secret. None needs a Telegram session file.
Hand over sources and conclusions
Keep the reviewed analytical report alongside the signed evidence ZIP. The report explains your reading of the sources; the ZIP lets a recipient check the saved record against an independently trusted fingerprint and checkpoint.