feat(apps): opper apps — deploy and manage agents as managed apps#18
Merged
Conversation
New `opper apps` command group against the /v3/apps surface (Opper
Apps — agent source in, running app out; the platform UI is a viewer,
the CLI is the creation path):
opper apps list | get <name> | delete <name>
opper apps create [--name n] [--dir .|--repo <git-url> [--ref r]]
[--config json]
opper apps redeploy <name> --dir .
opper apps logs <name> # SSE tail
opper apps run <name> --input "…"
opper apps secrets list|set|delete <app> [KEY] [VALUE]
- create accepts a local directory (tarred with the system tar,
excluding .git/node_modules/__pycache__/.venv) or a git URL that is
shallow-cloned and deployed; --name is optional when the source's
opper.yaml manifest declares one.
- OpperApi gains postMultipart (FormData upload) and streamGet
(SSE-over-GET for logs), sharing the existing SSE parser.
- New INVALID_ARGUMENT error code (exit 8) for bad local input.
Verified live against the evroc deployment: list/get/run/secrets all
round-trip; `apps run hermes` answered through the new command.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
`opper apps shell <name>` opens a real PTY in the app's container over the app's /run/shell WebSocket (the in-pod ttyd, proxied by the wrapper), through the normal API-key-authed chain — no SSH, no cluster access. It puts stdin in raw mode so Ctrl-C/Ctrl-D/arrows reach the remote shell, forwards SIGWINCH as ttyd resize frames, and restores the terminal on exit. Uses the `ws` client (Node 20 floor has no global WebSocket). Verified against a ttyd-enabled image: connects, runs a command, streams output back. Needs the deploy-side terminal (opper#2954) and the task-api websocket proxy (opper#2955) deployed to work end to end. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
mattias-lundell
force-pushed
the
feat/apps
branch
from
July 1, 2026 08:14
99fc852 to
618a0e2
Compare
… dead deploy_token - create/redeploy gain --wait: poll the build to a terminal state and exit non-zero (DEPLOY_FAILED, exit 9) on failure so CI can gate on a green deploy - secrets set reads the value from --from-stdin / --from-file, keeping it off argv and out of shell history; the positional value still works - delete confirms interactively and refuses in a non-TTY without --yes - drop the deploy_token branch: neither deploy nor task-api ever returns it Verified live on prod (api.opper.ai) end-to-end with the hello-agent example: create -> secret via stdin -> redeploy --wait (building->running, exit 0) -> run -> delete --yes; delete without --yes refused (exit 8). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Thin wrapper over POST /v3/apps/<name>/run with naive {data}-shape output
and no streaming — create/get already print the invoke URL for curl/SDK.
Trims the surface; no dependency change.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the
opper appscommand group for Opper Apps (the deploy/Knative backend): agent source in, running app out, via task-api's/v3/appssurface.Highlights
--reposhallow-clones and deploys —opper apps create --repo https://github.com/org/agentjust works when the repo carries anopper.yaml.--nameis optional when the source'sopper.yamldeclaresname:(fly.io-style config-as-code);template:/cpu/memory/disk/timeout/envalso flow via the manifest.--waitpolls the build to a terminal state and exits non-zero (DEPLOY_FAILED, exit 9) if it fails, so pipelines can gate on a green deploy.secrets setreads the value from--from-stdin/--from-file, so it never lands in shell history orps.--yes.opper apps shellopens a real PTY in the running container over the same authed proxy (ttyd/WebSocket) — no SSH, no cluster access.postMultipart(FormData upload) +streamGet(SSE-over-GET); newINVALID_ARGUMENT(exit 8) andDEPLOY_FAILED(exit 9) error codes.Tested: 13 vitest cases for apps (full suite 382 green,
tscclean). Verified live end-to-end against prod (api.opper.ai) with thehello-agentexample: create → setOPPER_API_KEYvia--from-stdin→redeploy --wait(building→running, exit 0) → run (real LLM answer) →delete --yes;deletewithout--yescorrectly refused (exit 8).🤖 Generated with Claude Code