Ettore Di Giacinto 3edcec1813 feat(studio): let the owner allow acts for triggers proposed from a chat ...

A trigger proposed from Slack or Telegram was always read only, and
the person had no way to let its runs act except to edit the trigger
on the Triggers page afterwards.

The approval of a binding now has an acts list, the act.* permissions
that a proposal from its chats may carry. It is empty by default, so
nothing changes until the owner sets it. It is stored in the same
approval JSON (no migration), checked against the closed list in the
API, and always limited to what the agent holds.

The acts of a proposal are what the model asks for, within the list of
the binding and the grants of the agent. The rest is dropped and
named in the proposal text, and the model is told which acts it may
ask for and to ask the person first when the job changes things. A
read only proposal now says what the person can do next.

For a proposal with acts, auto_readonly still asks. auto starts it at
once only when every act is allowed for the binding, nothing was
dropped and every sender of the turn is paired; otherwise it asks. A
trigger made without asking also keeps to the acts of its binding at
run time.

Assisted-by: Claude:claude-sonnet-5-5

2026-11-04 10:17:23 +00:00

..

gate.go

feat(chats): server-side chats with steering, sub-agents and compaction (#12918)

2026-11-01 12:08:23 +01:00

tools.go

feat(studio): let the owner allow acts for triggers proposed from a chat

2026-11-04 10:17:23 +00:00