It's all just Linux, a shell and scripting wrapped around the model layer.
Those 100-in-1 swiss army knifes are so much productivity pr0n man.
A cli harness, basic *nix skills and an idea about the inference lifecycle to solve problems on demand - and go.
We now have:
• Muse
• Grok Bot
• Hermes
• Dots
• Cue (by Manus)
• Openclaw?
If you're not using at LEAST one of these, it's official: you're falling behind in tech and leaving massive productivity on the table as a result.
Most expensive mistake you could make.
@clone1018@travismakes If you just use it then yes. If you follow through on the mentality you have a self-managed stack e.g. with pulumi and switching vendors is 1 command
Model your agent logic as a state machine.
Give Jev the state + goal; the enabled events it can trigger are Choices.
That's how you use Jev with state machines. It works extremely well.
@Shpigford I just let codex do the work. It connects to all my machines and performs what I would perform there, from triggering agents to actual work https://t.co/ma2SJ9cmqs - but likely not what you mean?
Neat Android setup built in under an hour:
Termux + proot + Codex CLI + Tailscale/SSH + Whisperian + Termux:Widget.
Now I can launch Codex from my home screen, talk to it, and have it work across my private machines/servers: projects, logs, email, MCPs, whatever.
More ideas?
Neat Android setup built in under an hour:
Termux + proot + Codex CLI + Tailscale/SSH + Whisperian + Termux:Widget.
Now I can launch Codex from my home screen, talk to it, and have it work across my private machines/servers: projects, logs, email, MCPs, whatever.
More ideas?
@DorianDevelops I enjoy both depending on the job. E.g. using distinct tabs with claude in vsc is nice for "conversation management" (convos stay opened, easier to jump between sessions). Other than that, TUI supremacy
@kanwisher@vincent_koc CoW also works on mac (APFS). On Linux not always natively, depends on the file system (e.g. Btrfs). Also, to work ootb, you need a git plugin. CoW itself is a filesystem feature, not a git feature.
@cynthiamcgillis It becomes more clear if you understand the entire roundtrip of any harness or chat (like chat got web UI). Check how primitive tool calling actually works, it should explain everything.