parent
ac35f0f2cf
commit
578ee90096
2 changed files with 11 additions and 12 deletions
|
|
@ -133,7 +133,7 @@ everything below applies only when it doesn't:
|
|||
(inject a `from: <X>` message straight into the caller's own inbox)
|
||||
is on this socket too but isn't privileged to either flavour; no
|
||||
built-in in-container producer calls it today — matrix, bash and
|
||||
forge notifications all moved to pushing a todo on the harness's
|
||||
forge notifications push a todo on the harness's
|
||||
in-agent socket instead (see
|
||||
[`docs/turn-loop/mcp.md`](../turn-loop/mcp.md#waking-the-agent-from-inside-the-container)).
|
||||
- **Storage/mounts** — only the manager container gets
|
||||
|
|
@ -147,7 +147,7 @@ everything below applies only when it doesn't:
|
|||
path writes `flake.lock` any more — `request_update_meta_inputs` was
|
||||
removed, leaving the operator dashboard's `POST
|
||||
/api/meta-update` as the only entry point.
|
||||
- **Prompt** — _not_ treated differently in practice any more: `prompts/system.md`
|
||||
- **Prompt** — treated identically: `prompt::render` always filters for `agent`. `prompts/system.md`
|
||||
still carries `<!-- role:agent -->` / `<!-- role:manager -->` marker
|
||||
blocks, but `prompt::render` filters for `"agent"` unconditionally for
|
||||
every container, manager included ("always `agent` role — there is
|
||||
|
|
|
|||
Loading…
Reference in a new issue