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

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

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

Visibility: public

Requested revision: e7be3191310fe8c8ee8493338a2e98665a999d4d

Requested commit: e7be3191310fe8c8ee8493338a2e98665a999d4d

Commit: e7be3191310fe8c8ee8493338a2e98665a999d4d

Tree: abf160eb6d14a5cb780f8c2adcf51cb8cecf7c21

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

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

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