datatug / backend / 41875923147
100%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 418
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 99.995%. Remained the same
41875923147

push

github

web-flow 
feat(access): agents ask their user; own-agent decisions; agent registry (#154)

Perimeter AI-agent access, part 1 (D23, D25, D27, D28), on datatug-core v0.139.0 ([datatug/datatug-core#450](https://github.com/datatug/datatug-core/pull/450)). No protected-field reveal (DAS L3 later).

**Agents on their own account.** A person registers agents in a project (`POST/GET /v0/datatug/access/agents`, `POST agents/:id/disable`; stored at `spaces/{space}/ext/datatug/accessAgents/{id}`, IDs `ag-…`). The registrant is the agent's user. Agent routes take `X-DataTug-Agent: <id>`; without it the agent acts for the verified person. The agent runs with its user's CLI login and is always capped by that user.

**The agent asks its user.**
- `POST agent/requests`: self-request only (subject = requester = agent, `agentUser` server-set), at most 20 open per person per connection.
- `GET agent-requests`: the user's inbox, with `canApprove`, `canRefuse`, `canForward`, `agentUserLacksAccess`.
- The user declines (`access.refused`, `byAgentUser`), forwards (`POST grants/:id/forward`, `access.forwarded`; web sign-in only), or approves on the existing approve route by **authority** (delegation) or **access** (their fresh resolution covers the scope; `dataaccess.Covers`). Flagged `forOwnAgent`; `dormant` when they cannot read it now. An access-only approval runs at most the connection's default maximum.
- Production with self-approval off: `OWN_AGENT_SELF_APPROVAL_OFF`, and an existing own-agent approval goes inert while that floor holds.
- Approvers see and decide nothing until forwarded; they may revoke an approved one.

**Agent ⊆ user.** `ResolveAgentAccessWithExactSnapshot` returns the agent's own approvals with its user's fresh resolution (user grants redacted to scope and time); Core intersects them per table at every authorization, so a user's revocation reaches the agent within the 60 s lease (`AGENT_USER_LACKS_ACCESS`).

**Dormant → effective once.** At the agent's first... (continued)

56029 of 56032 relevant lines covered (99.99%)

1.0 hits per line

Jobs
ID Job ID Ran Files Coverage
1 41875923147.1 418
99.99
GitHub Action Run
Source Files on build 41875923147