Visual plans your team can act on

• Plans are visual, not walls of text. Ask your AI coworker for a plan and it writes a rich, interactive page with diagrams, timelines, and comparisons, built to be decided on in ten minutes.
• Authored for you. You prompt in Claude Code or Codex; your coworker runs the ox CLI on your behalf to enrich, save, and render the plan.
• Grounded in your team's context. A plan cites the architecture decisions your team already wrote down, and flags where a coworker is already working in the same place. Every claim points at a real artifact, never a guess.
• Browse them as a team. Every saved plan lands in your team's Plans gallery in the console, newest first.
• Linked from the PR. When the work ships, the pull request carries a credit line back to the session and plan that produced it, so the reasoning travels with the code.

Read the Plans docs to see how to prompt for a great one.