Deploy a bex App to the current Kubernetes cluster and verify it reaches Ready. Use when the user asks to deploy a render.yaml (or legacy bex.yml) or the sample app and validate the rollout end to end. Optional argument: path to render.yaml.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Deploy an App and verify it end-to-end. Use KUBECONFIG=infra/local/bex.kubeconfig if no other cluster is targeted.
Requires BEX_API_URL and BEX_API_TOKEN in the environment (scripts/app-apply.sh reads them and fails with set BEX_API_URL if unset — both are client-supplied, not in .env.example; BEX_API_PUBLIC_URL in .env.example is the unrelated backend DeployHook origin). BEX_API_TOKEN is the Hydra-issued Bearer token (API key minted via /v1/api-keys), not the removed static shared secret. Optional BEX_OWNER_ID, BEX_REPO, BEX_BRANCH narrow the deploy.
$ARGUMENTS is a path to a render.yaml (or legacy bex.yml alias — canonical is render.yaml, see scripts/app-apply.sh), apply it with DRY_RUN=1 bash scripts/app-apply.sh $ARGUMENTS first and show the generated App CR, then bash scripts/app-apply.sh $ARGUMENTS to deploy. If $ARGUMENTS is a directory, pass the directory — the script discovers render.yaml then bex.yml inside it. Otherwise apply the sample: kubectl apply -f examples/whoami-app.yaml.kubectl get apps.app.bex.co <name> -o jsonpath='{.status.phase} {.status.revision} {.status.url}' until phase is Ready (timeout ~3 minutes; on timeout, show kubectl describe apps.app.bex.co <name> and the operator logs kubectl -n bex-system logs deploy/bex-controller-manager --tail=50).status.url is set and resolvable, curl -fsS it (use --resolve/-k only if the local mock has no real DNS/TLS) and show the response status.kubectl get pods -l app.bex.co/app=<name> -o wide).No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Deploy a local checkout to a production Hetzner App using the manual image-import runbook. Use when the user asks to ship local working-tree code to a live bex App rather than deploy from remote Git. Arguments are the local repo path and app name.
The English summary is being prepared. Showing the original description.
Autonomously drain a `.pm` workstream — triage every open item (milestone or inbox-note task), then work it to done, park it in `blocked/`, or delete it as invalid, until the workstream has no open items left. Use when the user asks to "loop", drain, or clear a whole workstream's backlog (e.g. `/loopx w1`). Sequential, not interval-based; for a timed poll use /loop.
The English summary is being prepared. Showing the original description.
Create concise, syntax-verified Mermaid architecture diagrams. Use when the user asks to diagram a repository component, document, system, dependency flow, or supplied description in Mermaid.
The English summary is being prepared. Showing the original description.
Stand up or scale the local CAPD mock cluster and deploy the bex operator into it. Use when the user asks to create, inspect, or resize the repository's local development cluster. Optional argument: scale N.
The English summary is being prepared. Showing the original description.
Inspect and maintain the repository's .pm workstreams, inbox notes, milestones, and tasks. Use when the user asks for PM board status or requests a supported board mutation such as creating, promoting, adding, or completing work.
The English summary is being prepared. Showing the original description.
Analyze and decompose a product topic into a text-only proposal for the repository's .pm board. Use when the user wants to pressure-test scope, size milestones, identify dependencies, or prepare exact PM board commands without writing board files.
The English summary is being prepared. Showing the original description.