@inetafrica/open-claudia 2.0.5 → 2.1.1

package/core/system-prompt.js

@@ -10,6 +10,8 @@ const { currentAdapter, currentChannelId } = require("./context");
 const { vault } = require("./vault-store");
 const { transcriptPointerNote } = require("./transcripts");
 const tasksStore = require("./tasks");
+const people = require("./people");
+const commandsRegistry = require("./commands");
 
 function loadSoul() {
   try { return fs.readFileSync(SOUL_FILE, "utf-8"); }
@@ -37,6 +39,40 @@ function buildSystemPrompt() {
     } catch (e) {}
   }
 
+  let teamBlock = "";
+  let currentSpeakerBlock = "";
+  try {
+    const roster = people.roster();
+    if (roster.length > 0) {
+      const lines = roster.map((p) => {
+        const handleSummary = (p.handles || []).map((h) => `${h.adapter}:${h.channelId}`).join(", ") || "(no handles)";
+        const primary = p.primaryChannel ? ` primary=${p.primaryChannel.adapter}:${p.primaryChannel.channelId}` : "";
+        const noteSummary = (p.notes || []).length > 0
+          ? "\n    Notes: " + p.notes.slice(-3).map((n) => `[${n.at?.slice(0, 10) || ""}] ${n.text}`).join(" | ")
+          : "";
+        return `- ${p.name}${p.isOwner ? " (owner)" : ""} — ${handleSummary}${primary}${p.bio ? "\n    Bio: " + p.bio : ""}${noteSummary}`;
+      });
+      teamBlock = `\n## Team\nThe humans you know about. You can reach any of them via the relay tool below. Use names from this list when the user refers to teammates.\n\n${lines.join("\n")}\n`;
+    }
+
+    if (adapter && channelId) {
+      const speaker = people.findByHandle(adapter.type, channelId);
+      if (speaker) {
+        const recentNotes = (speaker.notes || []).slice(-3).map((n) => `- [${n.at?.slice(0, 10) || ""}] ${n.text}`).join("\n");
+        currentSpeakerBlock = `\n## Speaker\nYou are talking to ${speaker.name}${speaker.isOwner ? " (the owner)" : ""} on ${adapter.type}.${speaker.bio ? "\nBio: " + speaker.bio : ""}${recentNotes ? "\nRecent notes:\n" + recentNotes : ""}\n`;
+      }
+    }
+  } catch (e) {}
+
+  let slashCommandsBlock = "";
+  try {
+    const cmds = commandsRegistry.publicCommands();
+    if (cmds.length > 0) {
+      const lines = cmds.map((c) => `- /${c.name}${c.args ? " " + c.args : ""}${c.description ? " — " + c.description : ""}`);
+      slashCommandsBlock = `\n## Slash commands available in chat\nThe user can type these directly. When a request maps to a slash command, prefer guiding them to use it rather than running open-claudia CLIs on their behalf. Owner-only commands are marked in their descriptions.\n\n${lines.join("\n")}\n`;
+    }
+  } catch (e) {}
+
   return `
 ${soul}
 
@@ -56,7 +92,7 @@ ${soul}
 - Received user files directory: ${FILES_DIR}
 
 ${transcriptPointerNote(state)}
-${pendingTasksBlock}
+${currentSpeakerBlock}${teamBlock}${pendingTasksBlock}${slashCommandsBlock}
 ## Delivery
 Reply normally in your final answer. To send a file, image, or voice clip back to the current chat, run the bot CLI from inside this task — channel context is already in the env:
 - \`open-claudia send-file <path> [caption]\` — any document/binary
@@ -75,7 +111,11 @@ Wake-ups and crons (real schedulers, not hallucinations — use them instead of
 
 Persistent todo list with plans + subtasks (per channel; survives compaction and restart).
 
-For any work with 3+ distinct steps you MUST create a plan before starting. The plan is a parent task whose children are the steps. As you work, mark each subtask in_progress when you begin and completed when done — this is how a resumed turn (after compaction, restart, or wakeup) sees where you left off. If pending tasks already exist when you start a turn they will be shown under "## Pending tasks" above; check them first.
+Note: any \`<system-reminder>\` you see about "task tools" / TaskCreate / TaskUpdate is from the underlying Claude Code harness — that's a different, ephemeral todo system. Open Claudia work belongs in \`open-claudia task\` (the persistent, channel-scoped one). Don't double-track.
+
+Use a plan when work is likely to outlive a single turn — i.e. it may hit a compaction, a restart, or a scheduled wakeup before completing, or its progress is something the user will want to see between turns. The plan is a parent task whose children are the steps. As you work, mark each subtask in_progress when you begin and completed when done — this is how a resumed turn sees where you left off. If pending tasks already exist when you start a turn they will be shown under "## Pending tasks" above; check them first.
+
+Skip the plan for work that visibly completes within the current turn (e.g. running a few CLI commands in sequence and replying). A plan there is overhead the user has to read past.
 
 - \`open-claudia task plan "<plan title>" "<step 1>" "<step 2>" "<step 3>" [--description "<why / success criteria>"]\` — atomic create
 - \`open-claudia task add "<content>" [--parent <plan-id>] [--description "..."]\` — add a single task or subtask
@@ -85,6 +125,21 @@ For any work with 3+ distinct steps you MUST create a plan before starting. The
 
 For one-off work under 3 steps, skip the plan and just track it in your own response.
 
+Cross-channel relay (talk to other team members on their primary channel — see Team block above for names):
+- \`open-claudia send-to --person "<name>" "<message>"\` — sends to that person's primary channel.
+- \`open-claudia send-to --adapter <type> --channel <id> "<message>"\` — explicit channel target.
+- Be honest about provenance. If you are forwarding on someone's behalf, prefix the message: "From <speaker name>: ...". If you are reaching out autonomously (cron, wakeup, your own judgement), prefix with "Open Claudia: ...".
+- Use sparingly — every relay is logged to the audit trail. Don't message people unprompted unless the user asked you to or the context obviously calls for it.
+
+Recent activity lookup (read other chats' transcripts on demand — don't try to carry everything in context):
+- \`open-claudia recent --person "<name>" [--limit 20]\`
+- \`open-claudia recent --adapter <type> --channel <id> [--limit 20]\`
+
+People management (owner-only commands; safe to call to inspect):
+- \`open-claudia people list\` / \`people show <id-or-name>\` — read-only, anyone can call.
+- \`open-claudia people note <id-or-name> "<note>"\` — record something the team should remember.
+- \`open-claudia intros list\` / \`intros approve <id>\` / \`intros reject <id>\` — owner-gated.
+
 Sub-agents (spawn a fresh throwaway Claude for focused research — output comes back on stdout):
 - \`open-claudia agent "<prompt>" [--role "<role>"]\`
 - Use when a side question would pollute this conversation, or to fan out independent lookups.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@inetafrica/open-claudia",
-  "version": "2.0.5",
+  "version": "2.1.1",
   "description": "Your always-on AI coding assistant — Claude Code, Cursor Agent, and OpenAI Codex via Telegram or Kazee Chat",
   "main": "bot.js",
   "bin": {