Skip to content

Run the server from the published OpenBot images - #1530

Merged
davidmckayv merged 13 commits into
mainfrom
run-server-from-published-images
Nov 13, 2026
Merged

davidmckayv merged 13 commits into
mainfrom
run-server-from-published-images

Conversation

@davidmckayv

@davidmckayv davidmckayv commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

The server, routine worker, migrations, computer and supervisor now run from the published OpenBot images. Local start, CI and Desktop's local build pull them by one tag instead of building them from this tree. The app, Desktop, mobile, the Recorder, shared/ and the Bot harnesses are built and tested here as before.

Clone, follow the quick start, run bash scripts/start.sh: it pulls the images that match the checkout, and nothing else is built or needed for them.

The one tag

backend-images.env sets OPENBOT_BACKEND_TAG:

  • main on the main branch: the images built from main. It moves with every build.
  • The release's version in a release (v1.0.3 in the v1.0.3 tag). It never moves.

scripts/start.sh, CI, images.yml and desktop/scripts/local-build.sh all read it. start.sh fetches the images at the tag on every start, so a checkout of main runs the build that is current now; offline, or with IMAGE_PULL_POLICY=never, it uses the copies already on the machine. An OPENBOT_BACKEND_TAG in the environment or .env runs another build. SERVER_IMAGE, COMPUTER_IMAGE and SUPERVISOR_IMAGE still win over the tag, so Desktop's digest pins are unchanged.

Releases

  • The release PR pins backend-images.env to its version, like package.json and the Cargo files, and its checklist asks that the images are published at that version before it merges. The release-files checks accept a change to the tag line and nothing else in the file.
  • After a stable release, the publish workflow opens a PR that puts main back. A final's merge-back keeps main's own line, as it already keeps main's Intelligence CLI choice.
  • images.yml pins the server, computer, supervisor and all-in-one images at the tag by digest in container-images.json, after checking the three a laptop runs carry amd64 and arm64 (the all-in-one image is amd64, as before).

Removed from this tree

server/, worker/, toolkit/, supervisor/, agent-computer/, charts/openbot/, the root Dockerfile and docker/, and the scripts that only built or checked them: typecheck-tests.ts, test-server-sharded.ts, mutation-register*, check-rendered-chart.ts, check-new-values-keys.ts and chart-reuse-values.ts. .github/published-images.json lists only the Bot and harness images.

What each file that used server code became

File Now
scripts/generate-app-config.ts Rewritten: reads tenant.id and tenant.product_name from the tenant package's brand.yaml
scripts/setup-learning.ts, self-hosted-learning.ts, local-intelligence-cli.ts, setup-composio.ts Rewritten imports: CLI and Intelligence helpers in scripts/copilotkit-cli.ts, learning-container.ts, learning-key.ts
scripts/composio-smoke.ts Removed: bun run composio:smoke runs the server image's openbot composio-smoke (scripts/composio-smoke.sh)
scripts/start-local-chrome-computer.ts Removed: the personal edition's own browser shows in the page, as in OpenBot Desktop
scripts/start.sh Rewritten: pulls the images at the tag, runs the server and worker as Compose services with .env plus the run's environment (scripts/server-env.ts), and the app with Vite
scripts/stop.sh Stops the containers through Compose and never touches a container engine's port forwarder
scripts/update-local.ts Host updates migrate through the image's migrate service
scripts/release-prepare.ts Pins backend-images.env to the release; no chart appVersion to move
desktop/scripts/validate-telemetry.ts Removed: it ran the server's runtime
desktop/scripts/local-build.sh Builds the harness from HEAD and pins the server, computer, supervisor and all-in-one images by the digest of the tag
tests/workspace.test.ts Rewritten for the app, shared and extension workspaces
tests/personal-edition-env.test.ts Rewritten: the case that loaded the server's config is removed
tests/compose.test.ts, tests/no-*-in-user-copy.test.ts, app/tests/update-banner.test.tsx Rewritten for the files in this tree
tests/chart-*.test.ts, tests/promote-kubernetes-helm.test.ts, tests/s6-migrate-waits-for-postgres.test.ts Removed: they rendered the chart or the all-in-one image
App tests with server fixtures (arcade-*, admin-network-describe, key-only-apps-directory) Rewritten: the recorded fixtures moved to app/tests/fixtures/
brokered-account-row, connection-fields, bot-apps-empty-personal Rewritten: the server's published values are written out
agent-api-path, bots-api-today, bot-setup, bot-your-skills-personal, app-access-card-connect-before-tools, skins-opendots-frame, route-long-message, permissions-describe, setup-checklist-editions, boundaries-templates, approval-rule-example, agent-langgraph/tests/google-oauth-proxy Removed: they ran server route handlers or server modules in process
The test preload tests/support/network-guard.ts, with its test, and tests/bunfig-preload.test.ts

CI

  • Dropped: server types, the deployables' types, the computer's real-browser tests, chart lint and render, migrations, the all-in-one image job, and the Postgres service for the shards.
  • Kept: format, lint, types, mobile, the app's real-browser tests, the sharded suite, startup, Python harnesses, build and component Dockerfiles.
  • images.yml builds only the Bot and harness images. internal-build.yml and publish-release.yml get the pinned server images through it. The release no longer packages a chart from this tree.
  • Internal build takes a backend_tag input, main by default, so installers can pin main, a version or a test-<date>-<run> tag.

Also

  • On a fresh clone Docker Desktop could refuse the server's container with "bind source path does not exist" for .openbot, a folder that was there. start.sh now shows Docker the folder with a plain bind and starts the server again; any other failure still stops at once.
  • The account row cut a build's version to "main-2…". The version now shows in full in the default sidebar, the OpenDots sidebar and its account menu, and the name gives way. A real-browser test measures it.

Testing

  • bun install and bun install --frozen-lockfile on Bun 1.4.3.
  • bun run format:check, bun run lint, bun run typecheck and the whole suite.
  • A fresh clone in a new directory with its own Compose project and ports: bash scripts/start.sh, the app in a browser, a Bot's answer.

@davidmckayv
davidmckayv force-pushed the run-server-from-published-images branch 5 times, most recently from bcf0e5f to fe2cc05 Compare November 13, 2026 01:47
@davidmckayv
davidmckayv marked this pull request as ready for review November 13, 2026 02:01
@davidmckayv
davidmckayv force-pushed the run-server-from-published-images branch 5 times, most recently from a503f0d to ec4c1fb Compare November 13, 2026 18:07
Local start, CI and Desktop's local build now pull the OpenBot server, worker, migrations,
computer and supervisor images at one tag, OPENBOT_BACKEND_TAG in backend-images.env, instead of
building them from this tree. The app, Desktop, mobile, the Recorder, the shared modules and the
Bot harnesses are built and tested here as before.

- docker-compose.yml names ghcr.io/copilotkit/openbot-server, -agent-computer and -supervisor at
  that tag, pulled when missing. The image variables still win, so Desktop's digest pins are
  unchanged, and a Compose run without the tag still reads the file.
- scripts/start.sh runs the server and the routine worker as Compose services, hands the server
  .env with the run's environment on top (scripts/server-env.ts), gives it this machine's
  addresses as a container reaches them, and keeps serving the app from the checkout with Vite.
  A server and worker an earlier start left on the host are stopped first. stop.sh stops the
  containers through Compose and never a container engine's port forwarder.
- The app's build config is read from the tenant package's brand.yaml directly.
- The Learning and Composio setup helpers drive the CopilotKit CLI and Intelligence's API from
  scripts/ (copilotkit-cli.ts, learning-container.ts, learning-key.ts).
- `bun run composio:smoke` runs the server image's `openbot composio-smoke`.
- CI drops the jobs for code it no longer builds, keeps every client check, and adds an `end to
  end` job: the core loop journey in a real browser against a fresh stack from the published
  images, with aimock answering every model call.
- images.yml builds only the Bot and harness images and pins the server, computer, supervisor and
  all-in-one images in container-images.json by the digest their tag names. The release no longer
  packages a chart from this tree.
- Tests that imported server code read recorded fixtures or the values the server publishes.
These carry the server half of #1524 and #1531.

The desktop's two cross-writer lock tests take the server's own lock as their other writer, which
now runs in the server image, so they are ignored here and say why. The release rerun tests package
a chart with helm and archive a tree more than once, which takes longer than five seconds on a
shared runner.
These dial an MCP server added at an admitted loopback address on this machine, as they do an agent.

The end-to-end run reads the server's log from its container in the new conversation journeys too,
and sets the private-host allowance a local stack needs rather than leaving it to .env.
The end-to-end journeys stay in e2e/ and run on a developer's machine with
`bun run test:e2e`. CI no longer runs them, so `verify` no longer waits on
them and no repository secret is needed.
A checkout of a release should run the server, computer and supervisor
images of that release, and a checkout of main the images built from main.

- The release PR pins backend-images.env to the release's version, like
  package.json and the Cargo files. The release-files checks accept a change
  to that one line and nothing else in the file, in place of the chart's
  appVersion, which this tree no longer carries.
- After a stable release, the publish workflow opens a PR that puts main's
  own line back. A final's merge-back keeps main's line, as it already keeps
  main's Intelligence CLI choice.
- scripts/start.sh fetches the images at the tag before it starts anything.
  Compose's `missing` policy keeps any copy already on the machine, which for
  a tag that moves would be an old build. Offline, or with
  IMAGE_PULL_POLICY=never, it uses the copies it has.
- The release PR's checklist asks that the images are published at the
  version before it merges.
On the main branch the server, computer and supervisor images are the ones built from main, at the tag that moves with every build. scripts/start.sh fetches it on every start, and a release pins its own version in place of it.
This tree no longer builds the all-in-one image, so the deployment page says it is published and a deployment pulls it.
On a fresh clone, the first `bash scripts/start.sh` stopped at the server
with "bind source path does not exist" for `.openbot`, a folder that was
there. Compose mounts it strictly (create_host_path: false), and Docker
Desktop's view of a folder in a checkout made where another was deleted can
be stale; waiting does not put it right, and a plain `-v` bind of the folder
does. On that one refusal start.sh now makes such a bind and starts the
server again. Any other failure to start the server still stops at once.
Internal build takes a `backend_tag` input, `main` by default, and pins the
server, computer, supervisor and all-in-one images at that tag by digest
into the installers: `main`, a version such as v1.0.3, or a
test-<date>-<run> tag, so a build can be tried on Mac and Windows before it
merges. images.yml takes the same input and keeps reading backend-images.env
when it is empty, which is what a release does.
The account row read "main-2…": the name and the version shared it 4 to 1,
and the version was cut short to fit its fifth. A release's "v1.0.2" fits
that at the sidebar's default width, but a build's main-<date>-<run>,
test-<date>-<run> or internal-<commit> does not, and at the narrowest
sidebar not even "v1.0.2" did. The version is now as wide as its words
everywhere it shows (the default sidebar, the OpenDots sidebar and the
OpenDots account menu), and the name is what gets cut short. A real-browser
test measures the row at 340px and 220px.
This tree no longer carries the end-to-end suite, so backend-images.env and docker-compose.yml no longer list it among what reads OPENBOT_BACKEND_TAG.
@davidmckayv
davidmckayv force-pushed the run-server-from-published-images branch from ec4c1fb to 1bbd027 Compare November 13, 2026 18:52
The root no longer has @playwright/test, so a bare `bunx playwright install` fetched the newest Playwright and its Chromium, a different build from the one the root's playwright-core 1.62.1 launches, and every app browser test failed to start. The job installs through playwright-core itself.
@davidmckayv
davidmckayv merged commit f71b0f4 into main Nov 13, 2026
28 checks passed
@davidmckayv
davidmckayv deleted the run-server-from-published-images branch November 13, 2026 19:46
jerelvelarde added a commit to jerelvelarde/openbot that referenced this pull request Nov 17, 2026
… API spec

main moved the server out of this repository (CopilotKit#1530) and moved the app onto the generated v2 client.
The server half of the star prompt goes with the server. What stays here is its contract:
`starPromptAnswered` on the preferences (with a default, as every preference has), `starPrompt` on
the deployment, and POST /star-prompt-events with its StarPromptEvent body, beside app-errors. The
app reads and writes all three through the generated client.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant