Repository navigation
docs: state AO facts plainly for search and AI answers - #6912
AgentWrapper wants to merge 22 commits into
Conversation
🏆 Review leaderboardOct 12–19, 2026 · UTC
Ranked by distinct external PRs reviewed, then review rounds, then PR comments. Self-activity and bot activity are excluded. Show 8 more reviewers
|
AgentWrapper
left a comment
There was a problem hiding this comment.
Changes requested. Reviewed head 062fcc1. The license metadata changes in forge.config.ts (rpm), frontend, product-ui, the ao npm packages and the lockfiles all match the Apache-2.0 LICENSE file. The 36-agent count matches the README table. The claims that the QR carries Tailscale 100.x addresses and that tunnel-only hosts drop LAN/Tailscale addresses match backend/internal/mobilebridge/endpoints.go and BridgeService.Status. One blocking issue: the new copy says raw Tailscale works on Android, but the same docs page still says Android behavior is unverified and that no physical Android device was tested (see inline comments).
Optional, non-blocking: nothing in the repo references the App Store id 6792552173 or the Play package aoagents.dev, so please click-check both store links before merge. The README intro now says "formerly Agent Orchestrator, AO" and then keeps calling the product AO, which reads a little oddly. homepage/repository in frontend/package.json, product-ui/package.json and the rpm options still point at github.com/aoagents/agent-orchestrator, while packages/ao now points at OrchestratorInc.
AgentWrapper
left a comment
There was a problem hiding this comment.
Approved. Reviewed head b30a7ed. The earlier blocking finding is fixed. Android over Tailscale is now described as allowed (the Android app sets usesCleartextTraffic: true) but not verified on a device, the same way in the README Mobile section, the README FAQ, the remote-access table, the Tailscale steps and the troubleshooting rows, and that matches the existing unverified note. The Developer-mode note for Remote hosts is correct: settingsCatalog.tsx shows the remoteHosts section only when developerMode is on, and useRemoteHosts gates on developerMode && remoteHosts (the second flag defaults to on). The license metadata matches the Apache-2.0 LICENSE file.
Optional, non-blocking: click-check the App Store (id6792552173) and Google Play (aoagents.dev) links, which nothing else in the repo references. The frontend, product-ui and rpm homepage/repository fields still point at github.com/aoagents/agent-orchestrator.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
AgentWrapper
left a comment
There was a problem hiding this comment.
Changes requested. Reviewed head 38b8ec2 (new: the two AO Cloud wording commits). The setup steps are accurate: Settings → General → Developer mode, then the Cloud toggle (CloudOfferingRow), then sign in to AO Cloud. One blocking issue: the copy says Cloud is available "in the nightly channel", but nothing in the code limits it to nightly, and the current stable release already ships it (inline).
Everything reviewed earlier is still fine.
AgentWrapper
left a comment
There was a problem hiding this comment.
Approved. Reviewed head 56b161b. The Cloud finding is fixed. The README Mobile section, the README FAQ and the docs index Cloud card now describe AO Cloud as an early preview in current desktop builds, stable and nightly, turned on in Developer mode. That matches the code: {developerMode && <CloudOfferingRow />}, no update-channel check, and the full flow present in v0.14.2. No nightly-only wording remains in this PR.
Optional, non-blocking (from earlier passes): click-check the App Store and Google Play links. The frontend, product-ui and rpm homepage/repository fields still point at github.com/aoagents/agent-orchestrator.
AgentWrapper
left a comment
There was a problem hiding this comment.
Approved. Reviewed head 2703c01. The new "available now in the latest nightly" framing is accurate: nightly includes Cloud, and the copy no longer says nightly is required. The setup path (Developer mode, then Cloud, then Sign in to AO Cloud) matches the UI. "Anyone can sign in" is consistent with the code: sign-in creates an org when the account has none, and the cloud control plane has no invite or allowlist gate.
Optional, non-blocking: the README no longer mentions that stable builds also include Cloud. The Cloud guide in #6915 says so, which is enough. Click-check the App Store and Google Play links. The frontend, product-ui and rpm homepage/repository fields still point at github.com/aoagents/agent-orchestrator.
AgentWrapper
left a comment
There was a problem hiding this comment.
Changes requested. Reviewed head 643ccae (new: AO Cloud generally available, plus a Plans section). What checks out: Settings → Upgrade is the right label, Free / Starter / Pro / Enterprise and Talk to founder match , and "Everything in Free / Starter" matches the cards. Three blocking issues (inline): the GA claim contradicts the in-app Enable Cloud warning, Bring your own Coder is listed under Pro but is an Enterprise feature, and the plan limits are not the dimensions the app enforces or displays.
Optional, non-blocking: the app's Free card lists "Claude Code, Codex and Cursor" while the table says "any supported harness". Local use has no plan check, so the docs are right on behavior, but the two should be aligned.
AgentWrapper
left a comment
There was a problem hiding this comment.
Changes requested. Reviewed head ad7f273 (new: prices plus device and connectivity tiers in Plans). The three findings from review 5567235492 (GA vs the in-app preview warning, Coder under Pro, plan-limit dimensions) are unchanged and have no replies, so they are posted again. A fourth is new: the device and relay tiers contradict the Upgrade page and this README's own Mobile section. If the pricing and tiers come from a product decision that the app has not caught up with yet, reply on each thread saying so and link the app change. The docs and the shipped app should not disagree.
AgentWrapper
left a comment
There was a problem hiding this comment.
Approved. Reviewed head b2b336b, which merges main including #6907. That billing change moved the app to match this Plans table: Bring your own Coder is now on Pro (settings.billing.proCoder), limits are shown as cloud projects and simultaneous cloud agents, Free lists 2 devices and no cloud relay, Starter adds the relay and unlimited devices, and Enterprise lists unlimited projects and agents plus collaboration. So the Coder, limits and device-tier findings from review 5567256267 are resolved by the app. The Free row now also correctly keeps free remote access over your own Tailscale or the managed HTTPS tunnel, consistent with the Mobile section, and the sandbox caution is back.
Non-blocking notes:
- "Generally available" is now a product decision the docs carry with a caution, but the in-app Enable Cloud dialog still says "early, highly unstable preview ... Only enable it if you are actively testing" (settings.cloudConfirm.description), and Cloud is still behind Developer mode. Update that dialog in a follow-up app PR so a new user is not told GA by the README and "only if testing" by the app.
- The $20 and $40 prices are not in the repo (they come from Stripe at runtime). Keep them in sync with the Stripe products.
AgentWrapper
left a comment
There was a problem hiding this comment.
Changes requested. Reviewed head 2286b2c. "Available now as an early preview" resolves the earlier mismatch with the in-app Enable Cloud dialog. Two new blocking issues (inline): the new pricing link is a 404, and the new Cloud relay row in remote-access.mdx documents a connection method that is not implemented.
AgentWrapper
left a comment
There was a problem hiding this comment.
Changes requested. Reviewed head 2c40557. The Cloud relay row is gone from the remote-access connection table, and the relay and unlimited devices are now marked coming soon in the Plans intro and the Starter row, which matches the code (Connect Mobile has only lan, tailscale and tunnel endpoints). One blocking issue remains: the pricing link is still a 404 (inline).
Non-blocking: Starter and Pro now say 1/1 and 5/15. Those values come from Stripe at runtime and are not in the repo, so I could not verify them. Keep them in sync with the live Stripe products.
AgentWrapper
left a comment
There was a problem hiding this comment.
Approved. Reviewed current head 030e74c (the queued 779d86e plus one follow-up). The dead orchestrator.inc/pricing link is gone; plans now point to Settings → Upgrade. The new Teams & Enterprise waitlist link resolves (200). Cloud availability wording is neutral and still states the Developer mode, then Cloud, steps and the sandbox caution, so it does not conflict with the in-app Enable Cloud dialog. The unenforced 2-device limit is dropped from Free, and the relay stays marked coming soon. The plan figures come from Stripe at runtime and are not verifiable from the repo, so keep them in sync.
AgentWrapper
left a comment
There was a problem hiding this comment.
Approved. Head 030e74c is unchanged since review 5567370960, which approved this exact commit. Rechecked: the waitlist link still returns 200. No new findings.
AgentWrapper
left a comment
There was a problem hiding this comment.
Approved, with a merge gate. Reviewed head 8d1a66b. The Plans table no longer makes relay or device claims beyond "Coming soon: a cloud relay for access across devices" on Starter, which matches the code (no relay endpoint exists). Free keeps the accurate same-network, Tailscale and managed-tunnel access. The waitlist link returns 200.
Merge gate: https://orchestrator.inc/pricing still returns 404 as of this review. Per the worker reply, landing PR #64 publishes that page. Do not merge this PR until that URL returns 200; if #64 slips, drop the link.
Add an extractable summary, a Mobile and cross-device section and an FAQ to the README; retitle and extend the Remote access and mobile docs page with LAN vs Tailscale setup; add homepage, repository, bugs and keywords to the @aoagents/ao npm package and align npm licenses with Apache-2.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…se waitlist Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… cloud relay Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…aitlist Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
8d1a66b to
c7204c5
Compare
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
AgentWrapper
left a comment
There was a problem hiding this comment.
Approved, no changes needed. I checked the two new commits since 8d1a66b against main and the v0.14.4 tag.
- cloudflared wording is right.
frontend/forge.config.tsshipscloudflaredonly in darwin builds, already in v0.14.4 from #7002, and the package step fails if it is missing. On other platformssysteminstall.planCloudflaredinstalls it with winget on Windows and the system package manager on Linux. - The count of 37 is right for what ships (memcode is registered in v0.14.4).
Merge order: merge #7027 first or together with this PR. On this branch the Supported agents table still lists 36 names, so the FAQ line "37 coding agent harnesses ... See the Supported agents table above" only matches once #7027 adds the memcode row.
The pricing gate is cleared: https://orchestrator.inc/pricing returns 200 now.
Not blocking: planLinuxPackage depends on the distro having a cloudflared package. If that turns out to be unreliable, change "one-click install on Linux" to "install from Connect Mobile".
Summary
Makes the facts that search engines and AI assistants pull from easy to extract, with every claim checked against the code.
README.md
github.com/ComposioHQ/agent-orchestrator), open source (Apache-2.0), Claude Code, Codex and 35+ agents, parallel agents in isolated git worktrees, an orchestrator agent that plans work and spawns workers, the PR loop that sends CI failures and review comments back to the owning agent, desktop on macOS/Windows/Linux, and iPhone/iPad/Android apps.github.com/ComposioHQ/agent-orchestrator".AO Cloud and Plans (founder update, 18 October 2026)
settings.billing.*after fix(billing): show plan limits apply only to cloud agents #6907):remote-access.mdxstill lists only LAN, Tailscale and the HTTPS tunnel.npm metadata
packages/ao/package.json: adds a richer description, keywords,homepage,repository(withdirectory: packages/ao) andbugs.License fix: the repo has been Apache-2.0 since docs: add Apache License 2.0 #2233, but several manifests still said MIT. These now all declare
Apache-2.0:@aoagents/aoand its four platform packages (npm currently shows@aoagents/aoas MIT)frontend/package.jsonpackages/product-ui/package.jsonfrontend/package-lock.jsonandpackages/product-ui/package-lock.json.rpmmetadata infrontend/forge.config.ts, where MIT was hardcodedpackages/cloud-clientalready said Apache-2.0. Nopackage.jsonin the repo declares MIT anymore.npm publishing appears to have stopped. On npm,
@aoagents/aolatestis 0.10.3 (12 July 2026) andnightlyis 0.10.4-nightly.202607251158 (25 July 2026). GitHub releases are on 0.14.x: v0.14.2 stable and v0.14.3 nightlies. No workflow in this repo publishes these packages; they were published by hand withnpm publishafterpackages/build-binaries.sh. This PR does not change the publishing pipeline. Reviving or deprecating the npm package is pending a founder decision. Until something is published again, the new npm metadata and license stay in the repo only.Docs (docs.orchestrator.inc)
frontend/src/docs/content/and deployed by.github/workflows/deploy-docs.yml./configuration/remote-accesstitled "Connect Mobile". I renamed it Remote access and mobile and kept the URL, so existing links still work. I added:What the code says about pairing
mobilebridge.Endpointsputs LAN and Tailscale100.xaddresses in the offer assecure: false. Only the Cloudflare tunnel issecure: trueon port 443.packages/mobile/app.jsonallows cleartext on Android. iOS blocks cleartext to100.64.0.0/10. So Tailscale is documented as Android-only for now, and iPhone/iPad are pointed to the managed HTTPS tunnel.tailscale serveTLS on its own, but the offer does not include that endpoint yet, so the docs don't claim Tailscale HTTPS pairing works.127.0.0.1. The mobile listener is off by default and needs the connection password. The managed tunnel goes through Cloudflare, which terminates TLS, and the README says so.Tests
npm ci && npm run buildinfrontend/src/docs: passes, and the rendered/configuration/remote-accesspage includes the new content.Known gaps / follow-ups
translations/don't have the new summary, mobile section or FAQ yet.🤖 Generated with Claude Code