What problem does it solve?
It removes the friction of coordinating communication between agent identities by routing your message to the correct Oracle agent channel (via contacts, persistent threads, or offline inbox) instead of forcing manual, one-off coordination.
Core Features & Use Cases
- Contacts-first routing: Looks up the target agent’s transport details (maw, inbox path, thread) from
ψ/contacts.json (with a fallback path), so messages go where they should.
- Transport selection with clear intent: Supports auto, real-time
maw transport, persistent MCP threads, and offline inbox file drops.
- Conversation modes: Sends one-shot messages, creates new threads quickly, lists existing channels, or runs an autonomous up-to-10-turn loop for insight extraction.
- Use Case: When you need status updates or reasoning from a specific agent (e.g., “talk to pulse” or “message neo”), it finds or creates the right per-agent thread and posts your request on their channel with a follow-up read.
Quick Start
Send a direct instruction to the target agent with: /talk-to arthur "What's your status?"
