Exocortex update: Manus out, GrokBot in as the daily base

The exocortex described here is a Markdown + Git knowledge base held in a private GitHub repository, with the wiki root at about 470 pages at the time of writing. The author had already laid out its folder contract — the entrance, raw immutability, and synthesized knowledge — in an earlier article, and that contract did not move. What changed in one month was where dialogue and execution live, which is why he argues the structure can sit on the Vault's Schema while the agent runtime is swapped out.

The reason he gives for leaving Manus is a mismatch of purpose rather than a failure of tooling. His July question was whether an agent optimized for completion can work as a sparring partner, since planning straight through and stopping to question assumptions do not easily coexist. Regular runs, ingest and exocortex reads and writes were assets under Manus, but his main dialogue path had shifted toward exploration and argument, and GrokBot now fills that role.

Work is split by weight rather than by tool. GrokBot handles listening, searching, organizing, capture, outlines, sparring, discussion and light tasks, while Cursor Cloud Agent finishes large jobs — many slides, files or steps — in a git environment separate from his PC, landing differences as PRs. Linear holds tasks, ideas and things he wants to do instead of GitHub Issues, so chat history does not become the task board. A capture-only bot named ロウ writes only new notes into wiki/raw, its public template shared as a recipe without conversation history, and it is kept out of the discussion rooms. The group chat is opened only when a point splits, not as a standing entrance, and the author says the interesting part is watching a disagreement in progress and making one human judgment, not the speed of the output.