Goose web/mobile remote access and p2p progress

[michaelneale]

I wanted to report on this ongoing body of work: #10906 (comment) which is now in implementation phase.

Goose mobile was a swift app, which used a hosted tunnel, this new approach is direct p2p, with wasm/web options (mobile web app, PWA) as well as api/cli etc options.

It is currently in a early working state, even brought back some design elements from the old app:

it works (currently) as a CDN hosted app (which has no state/processing):

https://aaif-goose.github.io/goose-mobile/

This then provides a public "card" which can be shared with your goose and accepted into it, and then your goose can provide its public "card" which the app accepts - this provides an enduring secure connection between them (and only them) which can work no matter where either end works (these are peers in the p2p sense, although in a browser it is clearly a client, in this case it is an ACP client that makes use of the react widgets from the desktop app).

I believe this may shape up to be a nice replacement - could imagine a very easy experience wher eyou scan a code from your desktop app or cli, get a web app instantly (nothing to install) and then you share its card back to your other end to provide a maximally secure binding, and you have mobile access.

Curious to hear any thoughts - and open to any help on the linked WIP issue.

Enjoy!

[ccgauvin94]

I think this is tremendous and roam really adds a lot to Goose. Claude Code RC has been a killer feature for me and this is an even bigger deal with ACP because ACP by default (at least right now) restricts the filesystems you can access to just where the Goose server is. So the only way to really code in multiple places with the same client is through something like roam.

I've been working on a native Android ACP client and this is a natural fit I believe:
https://github.com/ccgauvin94/grouse

It is currently n=1 tested. Very open to suggestions or work. But it's pure ACP and should work as is with any goose serve since the ACP switch.

Additionally, I made roam branch - this requires a currently undocumented small shim to allow goose serve to federate with the goose roam sessions over iroh. It's working fine for me (tm) but this should be considered a very unstable feature with probably a pretty low chance of getting the shim upstreamed. More on that soon though.

https://github.com/ccgauvin94/grouse/tree/roam

[michaelneale]

@ccgauvin94 would like to learn more about the federation as maybe that is the missing piece? if we want to go into detail can spec things up by hand in the issue and we can have our agents try things out if you like.

Also made me think - should there be a consolidated view - so you connect to multiple hosts at once, but all one big list/grouping of things across machines?

[ccgauvin94]

Shim is here:

https://github.com/ccgauvin94/goose/tree/feat/acp-federate-roam

It wasn't really designed to be well architected, just quickly get me off the ground. IMO I think that the unified view should live at the server level so that it doesn't need to be reimplemented in every app. Basically the federation shim is just translating roam sessions to native sessions with passthrough.

The way I wrote it that probably kills it as-is, is that there's nothing in the ACP spec that knows about roam, so I added a roam: prefix to remote sessions, and use that to indicate to the client that they are not local sessions. We would need some marker on SessionInfo to denote that it's not a local session.

If you think it fits the vision, it's something I'd love to help develop further.