coordinate

Coordinates Codex App tasks through the session-bound AgentStack bridge for ORRERY Mail identity.

7|3|Updated Sep 3, 2026
One-click install
npx skills add https://github.com/gyroid-eth/orrery-telemetry --skill coordinate-gyroid-eth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coordinate
Source: https://github.com/gyroid-eth/orrery-telemetry/tree/main/integrations/codex_app/plugin/skills/coordinate
Command: npx skills add https://github.com/gyroid-eth/orrery-telemetry --skill coordinate-gyroid-eth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When running multiple coding agents, a Codex App task needs a reliable way to know its own identity and exchange messages with other agents without guessing from environment variables or terminal state. This Skill routes all coordination through the session-bound AgentStack bridge so identity and messaging stay consistent. ## Core Features & Use Cases - Session-bound bootstrap: Call agentstack.bootstrap once with the current session_id (plus agent_id for subagents) to establish the authoritative identity for all later coordination calls. - Mail and file coordination: Fetch inbox messages, reserve files before editing, acknowledge or reply to delivered messages, and report verification results to the requesting agent. - Identity reporting: Use agentstack.runtime_status with no arguments when asked which agent the current task is, instead of inferring from AGENT_NAME, TMUX, or pane titles. - Use Case: A Codex subagent spawned via delegation bootstraps with its hook-provided agent_id, receives pending mail after a cold wake, reserves the files it will edit, and reports results back to its parent agent. ## Quick Start Ask the agent to coordinate this Codex App task through AgentStack by bootstrapping the current session and checking the inbox for pending messages.

Frequently Asked Questions about coordinate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify which agent a Codex App task is?

Call agentstack.bootstrap once with the current session_id, then use agentstack.runtime_status with no arguments. The bootstrap result is the authoritative identity; never infer it from AGENT_NAME, TMUX, or pane titles.

How does a Codex subagent bootstrap with AgentStack?

A subagent calls agentstack.bootstrap with both the current session_id and its hook-provided agent_id. After bootstrap, it must not pass session IDs, agent IDs, project keys, or agent names to later coordination tools.

What happens when a Codex task has pending ORRERY Mail?

When a PostToolUse notice or cold-wake prompt reports pending mail, call agentstack.fetch_inbox to retrieve message bodies through the proxy. Cold wake only resumes idle tasks; active turns receive the PostToolUse notice instead.

Can I use environment variables to determine agent identity?

No. The Skill explicitly forbids inferring identity from inherited AGENT_NAME, TMUX, TMUX_PANE, or pane titles. Only the bootstrap result from the AgentStack bridge is authoritative.

What should I do if AgentStack bootstrap fails?

If bootstrap fails, report that the identity is unknown and stop all coordination activity. Do not attempt to work around the failure using shell or terminal state.