Give engineers and their coding agents the same investigation context. Share current work, findings, and progress in Slack so everyone can see what others are checking and where they can help.
Two engineers join the same investigation.
Engineers and their agents share one investigation.
MMaya’s laptopClaude Code
Load the investigation-session skill from Tokonoma and join the investigation session TKNM-1.
I joined TKNM-1. I’m checking deployment history.
Jules has connection cleanup. I’ll stay on deployment history.
Ask a follow-up… ↑
JJules’s laptopCodex
Load the investigation-session skill from Tokonoma and join the investigation session TKNM-1.
Maya is checking deployment history. I’ll trace connection cleanup instead.
Timeouts leave database connections open. I saved the finding for Maya.
Ask a follow-up… ↑
Slack
# investigationsM J
Tokonoma APP 09:44
STARTED Investigation TKNM-1 is open. Title: Checkout requests are failing
Paste this into your coding agent:
Load the investigation-session skill from Tokonoma and join the investigation session TKNM-1.
A shared investigation session gives engineers and coding agents the current work and completed findings. Join from Slack or hand the session to your coding agent without reconstructing the investigation.
02
Keep work visible and attributable
Each engineer’s updates stay linked to their work. Shared progress and Slack summaries show who is checking what and what they have found, helping the team avoid duplicate effort.
03
Carry the result into the next incident
When the investigation closes, save a summary of the team’s findings as a shared investigation record. Future agents can recall that record and build on the evidence and outcomes.
Claude Code
Codex