You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Proposal: a session-visible notice seam for plugin advisories
#10263
A plugin that discovers an environment problem at session start has no way to
tell the person looking at the session. The available channels in 0.2.1-rc.2 are ctx.logger.warn (host log, invisible unless opened), a
runtime-context entry (model-visible, not a notification), and agent/error
(reserved for failures). There is no ctx.notices/toast service and no client
slot for one.
Concrete case: this repository's WSL plugin runs a session-start preflight for bubblewrap, systemd PID 1, the user manager, systemd-run and Linger. A
failure is advisory — it must not fail the session or install anything — but it
is exactly the information the user needs before the first command fails
closed. Today the plugin publishes the advisory to the log and to a
session-scoped runtime-context entry; the GUI cannot render it as a banner.
Proposal: a small service plus a client slot, mirroring the approval service's
session-scoped contract:
Requirements: visible in the session before the first failed command;
session-scoped; severity + remedy; replaceable/dismissable (a fixed environment
must not keep the old warning); non-fatal (no turn cancelled, no tool result
changed). The host keeps the last value per (session, id) for reconnect and
replay.
Nothing here is model-facing: producers that also want the model to see the
advisory keep their runtime-context entry. The seam is presentational.
Full context, current workaround and the plugin's use of it: docs/UPSTREAM-SESSION-NOTICE.md in Big-Dao/dsh-plugin-wsl-env.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
A plugin that discovers an environment problem at session start has no way to
tell the person looking at the session. The available channels in
0.2.1-rc.2arectx.logger.warn(host log, invisible unless opened), aruntime-context entry (model-visible, not a notification), and
agent/error(reserved for failures). There is no
ctx.notices/toast service and no clientslot for one.
Concrete case: this repository's WSL plugin runs a session-start preflight for
bubblewrap, systemd PID 1, the user manager,systemd-runand Linger. Afailure is advisory — it must not fail the session or install anything — but it
is exactly the information the user needs before the first command fails
closed. Today the plugin publishes the advisory to the log and to a
session-scoped runtime-context entry; the GUI cannot render it as a banner.
Proposal: a small service plus a client slot, mirroring the approval service's
session-scoped contract:
Requirements: visible in the session before the first failed command;
session-scoped; severity + remedy; replaceable/dismissable (a fixed environment
must not keep the old warning); non-fatal (no turn cancelled, no tool result
changed). The host keeps the last value per
(session, id)for reconnect andreplay.
Nothing here is model-facing: producers that also want the model to see the
advisory keep their runtime-context entry. The seam is presentational.
Full context, current workaround and the plugin's use of it:
docs/UPSTREAM-SESSION-NOTICE.mdinBig-Dao/dsh-plugin-wsl-env.All reactions