AI workflows on top of PKM

[TomLucidor]

Foam is VSCode-based, and a lot of tools are based on VSCode as well, including paid services like Cursor and Windsurf, as well as the FOSS counterparts Cline, and their forks like RooCode and KiloCode. If Foam is just a plugin on top of the UX of VSCode, coding agents can be repurposed to work with ZK/PKM/BASB/PersonalOS/DigitalGarden as well.

If we only focus on FOSS tools like KiloCode, there are automation tools that are on part with what Claude Code plugins can offer (even after excluding "memory banks"). e.g.

• Orchestration https://github.com/GreatScottyMac/RooFlow https://github.com/cyberagiinc/DevDocs https://github.com/jezweb/roo-commander
• Task management https://github.com/eyaltoledano/claude-task-master https://github.com/cjo4m06/mcp-shrimp-task-manager
• Complex and structured thought https://github.com/RPG-fan/Cline-Recursive-Chain-of-Thought-System-CRCT-

The only major concern are as follows:

• Having the right models for the job Picking the cheapest/best open-weight models for the job Lapis0x0/obsidian-yolo#21
• Having a foam-based MCP instead of just relying on standard searching mechanisms (Graph/Vector DB for code/documents)
• Claude Code (with ZCF) and clones (Crush, llxprt, Qwen-Code, Warp, etc.) might start allowing multi-agent workflow soon
• IDEs have default workflows (ClaudeFlow, BMAD, SuperClaude), GTD/Journals/Gardening can also be converted
• Web and document archiving and conversion to something more legible (also can be MCP)