Crush HTTP interface

[jpillora]

The TUI is excellent, but the underlying agent and prompts is also great - and it’d be handy to be able to drive the agent from an external chat

I’m aware I can drive it via TTY but this would be error prone

Have you guys thought about adding an http listener flag (socket or tcp) to expose the internals to other tools?

[meowgorithm]

Yes! Definitely on the roadmap. No ETA yet, but we'll keep this issue up to date on progress.

[minholi]

I’m aware I can drive it via TTY but this would be error prone

Always use tmux to keep commands running on ssh sessions. Best practice when using terminal applications or doing updates or backup restores.

[jpillora]

We can do better than tmux

[Atomzwieback]

Wouldn’t a Crush SDK be preferable here? For example, I’d like to control it programmatically rather than through a chat interface, similar to the Claude SDK.

[jpillora]

I have plans for an extra interface, but still want the TUI. That said, “headless crush” would be handy too I’m sure

…

On Thu, 11 Sep 2025 at 6:34 pm, Sebastian ***@***.***> wrote: *Atomzwieback* left a comment (charmbracelet/crush#976) <#976 (comment)> Wouldn’t a Crush SDK be preferable here? For example, I’d like to control it programmatically rather than through a chat interface, similar to the Claude SDK. — Reply to this email directly, view it on GitHub <#976 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAE2X46ISKYEBTG3T6DUBKT3SEX2HAVCNFSM6AAAAACFYVBA6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENZZGE4TANRXHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[IAliceBobI]

Big +1 on this! A web interface would be incredibly useful for remote access and mobile usage. Similar to what opencode provides with its web mode - being able to continue conversations from mobile/browser without being tied to a terminal session is a game changer for productivity.

Looking forward to seeing this land! 🚀