You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Been daily driving BB the last 3 weeks and using the web app (through Tailscale on a home server) on my phone + laptop has become my main way to drive agents. It's working great so far! thanks for the amazing work
Reacted by Sawyer Hood, Fábio Pedrosa and Jeremiah Harvey
I'm clearly in need of this feature because I run 3 bb's at a time lol.
Question for @Git-on-my-level / @georgecollier-nqu / @jshph. How would you expect to "connect" your hosts together. I think the most natural thing is you could be using the desktop / local version and add your remotes there. The issue is that one of the servers has to be the "primary one" ex the one that you access from your phone / computer. This one should also be responsible for owning all of the automations / config / plugins (in the future). What is odd that this should probably be the remote one!
Curious if you all have opinions. My current thought is something like this:
In the desktop app add the ability in the UI to switch the url it points to (you can point it to the remote)
You can add multiple ssh hosts and they will all be "targets" when you make a thread.
This solves my pain of I can use the desktop app on my main laptop while the ui points to my headless machine and I can add my other computers as targets.
Targets are a great concept -- question of repos getting out of date with each other is something to think thru though (but promising if done well). If i'm iterating on my VPS because I'm mobile, how does my laptop's BB (local) inherit the changes? What tree of threads is shown in the project folder -- remote or local?
That said I also run several BBs (have an ios home screen to both laptop and vps too). I think it's fine for now...
+1 on this! If you take a look at https://multica.ai, they solve this problem and you can initialize a background daemon per machine. They have the main interface hosted themselves and you can easily switch between workspaces and machine-served agents (I use this right now). There's quite a bit in their docs to take from it and you can self-host all of it yourself. Perhaps BB can take a similar approach here?
This is very similar to how bb is currently set up under the hood (we have a server and daemon). I think we just need to figure out the UX. But maybe this makes the most sense where if you have an always on dev box host the server there and all of your other machines become daemons.
Yeah a hosted version would also be so good. We gotta add that.
I think you should let the user pick a primary "gateway" or whatever, it can centralized credentials, automations, etc...
Then all UIs are just clients, but you should probably let each UI cache creds locally during runtime to reduce latency and dependence on the gateway, in case there is packet loss or whatever, don't want to stream all LLM traffic through the gateway. Each UI can show itself as the main workspace but support remote bb connections (via ssh or something), or you can centralize UI configs so that all UIs connected to the same gateway get the same remote connections or something out of the box
Wait @harveyfullstack open up a PR for this! The ui looks pretty clean. I started on this here: #510, but I mainly did infra and no ui (this PR also adds a bb connect service so you can connect sans tailscale if you want). But your ui looks like a good staring point to iterate under an experiments flag.
How would you expect to "connect" your hosts together. I think the most natural thing is you could be using the desktop / local version and add your remotes there.
Yeah we'd add via SSH.
But we need the nuts and bolts included e.g:
when i click a file hyperlink, it should open it from the VPS
diffs etc should all work
I feel like once you start having to connect remotes, you do need some kind of account system that lets you just reuse the same account + config on desktop/mobile whatever. Maybe that's how you monetize ;)
I haven't looked into too much how bb stores stuff, but yeah it feels weird to have lots of different sources of truth for the agents in an application. To get a list of conversations are you just fanning out requests to each connected remote etc?
I'm very happy with my current approach of just hosting UI on remote and doing everything on there. of course, that makes it tricky if I want to do something on my laptop and then see it on my remote UI...
I don't know if I'm articulating it clearly, but maybe you can tell what I mean. For my bb 'workspace', which is some collection of local machines and remotes, I should be able to interact with threads from any of them.
Hey just added support for multi machine. How it mainly works is that any config you have that's set up in your main .bb folder, so skills, agent MD, etc., all get synced to the target machines. So they should basically start following your instructions. Basically, when you pick a project, you can now pick which machine it runs on as well in the editor. I'm still working on the composer UI, I expect it to change a little bit, but overall, most of the things you want should work. The other thing is that we have a new, there's a new connect feature as well, which will let you basically work from your phone. So you basically sign in with your GitHub account, and then you can tunnel and start chatting with it. Or use it from your phone or from your other machines, and then this is also how you can link up your machines.
There is a new "machines" tab in settings that will let you set this up
Activity
SawyerHood commentedon Jul 2, 2026
100% agree we should do this! We actually have most of the code to do this already, we just haven't put in the elbow grease to make it good yet!
jshph commentedon Jul 3, 2026
Been daily driving BB the last 3 weeks and using the web app (through Tailscale on a home server) on my phone + laptop has become my main way to drive agents. It's working great so far! thanks for the amazing work
georgecollier-nqu commentedon Jul 3, 2026
Yep almost life changing for me haha! I hate the shitty mobile apps Codex/Claude have, I prefer web, can run everything on a VPS.
SawyerHood commentedon Jul 3, 2026
I'm clearly in need of this feature because I run 3 bb's at a time lol.
Question for @Git-on-my-level / @georgecollier-nqu / @jshph. How would you expect to "connect" your hosts together. I think the most natural thing is you could be using the desktop / local version and add your remotes there. The issue is that one of the servers has to be the "primary one" ex the one that you access from your phone / computer. This one should also be responsible for owning all of the automations / config / plugins (in the future). What is odd that this should probably be the remote one!
Curious if you all have opinions. My current thought is something like this:
This solves my pain of I can use the desktop app on my main laptop while the ui points to my headless machine and I can add my other computers as targets.
jshph commentedon Jul 3, 2026
Targets are a great concept -- question of repos getting out of date with each other is something to think thru though (but promising if done well). If i'm iterating on my VPS because I'm mobile, how does my laptop's BB (local) inherit the changes? What tree of threads is shown in the project folder -- remote or local?
That said I also run several BBs (have an ios home screen to both laptop and vps too). I think it's fine for now...
harveyfullstack commentedon Jul 4, 2026
+1 on this! If you take a look at https://multica.ai, they solve this problem and you can initialize a background daemon per machine. They have the main interface hosted themselves and you can easily switch between workspaces and machine-served agents (I use this right now). There's quite a bit in their docs to take from it and you can self-host all of it yourself. Perhaps BB can take a similar approach here?
SawyerHood commentedon Jul 4, 2026
wow @harveyfullstack i have not seen this one before!
This is very similar to how bb is currently set up under the hood (we have a server and daemon). I think we just need to figure out the UX. But maybe this makes the most sense where if you have an always on dev box host the server there and all of your other machines become daemons.
Yeah a hosted version would also be so good. We gotta add that.
Git-on-my-level commentedon Jul 4, 2026
I think you should let the user pick a primary "gateway" or whatever, it can centralized credentials, automations, etc...
Then all UIs are just clients, but you should probably let each UI cache creds locally during runtime to reduce latency and dependence on the gateway, in case there is packet loss or whatever, don't want to stream all LLM traffic through the gateway. Each UI can show itself as the main workspace but support remote bb connections (via ssh or something), or you can centralize UI configs so that all UIs connected to the same gateway get the same remote connections or something out of the box
I really like the codex remote connection UX
harveyfullstack commentedon Jul 5, 2026
Too eager to wait, I just got this working for myself as a PoC!
SawyerHood commentedon Jul 6, 2026
Wait @harveyfullstack open up a PR for this! The ui looks pretty clean. I started on this here: #510, but I mainly did infra and no ui (this PR also adds a bb connect service so you can connect sans tailscale if you want). But your ui looks like a good staring point to iterate under an experiments flag.
georgecollier-nqu commentedon Jul 8, 2026
Yeah we'd add via SSH.
But we need the nuts and bolts included e.g:
I haven't looked into too much how bb stores stuff, but yeah it feels weird to have lots of different sources of truth for the agents in an application. To get a list of conversations are you just fanning out requests to each connected remote etc?
I'm very happy with my current approach of just hosting UI on remote and doing everything on there. of course, that makes it tricky if I want to do something on my laptop and then see it on my remote UI...
I don't know if I'm articulating it clearly, but maybe you can tell what I mean. For my bb 'workspace', which is some collection of local machines and remotes, I should be able to interact with threads from any of them.
SawyerHood commentedon Jul 14, 2026
Hey just added support for multi machine. How it mainly works is that any config you have that's set up in your main .bb folder, so skills, agent MD, etc., all get synced to the target machines. So they should basically start following your instructions. Basically, when you pick a project, you can now pick which machine it runs on as well in the editor. I'm still working on the composer UI, I expect it to change a little bit, but overall, most of the things you want should work. The other thing is that we have a new, there's a new connect feature as well, which will let you basically work from your phone. So you basically sign in with your GitHub account, and then you can tunnel and start chatting with it. Or use it from your phone or from your other machines, and then this is also how you can link up your machines.
There is a new "machines" tab in settings that will let you set this up