macroclaw 0.4.0 → 0.5.0

package/README.md

@@ -5,52 +5,6 @@ Telegram-to-Claude-Code bridge. Bun + Grammy.
 Uses the Claude Code CLI (`claude -p`) rather than the Agent SDK to avoid any possible
 ToS issues with using a Claude subscription programmatically.
 
-## Vision
-
-Macroclaw is a minimal bridge between Telegram and Claude Code. It handles the parts
-that a Claude session can't: receiving messages, managing processes, scheduling tasks,
-and delivering responses.
-
-Everything else — personality, memory, skills, behavior, conventions — lives in the
-workspace. The platform stays small so the workspace can be infinitely customizable
-without touching platform code.
-
-## Architecture
-
-Macroclaw follows a **thin platform, rich workspace** design:
-
-**Platform** (this repo) — the runtime bridge:
-- Telegram bot connection and message routing
-- Claude Code process orchestration and session management
-- Background agent spawning and lifecycle
-- Cron scheduler (reads job definitions from workspace)
-- Message queue (FIFO, serial processing)
-- Timeout management and auto-retry
-
-**Workspace** — the intelligence layer, initialized from [`workspace-template/`](workspace-template/):
-- [`CLAUDE.md`](workspace-template/CLAUDE.md) — agent behavior, conventions, response style
-- [`.claude/skills/`](workspace-template/.claude/skills/) — teachable capabilities
-- [`.macroclaw/cron.json`](workspace-template/.macroclaw/cron.json) — scheduled job definitions
-- [`MEMORY.md`](workspace-template/MEMORY.md) — persistent memory
-
-### Where does a new feature belong?
-
-**Platform** when it:
-- Requires external API access (Telegram, future integrations)
-- Manages processes (spawning Claude, background agents, timeouts)
-- Operates outside Claude sessions (cron scheduling, message queuing)
-- Is a security boundary (chat authorization, workspace isolation)
-- Is bootstrap logic (workspace initialization)
-
-**Workspace** when it:
-- Defines agent behavior or personality
-- Is a convention Claude can follow via instructions
-- Can be implemented as a skill
-- Is data that Claude reads/writes (memory, tasks, cron definitions)
-- Is a formatting or response style rule
-
-> **Litmus test:** Could this feature work if you just wrote instructions in CLAUDE.md and/or created a skill? If yes → workspace. If no → platform.
-
 ## Security Model
 
 Macroclaw runs with `dangerouslySkipPermissions` enabled. This is intentional — the bot
@@ -138,6 +92,52 @@ bun test       # run tests (100% coverage enforced)
 bun run claude # open Claude Code CLI in current main session
 ```
 
+## Vision
+
+Macroclaw is a minimal bridge between Telegram and Claude Code. It handles the parts
+that a Claude session can't: receiving messages, managing processes, scheduling tasks,
+and delivering responses.
+
+Everything else — personality, memory, skills, behavior, conventions — lives in the
+workspace. The platform stays small so the workspace can be infinitely customizable
+without touching platform code.
+
+## Architecture
+
+Macroclaw follows a **thin platform, rich workspace** design:
+
+**Platform** (this repo) — the runtime bridge:
+- Telegram bot connection and message routing
+- Claude Code process orchestration and session management
+- Background agent spawning and lifecycle
+- Cron scheduler (reads job definitions from workspace)
+- Message queue (FIFO, serial processing)
+- Timeout management and auto-retry
+
+**Workspace** — the intelligence layer, initialized from [`workspace-template/`](workspace-template/):
+- [`CLAUDE.md`](workspace-template/CLAUDE.md) — agent behavior, conventions, response style
+- [`.claude/skills/`](workspace-template/.claude/skills/) — teachable capabilities
+- [`.macroclaw/cron.json`](workspace-template/.macroclaw/cron.json) — scheduled job definitions
+- [`MEMORY.md`](workspace-template/MEMORY.md) — persistent memory
+
+### Where does a new feature belong?
+
+**Platform** when it:
+- Requires external API access (Telegram, future integrations)
+- Manages processes (spawning Claude, background agents, timeouts)
+- Operates outside Claude sessions (cron scheduling, message queuing)
+- Is a security boundary (chat authorization, workspace isolation)
+- Is bootstrap logic (workspace initialization)
+
+**Workspace** when it:
+- Defines agent behavior or personality
+- Is a convention Claude can follow via instructions
+- Can be implemented as a skill
+- Is data that Claude reads/writes (memory, tasks, cron definitions)
+- Is a formatting or response style rule
+
+> **Litmus test:** Could this feature work if you just wrote instructions in CLAUDE.md and/or created a skill? If yes → workspace. If no → platform.
+
 ## License
 
 MIT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "macroclaw",
-  "version": "0.4.0",
+  "version": "0.5.0",
   "description": "Telegram-to-Claude-Code bridge",
   "license": "MIT",
   "type": "module",

package/src/cli.ts

@@ -3,6 +3,7 @@ import {existsSync, readFileSync} from "node:fs";
 import {join, resolve} from "node:path";
 import {createInterface} from "node:readline";
 import {defineCommand} from "citty";
+import pkg from "../package.json" with { type: "json" };
 import {initLogger} from "./logger";
 import {ServiceManager, type SystemService} from "./service";
 import {loadSessions} from "./sessions";
@@ -180,7 +181,7 @@ const serviceCommand = defineCommand({
 });
 
 export const main = defineCommand({
-	meta: { name: "macroclaw", description: "Telegram-to-Claude-Code bridge", version: "0.0.0-dev" },
+	meta: { name: pkg.name, description: pkg.description, version: pkg.version },
 	subCommands: { start: startCommand, setup: setupCommand, claude: claudeCommand, service: serviceCommand },
 });