Turn exported group chat into a searchable Markdown archive
Recipe template · not yet tested on this site
This page is a recipe template, not yet tested here. Run logs, tokens and time go in after re-testing; until then no estimated numbers are filled in.
When to use
Six months of decisions are buried in thousands of chat messages. Finding who agreed to what means scrolling, and failing that, holding the meeting again.
Preparation
- Host version
- To fill (record the exact rc version when testing)
- Model
- To fill
- Mode / permissions
- Standard mode + modify-within-workspace is enough to start
- Plugins required
- None (add name & version after testing if used)
- Input materials
- Keep in a separate workspace; back up originals first
Full instruction
Turn this exported group chat into a searchable Markdown archive.
The export is plain text or JSON and formats vary. Requirements:
1. Identify the export format first (where timestamp, sender and body live), print the first five parsed messages for confirmation, then process everything.
2. Split by date: one .md per day, named 2026-11-14.md, under an archive/ directory.
3. Start each daily file with a three-line summary: what was discussed, what was decided, what is still open.
4. Also produce index.md: grouped by topic, each line pointing to a date and file location.
5. Redact phone numbers, ID numbers, email addresses and street addresses; keep only the display name needed to identify the speaker.
6. Finish with: date range covered, total messages, messages redacted, parse failures.Run log
| Item | Value | Note |
|---|---|---|
| Time spent | to be tested | |
| Result | to be tested | |
| In / out tokens | to be tested | |
| Leftovers | to be tested |
Output
After a successful run, list files and screenshots here, and note whether originals changed.
Acceptance checklist
Tap to tick each item off as you verify.
- Format confirmed on a small sample before the full run
- One file per day, filename matches the date inside
- Every index entry resolves to text in its file
- Spot-check ten messages: no complete phone or ID number left
- Unparsed messages listed rather than dropped
Failures & boundaries
- Export formats differ a lot between clients; a different export means confirming field positions again
- No automated login scraping here: only files you exported yourself
- Redaction is rule-based and can miss unusual formats; confidential material should not go through this flow
- This is a recipe template; it has not been run end to end on this site yet
- Blocked on: Needs a real chat export. Every sample on hand contains real names and contact details and cannot go on a public page, while a synthetic chat cannot reproduce the real mess: line breaks, quotes, image placeholders.