create-open-autonomy 2.4.7 → 2.4.9

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-open-autonomy",
-  "version": "2.4.7",
+  "version": "2.4.9",
   "description": "The default Open Autonomy starter kit: a complete repository that runs its own Hermes agent against the platform, with the SDK wired in. `bun create open-autonomy <dir>` scaffolds one.",
   "license": "Apache-2.0",
   "repository": {

package/src/kit.ts

@@ -9,7 +9,7 @@
 import { existsSync, mkdirSync, readFileSync, readdirSync, rmSync, writeFileSync } from 'node:fs';
 import { dirname, join, relative, resolve } from 'node:path';
 
-export const KIT = { name: 'hermes', version: '2.4.7' } as const;
+export const KIT = { name: 'hermes', version: '2.4.9' } as const;
 export const KIT_FILE = '.open-autonomy/kit.json';
 const TEMPLATE = resolve(import.meta.dir, '..', 'template');
 

package/template/.open-autonomy/start.ts

@@ -58,7 +58,9 @@ const own = (path: string) => { if (user) Bun.spawnSync({ cmd: ['chown', '-R', `
 // through: a start from inside another agent's worker (a project's world, brought up by a task) would otherwise inherit
 // that worker's HERMES_KANBAN_DB, HERMES_KANBAN_HOME, its task and run, and file its work on the outer board.
 const inherited = (): Record<string, string> => { const env: Record<string, string> = {}; for (const [k, v] of Object.entries(process.env)) if (v !== undefined && !k.startsWith('HERMES_')) env[k] = v; return env; };
-const agentEnv = (): Record<string, string> => ({ ...inherited(), HERMES_HOME: home, ...(user ? { HOME: home, USER: user.name, LOGNAME: user.name } : {}), ...(existsSync(sock) ? { SSH_AUTH_SOCK: sock } : {}), GIT_SSH_COMMAND: process.env.GIT_SSH_COMMAND ?? 'ssh -o StrictHostKeyChecking=accept-new' });
+// TERMINAL_CWD: a conversation's shell (a channel message answered live) starts in the checkout, as a task's does —
+// Hermes would otherwise start it in the home, where the agent finds its own files and none of the project's.
+const agentEnv = (): Record<string, string> => ({ ...inherited(), HERMES_HOME: home, TERMINAL_CWD: project, ...(user ? { HOME: home, USER: user.name, LOGNAME: user.name } : {}), ...(existsSync(sock) ? { SSH_AUTH_SOCK: sock } : {}), GIT_SSH_COMMAND: process.env.GIT_SSH_COMMAND ?? 'ssh -o StrictHostKeyChecking=accept-new' });
 
 const children: Array<{ name: string; proc: ReturnType<typeof Bun.spawn> }> = [];
 let ending = false;

package/template/hermes/skills/open-autonomy/community/SKILL.md

@@ -16,9 +16,14 @@ they wish for, and talk things over in three places: the repository's issues, it
 Every quarter hour you read what is new on GitHub, and every word you say in public is a published session on the
 project page. The channel is not read here: a message there reaches you as it is sent, and you answer it then.
 
-A look is exactly four commands — `poll`, what it calls for, `mark`, the report. Never search the home, its
-databases, its logs or the gateway's state for messages: nothing there is the community's, and a look that wanders
-is a quarter hour spent for nothing.
+A look is exactly four commands — `poll`, what it calls for, `mark`, the report. The tool is
+`bun .open-autonomy/community.ts <command>` from the repository root and nothing else: there is no other copy, and
+a guessed path is a turn wasted. Never search the home, its databases, its logs or the gateway's state for messages:
+nothing there is the community's, and a look that wanders is a quarter hour spent for nothing.
+
+The report is one of two things: the word `[SILENT]` alone when nothing was new, or one plain paragraph of what
+was answered, filed and declined. Never a bracketed marker of any other kind — a marker the harness uses in its own
+context is not a report.
 
 1. Read: `bun .open-autonomy/community.ts poll` lists every issue, comment and discussion since the last look, then
    `COMMUNITY_POLL_DONE`. Nothing new: report that and stop.