@istdrc: The first demo of Slock was built on Slack on Jan 4–5, 2026. Over the month that followed — my last month at Kimi — I w…

The first demo of Slock was built on Slack on Jan 4–5, 2026. Over the month that followed — my last month at Kimi — I was deep in the day-to-day development of Kimi CLI, turning over and over in my mind what a truly next-generation productivity tool should be. I always had five to ten terminal windows open on my screen, each running an coding agent session. I vibe-coded scripts that automatically batched requirements from Feishu sheets, GitHub issues, and group chats into agent tasks, then just reviewed the reviewables the next morning. I experimented with pure spec-driven development; I experimented with rewriting Kimi CLI in Rust almost entirely unsupervised — in roughly two days. In the end, my answer was to come back to Slock and make it a real product. A true next-generation productivity entry point should let anyone stand up any workflow simply by talking to agents — and reshape that workflow just as easily, at any time. At its core, it's about being the boss. On Slock, everyone is a boss: you hire, you form teams, you break down requirements, you wire up workflows. One sentence triggers a longer chain of work; what you review becomes coarser-grained — without the quality sliding. Slock is a meta product. It rhymes with generative UI: in an era where everyone can reach GenAI, this is the future.