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
Commit ee5bbde
Browse filesBrowse the repository at this point in the historyBrowse files
feat(server): work a linked environment starts stays within its link
A link's T3-Mode-Limit caps the modes of what it starts, but within those
modes it could still steer the user's own threads or change this
environment's projects and settings. Work a link starts is now fenced to
that link.
The linking side registers its OAuth client with the t3code-peer-link
software id; the receiving side signs that into the session's claims. Every
thread such a session launches carries an immutable linkOrigin, and so do
the subagents, forks and create_threads it derives. A client's own
thread.create cannot set one.
In the shared access declarations, a linked caller may change only threads
of the same link, and may not use writesEnvironment tools (projects,
settings), schedule tasks, or change scheduled tasks. Reads are not fenced.
Setup scripts are skipped for stamped threads in ProjectSetupScriptRunner,
which every path that runs them goes through.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
message: `Thread ${refusal.threadId} now runs in ${refusal.runtimeMode}/${refusal.interactionMode} mode, above this caller's. Its user changed it while this call ran.`,
210
232
});
211
233
212
-
/** The modes a started thread runs with: those requested, else the caller's own. */
234
+
/** How a thread starts: the modes requested, else the caller's own, and the link it is for. */
213
235
exportinterfaceStartedModes{
214
236
readonlyruntimeMode: RuntimeMode;
215
237
readonlyinteractionMode: ProviderInteractionMode;
238
+
/** The linked environment the caller acts for. The thread must carry it. */
0 commit comments