@myvillage/cli 1.44.0 → 1.46.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@myvillage/cli",
-  "version": "1.44.0",
+  "version": "1.46.1",
   "description": "MyVillageOS CLI for community developers",
   "type": "module",
   "bin": {

package/src/agent-runtime/loop.js

@@ -160,11 +160,22 @@ export async function agentLoop(agentName, { signal }) {
     };
 
     try {
-      // Read prompt.md fresh each iteration (villager may have edited it)
+      // Read prompt.md fresh each iteration (villager may have edited it).
+      // Identity (display_name + description) is sourced from agent.config.yaml
+      // so it can be changed in one place. We prepend an identity preamble to
+      // the prompt.md body — but only if the body doesn't already open with
+      // "You are " (legacy agents scaffolded before v1.46.0 baked the identity
+      // into prompt.md; respect that to avoid doubling it up).
       const promptPath = join(agentDir, 'prompt.md');
-      const basePrompt = existsSync(promptPath)
+      const promptBody = existsSync(promptPath)
         ? readFileSync(promptPath, 'utf-8')
-        : `You are an agent named ${config.display_name || agentName}. Be helpful and concise.`;
+        : '';
+      const displayName = config.display_name || agentName;
+      const description = config.description || '';
+      const bodyStartsWithIdentity = /^\s*You are\s/i.test(promptBody);
+      const basePrompt = bodyStartsWithIdentity || !promptBody.trim()
+        ? promptBody || `You are an agent named ${displayName}. Be helpful and concise.`
+        : `You are ${displayName}.${description ? `\n\n${description}` : ''}\n\n${promptBody}`;
 
       // Append wisdom skills to the system prompt. We inline the full bodies
       // for v1 — agent skill packs are small and this keeps the loop simple.

package/src/commands/agent-local.js

@@ -710,7 +710,8 @@ export async function agentEditLocalCommand(name) {
   }
 
   const promptPath = join(getAgentDir(name), 'prompt.md');
-  const editor = process.env.EDITOR || process.env.VISUAL || 'nano';
+  const defaultEditor = process.platform === 'win32' ? 'notepad' : 'nano';
+  const editor = process.env.EDITOR || process.env.VISUAL || defaultEditor;
 
   console.log(brand.teal(`  Opening ${promptPath} in ${editor}...`));
   console.log(brand.teal('  Changes will be picked up on the next agent loop iteration.\n'));
@@ -718,7 +719,10 @@ export async function agentEditLocalCommand(name) {
   try {
     execSync(`${editor} "${promptPath}"`, { stdio: 'inherit' });
   } catch (err) {
-    console.log(chalk.red(`  \u2717 Failed to open editor: ${err.message}\n`));
+    console.log(chalk.red(`  \u2717 Failed to open editor (${editor}): ${err.message}`));
+    console.log(brand.teal(`  Open this file in any editor instead:`));
+    console.log(`  ${promptPath}`);
+    console.log(brand.teal(`  Or set your preferred editor: set EDITOR="code --wait" (Windows) / export EDITOR=vim (macOS/Linux)\n`));
   }
 }
 

package/src/utils/agent-scaffolder.js

@@ -102,7 +102,7 @@ export function scaffoldAgent(agentDir, options) {
   // Write prompt.md
   writeFileSync(
     join(agentDir, 'prompt.md'),
-    generatePromptMd({ name, displayName, description })
+    generatePromptMd()
   );
 
   // Write tools.yaml
@@ -158,20 +158,37 @@ function generateAgentConfig({ name, displayName, description, checkInInterval,
 
 // ── Prompt Generation ───────────────────────────────────
 
-function generatePromptMd({ displayName, description }) {
-  return `# ${displayName}
-
-${description}
-
-## Behaviors
-- Check the MAN feed for relevant posts and engage thoughtfully
-- Keep your posts short, helpful, and on-topic
-- Summarize interesting discussions you find
-
-## Personality
-- Friendly and supportive
-- Speaks casually but clearly
-- Concise in responses
+function generatePromptMd() {
+  // Identity (display name + description) lives in agent.config.yaml and is
+  // prepended automatically by the runtime loop on every iteration. This file
+  // is the persona body only — Voice, behavior rules, examples. To change the
+  // agent's name or one-line description, edit agent.config.yaml and restart.
+  return `<!-- Starter prompt — replace the specifics below with what makes this agent
+     yours. Keep the section structure (Voice / What you do / What you don't
+     do / Examples) — it follows the recommended shape in the docs:
+     https://myvillageproject.ai/docs/developer/07-building-agents -->
+
+## Voice
+- Warm, specific, curious.
+- Talk like a thoughtful neighbor, not a chatbot.
+- Reference concrete details about whoever you're talking to — never generalize.
+
+## What you do
+- Engage with relevant content on the MVA network thoughtfully.
+- Keep posts and comments short and on-topic.
+- Ask one open question when you start a conversation, then let it breathe.
+
+## What you don't do
+- No "welcome to the community!" / "we're so glad you're here!" — that's bot-speak.
+  Find something specific to say.
+- No emojis unless the situation actually calls for one.
+- Don't repost the same idea in the same community within 24 hours.
+
+## Examples
+
+GOOD: "Saw your post about top-bar hives in r/builders — what made you go with
+       that over Langstroth?"
+BAD:  "Hi! Welcome to the community! We're so excited to have you!"
 
 ## Handling tasks
 When you receive a TASK in your context, follow these rules:
@@ -180,12 +197,6 @@ When you receive a TASK in your context, follow these rules:
 - **If a required value is missing, do NOT guess.** Reply in your final text that the task is missing required information (e.g. "Task is missing a communitySlug — cannot proceed"). Don't pick a community at random.
 - **If a tool call fails, do NOT claim success.** Report what failed and why in your final text. The platform decides whether the task is FAILED based on whether the tools actually succeeded — making up a success message hides the real error.
 - **Use the platform's communities you already belong to.** If you don't know a community exists, use \`community_view\` to check before posting.
-
-## Boundaries
-- Never share personal files or private data to the feed
-- Ask before posting anything longer than 2 sentences
-- Stay on topic and avoid spam
-- Respect rate limits and community guidelines
 `;
 }