Clawdbot as interface for claude code
I want Clawdbot to act as an orchestration layer between me and Claude Code. The idea is: I chat with Clawdbot via Telegram for discussion, planning, and maintaining context across sessions. When there's actual implementation work to do, Clawdbot delegates to Claude Code (running on my VPS with full tool access), which does the coding and writes progress back to shared memory files. Clawdbot then reports the results back to me.
Essentially: Clawdbot as coordinator and memory-keeper, Claude Code as implementation engine, shared workspace for continuity.
Is this a sensible design for Clawdbot? If so, is there existing infrastructure I should build on, or would this require new functionality? How do most people setup a system like this?
Essentially: Clawdbot as coordinator and memory-keeper, Claude Code as implementation engine, shared workspace for continuity.
Is this a sensible design for Clawdbot? If so, is there existing infrastructure I should build on, or would this require new functionality? How do most people setup a system like this?
