Oompa Cloud efficiency
Use Codex Cloud as a bounded repository-worker lane. Keep the active root and
integration owner local on the caller-selected model. The official CLI creates
a separate Cloud task; it does not convert or move this active task.
Choose the mode
- Install or update this machine: run
bun run scripts/bootstrap.ts --apply from this skill directory, then repeat with --check. Start a new
Codex task after plugin installation or bootstrap so the refreshed skill and
global guidance are loaded.
- Qualify a task: classify every execution and final-proof requirement,
then run
oompa-cloud-route with the exact repository root, intent, model
policy, environment profile, owner, and any local-only requirements. Use
--online immediately before dispatch to prove that the remote branch still
equals the local commit.
- Create or maintain an environment: read
environment profiles. Environment
creation is a user-visible Codex settings operation, not a private API call.
- Dispatch, monitor, or integrate: read
Cloud operations. Use only documented
codex cloud commands and the installed privacy launch guard.
- Adopt repository guidance: use
oompa-cloud-adoption --check --root ABSOLUTE_REPOSITORY or the explicit --apply form. It edits only this
plugin's managed block in a root AGENTS.md.
- Diagnose this machine: run
oompa-cloud-efficiency or
oompa-cloud-efficiency --json. The doctor is local and read-only.
Run scripts directly from the installed skill directory when convenience
commands have not been bootstrapped yet.
This plugin was previously named hra-cloud-efficiency. bootstrap.ts --apply
migrates that installation in place: it replaces exactly one well-formed
hra-cloud-efficiency managed block in global AGENTS.md with the current
block, retargets command links that point at the previous plugin, and installs
hra-cloud-adoption, hra-cloud-efficiency, and hra-cloud-exec
compatibility links beside the oompa-* commands. --check requires those
links only on a machine that already has one, and both the bootstrap and
oompa-cloud-adoption refuse a file that carries legacy and current markers
together.
Route by hard exclusions first
Keep the task local when its execution needs any of the following:
- an existing signed-in browser profile, extension, passkey, cookie store, or
interactive OAuth flow;
- npm 2FA, device pairing, Keychain, protected Messages or Contacts, Full Disk
Access, private SQLite, local archives, or other private local state;
- macOS, Apple Silicon, Xcode, native capture, audio hardware, signing,
notarization, or a user-visible desktop acceptance step;
- a secret during the agent phase, provider mutation, production publication,
deployment, release, authoritative production readback, or agent-phase
network access;
- uncommitted or unpushed inputs, a sibling checkout, or a mutable branch owned
by another worker;
- exact preservation of the selected model and reasoning effort.
The route command classifies these hard exclusions before inspecting Git. A
valid local decision therefore remains available for a dirty, detached, or
private-only working context and does not require a nominal Cloud source.
Use a hybrid route when implementation and focused Linux validation are
portable but one final proof needs a local authenticated browser, provider,
Mac, signing, or production lane. The Cloud worker must not perform that final
effect.
Cloud is eligible when the task starts from an exact pushed branch, is
Linux-container compatible, has no execution exclusion, is independent of
another worker's mutable files, and benefits from isolated compute, disk, or
background progress. Auth-free headless Chromium is eligible when its browser
and system dependencies are pinned in the environment.
Preserve model and ownership truth
- A local model selection does not prove the Cloud worker's hosted model or
reasoning effort. Require the route gate's explicit
cloud-default-ok
policy before dispatch. If exact model identity matters, stay local or use a
compatible connected host.
- Keep the root coordinator and integration owner on the caller-selected
model. Record each remote lane as
cloud-default, not as the local model.
- Give every editable Cloud task one unique branch and one owner. Never allow
concurrent writers on a branch or convergence file.
- Default to one Cloud attempt. Use multiple attempts only for a bounded,
high-value ambiguous task because every attempt consumes allowance and
creates additional review work.
Qualify the exact source
For an editable task, create and push a unique non-default branch before
qualification. For a read-only smoke task, the governed default branch is
allowed.
For Cloud and hybrid candidates, the route gate rejects a dirty or detached
tree, local and tracking-ref drift, hidden index flags, populated Git links,
replacement refs, legacy grafts, semantic Git environment overrides,
unsupported remotes, and editable work on the repository's actual default
branch. Its default check is local. --online additionally reads the exact
fully qualified remote branch and requires the same commit.
The report contains safe Git identity and routing facts only. It does not store
the local path, prompt, environment ID, provider output, or account data.
Example:
umask 077
oompa-cloud-route \
--root /absolute/repository \
--intent edit \
--owner feature-owner \
--profile portable-bun \
--model-policy cloud-default-ok \
--environment configured-environment-id \
--environment-repository hraness/repository \
--online \
--json > /absolute/private/dispatch-ready-route.json
Add --needs for an execution requirement and --final-needs for a final
local proof. A valid local decision is not an error. Do not omit a known
requirement to obtain a Cloud decision. In particular, --needs agent-network
means the worker itself requires runtime network and must stay local;
--final-needs agent-network means the portable worker can stay offline while
the local integration owner performs a later network-dependent proof.
Dispatch and integrate
Build a bounded dispatch packet with the route report's repository slug,
branch, exact commit, intent, owner, profile, scope, acceptance criteria,
focused commands, forbidden operations, and required evidence. State that the
Cloud worker may not merge, release, deploy, mutate a provider, or weaken a
gate.
Use oompa-cloud-exec to launch the official CLI. It consumes the private
dispatch-ready JSON route report rather than retyped Git identity, resolves its
explicit branch, prepends a mandatory repository, branch, commit, and clean
status preflight, feeds the result through stdin, runs the child in a newly
created private temporary directory, passes only reviewed Codex home, user,
path, locale, terminal, temporary-directory, XDG, and certificate variables,
forwards output and signals, and removes that exact scratch directory. Ambient
API keys, package credentials, and repository-specific environment values do
not enter the CLI process. The environment-repository value is an operator
attestation from visible Codex settings because the CLI cannot inspect that
binding; the worker preflight is the fail-closed backstop. The guard does not
parse provider protocols, store a receipt, or retry. If it is unavailable,
reproduce that privacy boundary explicitly and never run the current alpha
Cloud CLI from a repository directory.
A nonzero result after submission may be ambiguous. Never retry automatically.
Reconcile through codex cloud list --json or the visible Cloud UI before any
new task creation.
One owner monitors the task. Do not hold oompa-host-run or another local
compute lease while waiting. Prefer a reviewed pull request. Never run raw
codex cloud apply in an authoritative integration checkout because the
current alpha CLI writes identifier-bearing diagnostics in its working
directory. If an apply is necessary, use the private disposable exact-source
flow in Cloud operations, then integrate the
reviewed Git change through normal ownership. Run the repository's focused and
final gates after convergence. Cloud evidence never replaces a required final
integration, merge, release, deployment, or production-verification receipt.
Keep adjacent systems separate
- Use
$oompa-local-efficiency for host scheduling, local capability lanes,
validation receipts, worktree cleanup, CI ref audits, and local throughput
reports.
- Use repository-owned CI, merge queues, release tools, and deployment tools
without weakening their gates.
- Oompa hosted sync, Convex identity, and remote Oompa session authority are
separate product systems. This skill does not configure or operate them.
Cloud usage shares plan allowance with local Codex usage. Prefer tasks whose
resource or parallelism benefit justifies the hosted-model cost. Recheck the
official Codex documentation when model, pricing, environment, or CLI behavior
affects a decision.
1---2name: oompa-cloud-efficiency3description: >-4 Qualify, dispatch, monitor, and integrate bounded Codex Cloud repository5 workers for Hraness projects while preserving the caller-selected local6 coordinator, exact pushed Git state, privacy boundaries, and repository7 final gates. Use for Codex Cloud routing, environment readiness, hybrid8 local-and-Cloud validation, or installing the shared Cloud routing baseline.9 Do not use for Oompa hosted or Convex operations, local scheduling or cleanup,10 authenticated browsers, 2FA, Mac-native work, releases or deployments,11 agent-phase secrets, private local data, or exact model-and-effort12 preservation.13metadata:14 source: https://skillmd.com/skills/hraness/oompa-cloud-efficiency15---1617# Oompa Cloud efficiency1819Use Codex Cloud as a bounded repository-worker lane. Keep the active root and20integration owner local on the caller-selected model. The official CLI creates21a separate Cloud task; it does not convert or move this active task.2223## Choose the mode2425- **Install or update this machine:** run `bun run scripts/bootstrap.ts26 --apply` from this skill directory, then repeat with `--check`. Start a new27 Codex task after plugin installation or bootstrap so the refreshed skill and28 global guidance are loaded.29- **Qualify a task:** classify every execution and final-proof requirement,30 then run `oompa-cloud-route` with the exact repository root, intent, model31 policy, environment profile, owner, and any local-only requirements. Use32 `--online` immediately before dispatch to prove that the remote branch still33 equals the local commit.34- **Create or maintain an environment:** read35 [environment profiles](references/environment-profiles.md). Environment36 creation is a user-visible Codex settings operation, not a private API call.37- **Dispatch, monitor, or integrate:** read38 [Cloud operations](references/cloud-operations.md). Use only documented39 `codex cloud` commands and the installed privacy launch guard.40- **Adopt repository guidance:** use `oompa-cloud-adoption --check --root41 ABSOLUTE_REPOSITORY` or the explicit `--apply` form. It edits only this42 plugin's managed block in a root `AGENTS.md`.43- **Diagnose this machine:** run `oompa-cloud-efficiency` or44 `oompa-cloud-efficiency --json`. The doctor is local and read-only.4546Run scripts directly from the installed skill directory when convenience47commands have not been bootstrapped yet.4849This plugin was previously named `hra-cloud-efficiency`. `bootstrap.ts --apply`50migrates that installation in place: it replaces exactly one well-formed51`hra-cloud-efficiency` managed block in global `AGENTS.md` with the current52block, retargets command links that point at the previous plugin, and installs53`hra-cloud-adoption`, `hra-cloud-efficiency`, and `hra-cloud-exec`54compatibility links beside the `oompa-*` commands. `--check` requires those55links only on a machine that already has one, and both the bootstrap and56`oompa-cloud-adoption` refuse a file that carries legacy and current markers57together.5859## Route by hard exclusions first6061Keep the task local when its execution needs any of the following:6263- an existing signed-in browser profile, extension, passkey, cookie store, or64 interactive OAuth flow;65- npm 2FA, device pairing, Keychain, protected Messages or Contacts, Full Disk66 Access, private SQLite, local archives, or other private local state;67- macOS, Apple Silicon, Xcode, native capture, audio hardware, signing,68 notarization, or a user-visible desktop acceptance step;69- a secret during the agent phase, provider mutation, production publication,70 deployment, release, authoritative production readback, or agent-phase71 network access;72- uncommitted or unpushed inputs, a sibling checkout, or a mutable branch owned73 by another worker;74- exact preservation of the selected model and reasoning effort.7576The route command classifies these hard exclusions before inspecting Git. A77valid local decision therefore remains available for a dirty, detached, or78private-only working context and does not require a nominal Cloud source.7980Use a hybrid route when implementation and focused Linux validation are81portable but one final proof needs a local authenticated browser, provider,82Mac, signing, or production lane. The Cloud worker must not perform that final83effect.8485Cloud is eligible when the task starts from an exact pushed branch, is86Linux-container compatible, has no execution exclusion, is independent of87another worker's mutable files, and benefits from isolated compute, disk, or88background progress. Auth-free headless Chromium is eligible when its browser89and system dependencies are pinned in the environment.9091## Preserve model and ownership truth9293- A local model selection does not prove the Cloud worker's hosted model or94 reasoning effort. Require the route gate's explicit `cloud-default-ok`95 policy before dispatch. If exact model identity matters, stay local or use a96 compatible connected host.97- Keep the root coordinator and integration owner on the caller-selected98 model. Record each remote lane as `cloud-default`, not as the local model.99- Give every editable Cloud task one unique branch and one owner. Never allow100 concurrent writers on a branch or convergence file.101- Default to one Cloud attempt. Use multiple attempts only for a bounded,102 high-value ambiguous task because every attempt consumes allowance and103 creates additional review work.104105## Qualify the exact source106107For an editable task, create and push a unique non-default branch before108qualification. For a read-only smoke task, the governed default branch is109allowed.110111For Cloud and hybrid candidates, the route gate rejects a dirty or detached112tree, local and tracking-ref drift, hidden index flags, populated Git links,113replacement refs, legacy grafts, semantic Git environment overrides,114unsupported remotes, and editable work on the repository's actual default115branch. Its default check is local. `--online` additionally reads the exact116fully qualified remote branch and requires the same commit.117The report contains safe Git identity and routing facts only. It does not store118the local path, prompt, environment ID, provider output, or account data.119120Example:121122```sh123umask 077124oompa-cloud-route \125 --root /absolute/repository \126 --intent edit \127 --owner feature-owner \128 --profile portable-bun \129 --model-policy cloud-default-ok \130 --environment configured-environment-id \131 --environment-repository hraness/repository \132 --online \133 --json > /absolute/private/dispatch-ready-route.json134```135136Add `--needs` for an execution requirement and `--final-needs` for a final137local proof. A valid `local` decision is not an error. Do not omit a known138requirement to obtain a Cloud decision. In particular, `--needs agent-network`139means the worker itself requires runtime network and must stay local;140`--final-needs agent-network` means the portable worker can stay offline while141the local integration owner performs a later network-dependent proof.142143## Dispatch and integrate144145Build a bounded dispatch packet with the route report's repository slug,146branch, exact commit, intent, owner, profile, scope, acceptance criteria,147focused commands, forbidden operations, and required evidence. State that the148Cloud worker may not merge, release, deploy, mutate a provider, or weaken a149gate.150151Use `oompa-cloud-exec` to launch the official CLI. It consumes the private152dispatch-ready JSON route report rather than retyped Git identity, resolves its153explicit branch, prepends a mandatory repository, branch, commit, and clean154status preflight, feeds the result through stdin, runs the child in a newly155created private temporary directory, passes only reviewed Codex home, user,156path, locale, terminal, temporary-directory, XDG, and certificate variables,157forwards output and signals, and removes that exact scratch directory. Ambient158API keys, package credentials, and repository-specific environment values do159not enter the CLI process. The environment-repository value is an operator160attestation from visible Codex settings because the CLI cannot inspect that161binding; the worker preflight is the fail-closed backstop. The guard does not162parse provider protocols, store a receipt, or retry. If it is unavailable,163reproduce that privacy boundary explicitly and never run the current alpha164Cloud CLI from a repository directory.165166A nonzero result after submission may be ambiguous. Never retry automatically.167Reconcile through `codex cloud list --json` or the visible Cloud UI before any168new task creation.169170One owner monitors the task. Do not hold `oompa-host-run` or another local171compute lease while waiting. Prefer a reviewed pull request. Never run raw172`codex cloud apply` in an authoritative integration checkout because the173current alpha CLI writes identifier-bearing diagnostics in its working174directory. If an apply is necessary, use the private disposable exact-source175flow in [Cloud operations](references/cloud-operations.md), then integrate the176reviewed Git change through normal ownership. Run the repository's focused and177final gates after convergence. Cloud evidence never replaces a required final178integration, merge, release, deployment, or production-verification receipt.179180## Keep adjacent systems separate181182- Use `$oompa-local-efficiency` for host scheduling, local capability lanes,183 validation receipts, worktree cleanup, CI ref audits, and local throughput184 reports.185- Use repository-owned CI, merge queues, release tools, and deployment tools186 without weakening their gates.187- Oompa hosted sync, Convex identity, and remote Oompa session authority are188 separate product systems. This skill does not configure or operate them.189190Cloud usage shares plan allowance with local Codex usage. Prefer tasks whose191resource or parallelism benefit justifies the hosted-model cost. Recheck the192official Codex documentation when model, pricing, environment, or CLI behavior193affects a decision.