# feat\(server\): a full-access link is not fenced · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/e0f3f6a217a000886e1212ef8bbdb03ad14353ed)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: e0f3f6a217a000886e1212ef8bbdb03ad14353ed

Requested commit: e0f3f6a217a000886e1212ef8bbdb03ad14353ed

Commit: e0f3f6a217a000886e1212ef8bbdb03ad14353ed

Tree: 3e7e0a02b76586bbb266e63098215629bf58e592

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
feat(server): a full-access link is not fenced

A link's agents run as the receiving environment's user, so at full access
the fence only ever stopped T3's own tools, never what the agent could do.
It also kept a host from driving machines it fully trusts: answering a
pending question or steering a thread the user started there, updating a
project, or running the project's setup script in a worktree it launched.

The stamp now records the access the link was paired with, and only a link
below full access is fenced. Its work still carries linkOrigin, so clients
keep showing where it came from. Stamps from before access was recorded stay
fenced.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

```

## Parents

- [f001f2f2de73db9a4a78866902fe2ae26cc9dfba](https://git.cafe/pingdotgg/t3code/commit/f001f2f2de73db9a4a78866902fe2ae26cc9dfba?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/e0f3f6a217a000886e1212ef8bbdb03ad14353ed?format=markdown)