Discussion about this post

User's avatar
JP's avatar

The OpenClaw connection is interesting but I'd flip the causality slightly. The forces that shaped gws: CLI-first, Discovery Document-driven command generation, SKILL.md files for composable agent skills. They aren't downstream of OpenClaw. They're converging independently on the same architecture. Justin Poehnelt wrote the design thesis up in a post called 'You Need to Rewrite Your CLI for AI Agents' and it reads like a parallel derivation, not an influence.

LINCE is doing the same thing from the bottom up. Terminal as native habitat, CLIs as the composition layer. Same destination, different route.

Full gws architecture breakdown here https://reading.sh/google-workspace-finally-has-a-cli-and-its-built-for-agents-5f5fe87d0425 if you want the internals. The two-phase argument parsing from Discovery Documents is the bit that most directly connects to the MCP is dead thesis: when the command surface comes from the same docs the agent reads anyway, the discovery problem collapses.

No posts

Ready for more?