SC-11 Per-instance override surface (UI affordances) #633

New issue

Closed

opened 2026-05-01 10:35:56 +00:00 by claude-desktop · 0 comments

claude-desktop commented

2026-05-01 10:35:56 +00:00

Collaborator

User story

As an operator, I want every editor in the agent-config surface to support the instance scope from day one, so that dev-1 and dev-2 can run different prompts, models, plugins, MCP servers, or skill variants without forking the whole agent type.

Acceptance criteria

Filter row

Each tab's filter row carries a Scope: All | Builtin | Global | Agent type | Instance selector. Picking Instance reveals an instance-name dropdown listing every agents row.

Editor scope ladder

The 4-chip scope ladder visualiser supports the Instance chip as the most-specific layer. Active chip → editing that scope; clicking a parent chip navigates to that scope's row (or shows "Create override here" CTA).
A Fork to <instance> ▾ button appears on rows whose effective scope is higher than instance.

Agents-page deep link

The agents page's per-instance side panel (apps/web/src/components/agents/...) gains a Customize ▾ action that deep-links to /settings/agent-config?scope=instance&instance_id=<id> filtered to that instance.
Skills and System-prompt editors honour the deep link and pre-select the instance.

Render integration

No platform changes — render-to-disk already handles instance scope (SC-2). This story is purely the UI affordance.

Tests

Smoke test: fork a skill to dev-2, edit, dispatch to dev-2, assert the dispatch loaded the instance-scoped body (use the test harness's resolver mock to verify; the dispatch happens against a real worker instance).

Out of scope

Compare-instances diff view (e.g. dev-1 vs. dev-2 for the same skill) — useful but separate.
Per-instance secret scoping (secrets remain global; revisit if a use case appears).

References

specs/agent-config-customization.md §Story SC-11
apps/web/src/routes/agents.tsx and the per-instance side panel
Depends on SC-7, SC-8, SC-9.

## User story As an operator, I want every editor in the agent-config surface to support the `instance` scope from day one, so that `dev-1` and `dev-2` can run different prompts, models, plugins, MCP servers, or skill variants without forking the whole agent type. ## Acceptance criteria ### Filter row - [ ] Each tab's filter row carries a `Scope: All | Builtin | Global | Agent type | Instance` selector. Picking `Instance` reveals an instance-name dropdown listing every `agents` row. ### Editor scope ladder - [ ] The 4-chip scope ladder visualiser supports the `Instance` chip as the most-specific layer. Active chip → editing that scope; clicking a parent chip navigates to that scope's row (or shows "Create override here" CTA). - [ ] A `Fork to <instance> ▾` button appears on rows whose effective scope is higher than instance. ### Agents-page deep link - [ ] The agents page's per-instance side panel (`apps/web/src/components/agents/...`) gains a `Customize ▾` action that deep-links to `/settings/agent-config?scope=instance&instance_id=<id>` filtered to that instance. - [ ] Skills and System-prompt editors honour the deep link and pre-select the instance. ### Render integration - [ ] No platform changes — render-to-disk already handles instance scope (SC-2). This story is purely the UI affordance. ### Tests - [ ] Smoke test: fork a skill to `dev-2`, edit, dispatch to `dev-2`, assert the dispatch loaded the instance-scoped body (use the test harness's resolver mock to verify; the dispatch happens against a real worker instance). ## Out of scope - Compare-instances diff view (e.g. `dev-1` vs. `dev-2` for the same skill) — useful but separate. - Per-instance secret scoping (secrets remain global; revisit if a use case appears). ## References - `specs/agent-config-customization.md` §Story SC-11 - `apps/web/src/routes/agents.tsx` and the per-instance side panel - Depends on **SC-7**, **SC-8**, **SC-9**.

claude-desktop added the

area:dashboard

type:user-story

labels

2026-05-01 10:36:34 +00:00

claude-desktop added this to the Agent config customization milestone

2026-05-01 10:36:43 +00:00