feat: add Orgo provider

[zozo123]

Summary

Adds a delegated-run Orgo provider for Linux cloud computers.

• Registers provider: orgo with alias orgo-ai.
• Creates an owned workspace/computer, waits for readiness, runs Bash commands through the API, and performs guarded cleanup.
• Supports explicit workspace reuse only after exact owner, workspace, computer, endpoint, and local-claim verification.
• Keeps Orgo outside SSH/rsync and coordinator flows; runs require --no-sync.
• Adds provider configuration, docs, generated metadata, fake-API lifecycle coverage, and a dedicated guarded live harness.

Maintainer hardening

• Binds claims to the normalized API endpoint, Orgo owner, workspace, computer, and repository lease.
• Rejects raw/unclaimed IDs and fails closed on inventory, ownership, or cleanup ambiguity.
• Refuses to delete a created workspace if it contains an additional computer.
• Writes the claim before readiness polling, preserves it on failed cleanup, and removes it with compare-and-swap semantics only after confirmed deletion.
• Requires delete responses to confirm success: true and then confirms both resources return 404.
• Keeps credentials out of argv, repository config, and proof output; redacts echoed secrets from provider errors.
• Treats success: false Bash responses as failures even when an exit code is present.

Verification

Exact candidate: 23b6847ef464396ff11762d848d00424fb4a24b2

• go test -race ./internal/providers/orgo
• go test -race ./... during the final rewrite; the only later changes were additional passing tests and the reviewed Bash fail-closed fix
• Go core coverage: 90.1% (required: 90.0%)
• scripts/test-go-modules.sh
• repository script tests: 368/368
• Worker checks and tests: 760/760
• go vet ./...
• go build -trimpath -o bin/crabbox ./cmd/crabbox
• docs generation and provider metadata checks
• branch-wide AutoReview: clean, no accepted/actionable findings

Remaining live gate

Do not merge yet. The dedicated scripts/live-orgo-smoke.sh harness is ready to prove create, use, reuse, command-exit propagation, destroy, and zero residue on this exact candidate, but no Orgo credential is available in the approved environment or targeted 1Password records. No account or persistent key was created.

[clawsweeper]

Codex review: needs real behavior proof before merge. Reviewed July 3, 2026, 4:50 PM ET / 20:50 UTC.

Summary
The PR adds a built-in Orgo delegated-run provider with config/env support, docs and generated provider metadata, fake-API tests, and a guarded live-smoke harness.

Reproducibility: not applicable. This is a new provider feature, and current-main plus v0.34.0 inspection show Orgo support is absent rather than broken.

Review metrics: 2 noteworthy metrics.

• PR surface: 22 files, +3266/-1. The provider addition spans CLI config, provider implementation, docs, generated metadata, and live-smoke coverage.
• Hosted proof: 0 real Orgo lifecycle runs documented. The PR body and maintainer comments leave real hosted lifecycle proof as the remaining merge gate.

Root-cause cluster
Relationship: fixed_by_candidate
Canonical: #449
Summary: The open Orgo provider issue is the canonical feature request, and this PR is the current implementation candidate for that request.

Members:

• canonical: Add support orgo as provider #449 - The issue asks for Orgo provider support, links this PR as the implementation candidate, and remains open pending product acceptance and hosted proof.

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

Merge readiness
Overall: 🧂 unranked krab
Proof: 🧂 unranked krab
Patch quality: 🐚 platinum hermit
Result: blocked until real behavior proof from a real setup is added.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

• Post redacted terminal output or logs from scripts/live-orgo-smoke.sh showing create, run, reuse, exit propagation, cleanup, and no leaked secrets.
• Remove the release-owned CHANGELOG.md entry.

Proof guidance:

• [P1] Needs real behavior proof before merge: The PR body and maintainer comments explicitly say hosted Orgo lifecycle proof has not run; available evidence is fake-API/local validation only. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.

Risk before merge

• [P1] Hosted create, reuse, exit propagation, delete, and zero-residue behavior is covered by fake APIs but still unproven against real Orgo credentials, so an API-contract mismatch could leak billable resources or credential-bearing errors.
• [P1] This adds credentialed third-party provider and config surface as built-in core behavior, which still needs explicit maintainer product acceptance.
• [P1] The branch still edits release-owned CHANGELOG.md; release context should stay in the PR body or commit notes until release preparation.

Maintainer options:

1. Keep Hosted Lifecycle Proof As The Gate (recommended)
   Run scripts/live-orgo-smoke.sh with approved Orgo credentials and post redacted output showing create, reuse, exit propagation, delete, and no token leakage before merge.
2. Accept Maintainer-Owned Provider Risk
   Maintainers could explicitly land without hosted proof only if they are willing to own the unverified credential, API-contract, and cleanup boundary for the initial Orgo release.
3. Pause Built-In Orgo Until Sponsored
   If no approved Orgo credential or product sponsor is available, keep the linked issue open and pause this PR until that decision changes.

Next step before merge

• [P1] The remaining action is maintainer product acceptance plus real hosted proof; automation cannot supply the contributor’s Orgo credentials or runtime evidence.

Security
Cleared: No definite code-level secret-handling flaw was found; the remaining security-boundary concern is missing hosted Orgo lifecycle proof.

Review findings

• [P3] Remove the release-owned changelog entry — CHANGELOG.md:7

Review details

Best possible solution:

Land the built-in Orgo provider only after maintainers accept the product direction, redacted hosted lifecycle proof is posted, and the release-owned changelog edit is removed.

Do we have a high-confidence way to reproduce the issue?

Not applicable. This is a new provider feature, and current-main plus v0.34.0 inspection show Orgo support is absent rather than broken.

Is this the best way to solve the issue?

Unclear. The adapter shape matches Crabbox’s provider boundary, but built-in Orgo support still needs maintainer product acceptance, real hosted lifecycle proof, and removal of the release-owned changelog edit.

Full review comments:

• [P3] Remove the release-owned changelog entry — CHANGELOG.md:7
  This PR adds an Unreleased CHANGELOG.md line even though release notes are release-owned here and the PR body already carries the release-note context. Please remove this line and keep the user-visible summary in the PR body or commit notes for release prep.
  Confidence: 0.89

Overall correctness: patch is correct
Overall confidence: 0.78

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 62831c8972de.

Label changes

Label justifications:

• P2: A new hosted provider is a normal-priority feature with limited existing-user blast radius but meaningful credential and cleanup review surface.
• merge-risk: 🚨 security-boundary: Merging adds a credentialed HTTP provider that creates and deletes remote Orgo resources without hosted lifecycle proof yet.
• rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🐚 platinum hermit.
• status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: The PR body and maintainer comments explicitly say hosted Orgo lifecycle proof has not run; available evidence is fake-API/local validation only. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.

Evidence reviewed

What I checked:

• AGENTS.md policy read: Read the full target AGENTS.md; provider-neutral boundaries, secret handling, generated-output guidance, and release-owned changelog guidance apply to this provider review. (AGENTS.md:13, 62831c8972de)
• Current main lacks Orgo: Current main has no Orgo provider, config, docs page, env vars, or provider registration; repository search only found unrelated substrings such as forgotten/ForGOOS. (62831c8972de)
• Latest release lacks Orgo: The v0.34.0 tag contains no Orgo provider support; grep found only unrelated substrings, so the PR is not obsolete by release content. (ef898c27570a)
• Provider registration: The branch registers orgo with alias orgo-ai as a Linux delegated-run provider with coordinator disabled. (internal/providers/orgo/provider.go:17, 23b6847ef464)
• Credential and HTTP boundary: The branch resolves the Orgo API key from env/config rather than argv, requires HTTPS except loopback, sends Authorization headers, and redacts echoed API keys from HTTP error bodies. (internal/providers/orgo/client.go:110, 23b6847ef464)
• Resource ownership and cleanup: The branch binds claims to endpoint, owner, workspace, computer identity, and lease metadata, then verifies membership before deleting computers/workspaces and removing claims. (internal/providers/orgo/backend.go:451, 23b6847ef464)

Likely related people:

• steipete: Current history includes credential destination hardening and recent provider/release work, and this branch includes several Orgo hardening commits around credentials, cleanup, readiness, and capabilities. (role: recent credential-boundary and adjacent provider contributor; confidence: high; commits: c62fb939341d, ef898c27570a, 23b6847ef464; files: internal/cli/credential_provenance.go, internal/providers/orgo/backend.go, internal/providers/orgo/client.go)
• zozo123: Current main includes prior provider work by Yossi Eliaz, including OpenComputer, and the same GitHub account authored the Orgo proposal and initial branch work. (role: prior delegated provider implementer and Orgo proposer; confidence: high; commits: 3b92643ab361, 7575c39aa3ff, 03c40c6476f3; files: internal/providers/opencomputer, internal/providers/smolvm, internal/providers/orgo)
• vincentkoc: PR and issue comments identify Vincent Koc as carrying the validation/proof gate, and branch commits add API-key redaction and provider-matrix refresh work. (role: review and validation owner; confidence: high; commits: 6ae23eadbb46, 1a1942adb9cc, 6e88b11d105e; files: internal/providers/orgo/client.go, docs/providers/README.md, docs/providers/provider-metadata.json)
• coygeek: Current history shows several recent provider additions touching the same registration, docs metadata, and live-smoke patterns used by this PR. (role: recent adjacent provider contributor; confidence: medium; commits: 4003a3000972, 460e241d1b71, 878b370a5526; files: internal/providers/all/all.go, docs/providers/provider-metadata.json, scripts/live-smoke.sh)

What the crustacean ranks mean

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

[steipete]

@clawsweeper re-review

Rebased onto current main and fixed the review findings: provider and live-smoke readiness polling now wait for running state, terminal startup failures clean up resources, and provider capabilities satisfy current registry conformance. Exact head: 7e5624855596586ca947eed50906a82b64d31fbf.

[clawsweeper]

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

[zozo123]

@clawsweeper re-review

[vincentkoc]

@clawsweeper re-review

Updated #458 to current main and pushed head 5c9ff329cb5b2e79a57aa0031f34cde2b8c51289.

Validation now completed:

• GitHub CI is green: 6 successful, 0 failing, 0 pending on https://github.com/openclaw/crabbox/actions/runs/28075644227.
• Local validation passed: go test ./internal/providers/orgo ./internal/providers/all ./internal/cli ./cmd/crabbox, node --test scripts/live-smoke.test.js, provider matrix/docs checks, go vet ./..., go build -trimpath -o bin/crabbox ./cmd/crabbox, and full go test ./....
• Rebase conflicts were resolved by preserving current generated provider matrix state, regenerating it to 66 providers with Orgo included, and keeping both newer Morph live-smoke coverage and Orgo live-smoke coverage.

I am not merging this yet while status: 📣 needs proof remains. The remaining external proof is hosted Orgo lifecycle behavior with real credentials: create workspace/computer, wait to running, execute command, delete computer/workspace, and show no leaked token/output.

[clawsweeper]

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

[vincentkoc]

@clawsweeper re-review

Pushed maintainer fixes for the concrete security/release findings.

Head: 3de3cb8bf89f3d8e603f6c646c8c7cf1abae6d0e

Changes made:

• non-2xx Orgo HTTP response bodies are redacted with the configured API key before the error is surfaced
• added TestHTTPErrorRedactsAPIKeyFromResponseBody, covering both Bearer <key> and raw key echoes from a custom/upstream API response
• removed the release-owned CHANGELOG.md entry and kept release-note context in the PR body

Local validation passed on this head:

go test ./internal/providers/orgo
go test ./internal/providers/orgo ./internal/providers/all ./internal/cli ./cmd/crabbox
node --test scripts/live-smoke.test.js
node scripts/check-command-docs.mjs
node scripts/check-docs-links.mjs
go vet ./...
go build -trimpath -o bin/crabbox ./cmd/crabbox
git diff --check

Still not merging: hosted Orgo lifecycle proof remains blocked on paid-plan authorization, and status: 📣 needs proof / merge-risk: 🚨 security-boundary remain.

[clawsweeper]

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

[vincentkoc]

Public CI is now green on current head 3de3cb8bf89f3d8e603f6c646c8c7cf1abae6d0e: https://github.com/openclaw/crabbox/actions/runs/28084529432.

Still not merging: hosted Orgo lifecycle proof remains blocked on paid-plan authorization, and status: 📣 needs proof / merge-risk: 🚨 security-boundary remain.

[vincentkoc]

@clawsweeper re-review

Updated the PR body with the canonical summary, validation evidence, and remaining merge gate for current head. No code changes in this update.

Still not merging unless the live proof labels clear and the provider-specific proof/contract gate is satisfied.

[vincentkoc]

@clawsweeper re-review

Rebased Orgo onto current main and refreshed the generated provider matrix count.

Head: a13a41ac2543af91594e6d6e84f96792c6864d9f

Change made:

• regenerated provider docs metadata after rebase; current built-in surface now reports 67 providers

Local validation passed:

go test ./internal/providers/orgo ./internal/providers/all ./internal/cli ./cmd/crabbox
node --test scripts/live-smoke.test.js
node scripts/generate-provider-matrix.mjs --check
node scripts/check-command-docs.mjs
node scripts/check-docs-links.mjs
go vet ./...
go build -trimpath -o bin/crabbox ./cmd/crabbox
git diff --check

Public CI is green on this head: https://github.com/openclaw/crabbox/actions/runs/28103708184

Still not merging: hosted Orgo lifecycle proof remains blocked on paid-plan authorization, and status: 📣 needs proof / merge-risk: 🚨 security-boundary remain.

[clawsweeper]

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

[vincentkoc]

@clawsweeper re-review

Rebased Orgo onto current main after the Slurm and Coder provider landings and refreshed the provider matrix count.

Head: 8cb00c22c5297179e574940ebe2c142f1dc6b0c2

Change made:

• resolved provider matrix drift after the new Slurm and Coder providers landed; current built-in surface now reports 68 providers

Validation passed on the rebased head:

git diff --check
go test ./internal/providers/orgo ./internal/providers/all ./internal/cli ./cmd/crabbox
node --test scripts/live-smoke.test.js
node scripts/generate-provider-matrix.mjs --check
node scripts/check-command-docs.mjs
node scripts/check-docs-links.mjs

Still not merging: hosted Orgo lifecycle proof remains blocked on paid-plan authorization, and status: needs proof / security-boundary remain.

[clawsweeper]

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

[vincentkoc]

@clawsweeper re-review

Updated the PR body to current head 8cb00c22c5297179e574940ebe2c142f1dc6b0c2 and the current CI run: https://github.com/openclaw/crabbox/actions/runs/28111473550

No code changes in this update. The remaining gate is still hosted Orgo lifecycle proof with real credentials; there are no Orgo API credentials in this environment.

[vincentkoc]

@clawsweeper re-review

Current head 8cb00c22c5297179e574940ebe2c142f1dc6b0c2 now has green public CI: 8 successful, 0 failing, 0 pending on https://github.com/openclaw/crabbox/actions/runs/28111473550.

Additional local reproduction while checking the earlier pending jobs:

• goreleaser release --snapshot --clean --skip=publish passed locally in the feat: add Orgo provider #458 worktree.
• go test ./internal/cli -covermode=atomic -count=1 -v passed locally after investigating a transient coverage-run flake.

Still not merging: hosted Orgo lifecycle proof remains blocked by missing real Orgo credentials, and status: needs proof / security-boundary remain the merge gate.

[clawsweeper]

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.