Run OpenBot as one container, and give a Bot a shell - #62

Merged

davidmckayv merged 21 commits into

mainfrom

feat/a7-control-plane

Aug 20, 2026

Commits on Aug 20, 2026

Give each Bot a computer on Daytona when an API key is configured
mu-hashmi
committed
739570c
Keep Daytona reset monotonic across delayed sandbox indexes
mu-hashmi
committed
bc70631
Retry Daytona resets after transient deletion failures
mu-hashmi
committed
d74049c
Make Daytona computer lifecycle reads non-provisioning and bounded
mu-hashmi
committed
a10ad1e
Keep computer status reads renderable during supervisor failures
mu-hashmi
committed
6fa57d8
Check the address a supervisor hands back before calling it
davidmckayv
committed
0d24f4d
Tell OpenBot traffic apart in the analytics that already go
davidmckayv
committed
3e02bfb
Unify computer backends behind a deep provider and single gateway module
mu-hashmi
committed
e8b291b
Make computer providers honest and race-safe
mu-hashmi
committed
5124bfd
merge: resolve configuration and dependency conflicts with origin/main
mu-hashmi
committed
325ae72
Give a Bot a shell, and let Chromium sandbox itself where the host allows
davidmckayv
committed
3753e56
Run the whole thing as one container, with Postgres as a choice
davidmckayv
committed
5ce3522
Merge: put a provider seam under the computer
davidmckayv
committed
35ea202
Check the address a provider hands back before calling it
davidmckayv
committed
1d38374
Keep a changelog, and ask a PR to add to it
davidmckayv
committed
a5e1a3f
Say what a Bot's shell can do, and show the command it ran
davidmckayv
committed
4ee0b99
Say that a rule can match on the command
davidmckayv
committed
cd55f47
Stop the chat dying silently on a deployment without TLS
davidmckayv
committed
0a4feea
Merge main: take the one client, keep the provider seam
davidmckayv
committed
e26e2c5
Merge: keep both the minted thread and the one client
davidmckayv
committed
14de830
Use a neutral host in the computer address test
davidmckayv
committed
c85db03

Navigation Menu

Uh oh!

Run OpenBot as one container, and give a Bot a shell - #62

Run OpenBot as one container, and give a Bot a shell#62
davidmckayv merged 21 commits into
mainfrom
feat/a7-control-plane

Commits on Aug 20, 2026

Give each Bot a computer on Daytona when an API key is configured

Keep Daytona reset monotonic across delayed sandbox indexes

Retry Daytona resets after transient deletion failures

Make Daytona computer lifecycle reads non-provisioning and bounded

Keep computer status reads renderable during supervisor failures

Check the address a supervisor hands back before calling it

Tell OpenBot traffic apart in the analytics that already go

Unify computer backends behind a deep provider and single gateway module

Make computer providers honest and race-safe

merge: resolve configuration and dependency conflicts with origin/main

Give a Bot a shell, and let Chromium sandbox itself where the host allows

Run the whole thing as one container, with Postgres as a choice

Merge: put a provider seam under the computer

Check the address a provider hands back before calling it

Keep a changelog, and ask a PR to add to it

Say what a Bot's shell can do, and show the command it ran

Say that a rule can match on the command

Stop the chat dying silently on a deployment without TLS

Merge main: take the one client, keep the provider seam

Merge: keep both the minted thread and the one client

Use a neutral host in the computer address test