Skip to content

fix(add-mnemon): run mnemon setup in index.ts main(), not entrypoint.sh#2656

Open
MoonCaves wants to merge 1 commit into
nanocoai:mainfrom
MoonCaves:fix/add-mnemon-boot-hook
Open

fix(add-mnemon): run mnemon setup in index.ts main(), not entrypoint.sh#2656
MoonCaves wants to merge 1 commit into
nanocoai:mainfrom
MoonCaves:fix/add-mnemon-boot-hook

Conversation

@MoonCaves
Copy link
Copy Markdown

The /add-mnemon skill tells you to add mnemon setup to container/entrypoint.sh, but the host overrides the image ENTRYPOINT at spawn (bash -c 'exec bun run /app/src/index.ts'), so that line never runs and mnemon's hooks never register.

This moves the setup call to the top of main() in container/agent-runner/src/index.ts — the actual boot path, which is bind-mounted fresh into each container (so no image rebuild). Guarded on the claude provider and the mnemon binary existing; idempotent.

One gotcha I baked into the note: run it inside main(), not the spawn command. If setup runs before bun starts, the container has no heartbeat yet and the host kills it as orphaned before it can reply.

Verified end-to-end (remember + recall over Telegram).

The host spawns containers with `--entrypoint bash -c 'exec bun run
/app/src/index.ts'`, so the image ENTRYPOINT never runs — the setup line
the skill adds to entrypoint.sh is dead code and mnemon's hooks never
register. Move it to the top of main() in agent-runner/src/index.ts (the
real boot path, bind-mounted fresh per spawn, no rebuild), guarded on the
claude provider + binary presence. Running it there keeps the agent's
heartbeat alive; running it before bun starts makes the host kill the
container as orphaned before it can reply.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant