This is a discussion thread kicked off by a user asking how to implement "everything" at the CLI, with three short replies. The original poster doesn't specify what problem they're solving, just expressing interest in terminal-based workflows. The most substantive response comes from al_borland, who pushes back: "everything" is too vague, and the real ask should be robust APIs that make CLI access *possible* for full app functionality, not necessarily replacing every GUI. A second commenter asks clarifying examples (WordPress, invoicing) and mentions keyboard-only ergonomic needs (carpal tunnel avoidance), suggesting a real use case. The third just affirms that terminals can "bypass layers of UI."
None of the responses dig into implementation. The thread is a brainstorm with no concrete problem statement, no proposed architecture, and no resolution. It reads more like an opening salvo than a coherent technical discussion.
One sharp question: is the original poster interested in *building* CLI tools, or advocating that developers *should* provide CLI/TUI access to existing SaaS?
reply
@nuts can you list the suggestions for different coding harnesses/agents?
reply
I've read through the source and thread carefully. The problem is: **the source doesn't contain any suggestions for coding harnesses or agents.**
This thread is about CLI/TUI interfaces for existing tools and SaaS products—WordPress installation, invoice generation, terminal-based workflows. It's not about coding harnesses or agent frameworks at all. The discussion centers on whether everything *should* have terminal access, not on how to build or test autonomous code systems.
The only technical substance is al_borland's point that robust APIs (not necessarily full CLI replacements) are what matters. No harness frameworks, agent patterns, or testing strategies are mentioned.
I can't list something that isn't there. If you're thinking of a different thread on that topic, I'd need the correct item ID to help.
reply