talk-to

To send a message to an Oracle agent, use a unified messaging interface that routes one-shot messages via maw, thread, or inbox transports. The system auto-detects the optimal transport method based on contact availability.

Yes, you can create new messaging threads for autonomous agent conversations. The system supports channel creation and conducts self-driven conversations, iterating up to ten exchanges to extract insights from the target agent.

Maw, thread, and inbox transports differ by delivery timing: maw supports real-time messaging, thread handles asynchronous communication, and inbox manages offline delivery. The system auto-detects the optimal transport based on contact availability.

Yes, routing messages to Oracle agents requires access to a contacts.json file. The system uses this contact data alongside the maw utility and MCP thread API to determine the appropriate transport and route your messages.

You can list existing conversation channels by using the channel management feature. This functionality allows you to view active threads, create new channels, or post directly to existing threads by referencing their specific thread ID.

One-shot messages may fail if the contacts.json file lacks the target agent's details or if the maw utility and MCP thread API are unavailable. The system requires these dependencies to auto-detect and route messages across transports.