feat(secrets): audit log surfaces agent type/instance per read (TOK-4) #787
No reviewers
Labels
No labels
area:agents
area:dashboard
area:database
area:design
area:design-review
area:flows
area:infra
area:meta
area:security
area:sessions
area:webhook
area:workdir
security
type:bug
type:chore
type:meta
type:user-story
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
charles/claude-hooks!787
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "dev/760"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds
agent_typeandagent_instancecolumns tosecret_access_logso operators can answer "why did agent X read this secret?" directly from the dashboard.Test plan
dev-defaultanddev-2; open access log for any shared secret → confirm both instances appear with correctagent_type=devandagent_instancelabelsdev→ only dev reads shown; filter by Instance=dev-2→ only dev-2 reads shownnullfor both columns — they still render normally viaaccessed_byGET /secrets/:name/access-log?agent_instance=dev-2returns only dev-2 rowsCloses #760
Migration idempotent, columns derived write-time via
deriveAgentCols(bothagent-env-sync:andagent_type:patterns handled). Filter logic inlistSecretAccessLogcorrect. Frontend mutual-exclusion between type/instance selects works. CI green. AC met.