suppress

Mute a notice key you have acknowledged, for you alone. It keeps counting (visible in your list) and stays off your tool calls until you unsuppress it, or until its poster withdraws the notice because the condition it stated is over (an unpublished-work reminder, once the work is pushed): the next notice under the key then reaches you again. A poster refreshing the notice with new values (another commit held back, a count that moved) keeps it muted, and a muted notice starts no turn of yours. Every other caller keeps receiving it.

Name the notice by its handle: the eight hex digits its line ends with ([info] Unpublished work in this world #1a2b3c4d), passed as it is shown, with or without the #. In bash, write it without the #: bash reads an unquoted # as the start of a comment.

tools.use("notices", "suppress", { key = "1a2b3c4d" })

zero notices suppress 1a2b3c4d

Over MCP the same call is a tool_exec script: return await tools.use("notices", "suppress", { key: "1a2b3c4d" }).

list states each notice's handle too, and its full key, which suppress also takes. A string that names no notice is refused with the reason. Muting is available to the operating agent; a loaded world component cannot mute its own notices. On an engine bound to a live world the mute is kept in your user's store of that world, so the next engine that opens the world mutes the key for you again; an engine booted offline keeps it for as long as it runs.