Repository navigation
Remote-first daemon approach #11
Description
Activity
or actually.. just use crabcode with https://getmoshi.app/guides/herdr, no need to develop this (maybe)
Also currently exploring forking https://t3.codes, minimally. And adding crabcode support there via the fork.
From what I tested, you only need to actually update the Connector CLI/Server/Process, then anyone can use
crabcode, even my phone!Also experimented with http://herdr.dev, it works great.
I made a little companion CLI to use it with herdr: https://github.com/blankeos/herdr-serve so I can use it remotely.
It fits pretty much all the remote usecases but just have to accept a slightly jank TUI experience on mobile. But it gets the job done which is great!
This is my recommended path, at least until I get time to make it work more like
opencode2(if ever). opencode2 is great but the scope is a little too big rearchitect crabcode like that right now.More alternatives:
- https://www.codync.dev seems promising and supports custom ACP natively - so we might be able to get crabcode as a Grok Bot product - this is if you want to get into that "pstack/bot/kitchen-style ai development workflow"
- https://github.com/zeronsh/zeron - seems promising as a control plane (more of a nicer UX alternative to my herdr + herdr-serve method) - but I found it doesn't support custom ACP natively.
Goal: Use crabcode w/ a more seamless handoff + be useful anywhere
/remote(use nosleep), keep prompting/checking on my phone" (big personal usecase).Future usecases I don't know how to solve yet: