fix(agent-presets): keep the goal service on the host plane in the other presets
`cordis` and `code` are full copies of `standard`, so each carried its own copy of the goals group the Gateway cannot reach through. Same change, same reason.
This commit is contained in:
@@ -101,23 +101,14 @@
|
|||||||
|
|
||||||
# ── goals ───────────────────────────────────────────────────────────────────
|
# ── goals ───────────────────────────────────────────────────────────────────
|
||||||
|
|
||||||
- id: goals
|
# Only the model-facing tool. The goal SERVICE, its session driver, and the
|
||||||
name: cordis:group
|
# `/goal` command stay on the host plane: the Gateway serves the goal domain as
|
||||||
group: true
|
# Remote endpoints whose receiver comes from a generated descriptor, so it
|
||||||
isolate:
|
# resolves `goals` on the host and an entry-local realm here would hide it. The
|
||||||
goals: true
|
# registry is keyed by session anyway, so one host instance serves every
|
||||||
config:
|
# session. What a preset chooses is whether its agent can call the goal tool.
|
||||||
- id: goal
|
- id: tool-goal
|
||||||
name: '@deepseek-ai/dsh-goal'
|
name: '@deepseek-ai/dsh-tool-goal'
|
||||||
|
|
||||||
- id: goal-session
|
|
||||||
name: '@deepseek-ai/dsh-goal-session'
|
|
||||||
|
|
||||||
- id: command-goal
|
|
||||||
name: '@deepseek-ai/dsh-command-goal'
|
|
||||||
|
|
||||||
- id: tool-goal
|
|
||||||
name: '@deepseek-ai/dsh-tool-goal'
|
|
||||||
|
|
||||||
# ── plan mode ───────────────────────────────────────────────────────────────
|
# ── plan mode ───────────────────────────────────────────────────────────────
|
||||||
|
|
||||||
|
|||||||
@@ -76,23 +76,14 @@
|
|||||||
|
|
||||||
# ── goals ───────────────────────────────────────────────────────────────────
|
# ── goals ───────────────────────────────────────────────────────────────────
|
||||||
|
|
||||||
- id: goals
|
# Only the model-facing tool. The goal SERVICE, its session driver, and the
|
||||||
name: cordis:group
|
# `/goal` command stay on the host plane: the Gateway serves the goal domain as
|
||||||
group: true
|
# Remote endpoints whose receiver comes from a generated descriptor, so it
|
||||||
isolate:
|
# resolves `goals` on the host and an entry-local realm here would hide it. The
|
||||||
goals: true
|
# registry is keyed by session anyway, so one host instance serves every
|
||||||
config:
|
# session. What a preset chooses is whether its agent can call the goal tool.
|
||||||
- id: goal
|
- id: tool-goal
|
||||||
name: '@deepseek-ai/dsh-goal'
|
name: '@deepseek-ai/dsh-tool-goal'
|
||||||
|
|
||||||
- id: goal-session
|
|
||||||
name: '@deepseek-ai/dsh-goal-session'
|
|
||||||
|
|
||||||
- id: command-goal
|
|
||||||
name: '@deepseek-ai/dsh-command-goal'
|
|
||||||
|
|
||||||
- id: tool-goal
|
|
||||||
name: '@deepseek-ai/dsh-tool-goal'
|
|
||||||
|
|
||||||
# ── plan mode ───────────────────────────────────────────────────────────────
|
# ── plan mode ───────────────────────────────────────────────────────────────
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user