Moonwind is early and the product docs are not public yet. Here is what you can read now and what the first guides will cover.
Read the technical notes in Labs or send the team a specific implementation question.
The first documentation will focus on workflow shape, access, approvals, reusable patterns, and integrations.
Follow a durable assignment from issue intake to a reviewed pull request, including retries and approval gates.
The first guides focus on what enters, how state survives across attempts, where judgment happens, and what evidence leaves with the result.
Understand tasks, runs, approvals, workspaces, traces, and team policies.
These concepts make authority and state visible so a team can reason about an agent workflow before it reaches production work.
Reference patterns for bug fixes, dependency upgrades, release notes, and review-heavy changes.
Each pattern is intended to show the checkpoints and handoffs that matter, rather than hide them behind a single automation step.
Connect Moonwind to GitHub, issue trackers, chat, and the agent runtimes your team already uses.
Integration guidance begins with tool boundaries, credentials, and approval policy before configuration details.
Good agent documentation should explain access, approvals, failures, and recovery before it explains advanced configuration.
Tell us what you are building and where the current guidance falls short.