threads

Pioneer Threads

Use Threads for conversation discovery, source reading, and permitted conversation actions. Read, search, create, send, and start are separate operations:

• thread_create creates a thread; it does not run a model.
• thread_message_send adds a message; it does not run a model.
• threads_turn_start starts a turn at a permitted destination with agent-authored input. It does not create a durable Task or enter the attached-subagent protocol.

Tasks and attached subagents have separate skills, system:pioneer/tasks and system:pioneer/subagents. Do not apply their wait, review, or accept protocol to a thread turn.

Tool Discovery And Authority

A native agent opens hidden tools by requesting the domain, not individual names:

{"domains":["threads"],"reason":"Need to find and read accessible conversations or perform permitted thread actions."}

Call request_tools only when it is available and the needed tools are hidden. Use only the subset actually available to this execution. A loaded skill neither supplies tools nor grants permission.

For CLI runtimes, system:pioneer/threads resolves to the exported pioneer-system-threads skill. Load it through the runtime's skill mechanism or read its exported SKILL.md; resolve references/ relative to that directory. Use the issued callable names in the current turn's fixed MCP catalog and capability instructions. CLI does not require request_tools or read_skill. Other system references do not imply an available CLI export.

Read access is scoped to the initiating user's current permissions, workspace, and admitted execution. Knowing a threadId permits neither reading nor writing by itself. Writes and launches require server-issued opaque options; options enumerate existing permissions and cannot create rights. Every page and every source transition rechecks access.

Working Sequence

1. Choose the operation from the user's intent. Use threads_list for accessible saved conversations, threads_search for indexed content, and threads_history_read for the actual history.
2. For non-trivial payloads or exact fields, read references/tool-schemas.md first. For concrete sequences, read references/workflows.md.
3. Follow pagination and complete record fragments before interpreting their contents. Keep cursors with their original operation and parameters.
4. Open relevant search sources with a history anchor. Follow child references selectively; do not automatically read every descendant.
5. Use threads_tools_result_read with an exact supplied reference for a large saved tool output or saved complete search page.
6. For create/send/start, obtain the relevant creation or target option, perform the requested action, and report only the confirmed result.
7. After failure, stale state, partial reading, or an uncertain mutation outcome, read references/troubleshooting.md before retrying.