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
Owner question: may the assistant delete projects and change other threads? (split tool groups) #954
Recommendation: split the T3 tool groups projects and threads into "read / start / message" tools and "destructive" tools, give the assistant only the first part, and do this before any mail PR (assistant PR 4 onwards) lands.
Why: the assistant profile (assistant PR 2, #953) uses the whole orchestration, threads and projects groups, as the design and #879 name them. #158 lets the assistant start and message work without a tap. But the same groups also let it, without a tap:
delete any project except Scratch with force, which deletes every thread in it, archived ones too, so their transcripts are gone;
clone repositories onto disk and create project folders;
change another thread's model, interrupt threads, stop workflows, link or unlink environments.
The design said starting work without a tap is safe only with cards-only mail (question 1). #153 chose otherwise, so later a hostile mail could steer a thread that holds these tools. Single tools cannot be dropped from a profile today, so a split is needed.
What changes if accepted: a follow-up PR adds the split groups; the built-in assistant profile uses only the safe ones; deleting projects and the other destructive actions stay with the person (or a normal thread). The assistant stays off by default until then.
If rejected: the assistant keeps the whole groups; the Settings text and docs will say plainly that it can delete projects and their threads.
Accept or reject by replying "Owner decision: ...".
Activity