Make Developers a clean CLI and API reference - #2000
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ff0196aada
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| <pre>curl '` + base + `/work' \ | ||
| -H "Authorization: Bearer $MU_TOKEN" \ | ||
| -H 'Content-Type: application/json' \ | ||
| -H 'Accept: application/json' \ | ||
| -d '{"agent":"researcher","prompt":"Compare SQLite and PostgreSQL for a small personal server"}' | ||
| -H 'Content-Type: application/json' \ | ||
| -d '{"prompt":"Research the options and recommend one"}' |
There was a problem hiding this comment.
If POST /work completes server-side but the client loses the response, repeating this curl creates another durable task because the product endpoint has no idempotency key; both jobs may consume credits and repeat tool side effects. This rewrite removes the previous inspect-before-retry warning while continuing to advertise the raw POST, so restore that warning adjacent to the example or document an idempotency mechanism.
Useful? React with 👍 / 👎.
| <h2>CLI</h2><p>Install Mu and connect to your account:</p><pre>curl -fsSL https://raw.githubusercontent.com/micro/mu/main/install.sh | sh | ||
| mu login ` + base + ` |
There was a problem hiding this comment.
On a fresh machine where ~/.local/bin is not already in PATH, the piped installer puts mu there and exports the updated path only inside its child shell, so the immediately following mu login fails with command not found. Invoke the installed binary by its full path or tell the user to reload/source their shell before continuing.
Useful? React with 👍 / 👎.
| <table class="data-table stacked"><thead><tr><th>Resource</th><th>Use</th></tr></thead><tbody> | ||
| <tr><td><code>POST /agent</code></td><td>Ask Micro with a prompt and optional thread.</td></tr> | ||
| <tr><td><code>POST /agent/NAME</code></td><td>Ask a specific agent.</td></tr> | ||
| <tr><td><code>GET /agents</code></td><td>List your agents.</td></tr> |
There was a problem hiding this comment.
A bearer-authenticated client following a table-only entry such as GET /agents without Accept: application/json receives the HTML resource because these handlers select JSON through content negotiation. The curl examples do not cover /agents or /inbox, and this change removes the previous global header requirement, so restore an explicit Accept: application/json instruction beside the table.
AGENTS.md reference: AGENTS.md:L16-L18
Useful? React with 👍 / 👎.
1 participant
Developers had become an agent-creation walkthrough. Restore the curl installer and focus the page on the useful entry points: asking Micro, assigning work, reading results and using services. Put Tools/MCP, API, x402 and token links at the top; keep self-hosting as a short link to its guide.
Checked examples against the installer and CLI dispatch/HTTP handlers. Server and CLI tests pass. Uses existing shared document and table styling; fresh desktop/mobile screenshots were unavailable.