Skip to the content
TEND is in beta.Limitations

TEND / Activity

A clear record ofeverything asked.

Who asked, what,and who decided.

Requests, decisions and rule changes go to an append-only log. Each entry is chained to the one before it, so a changed or removed entry shows up when the chain is checked.

Activity

Example

14:00 · repo-helper

Run: git push --force origin main

Needs approval
Decided by
Rule: Ask me first
Tool
shell.run
Hash
#e0b25d
Previous
#4a7f03

The activity log

Search the example log, filter by outcome, and open an entry to see what decided it.

How the log works

Activity

Example
  1. repo-helper · shell.run · Rejected
  2. support-bot · send_email.send · Approved
  3. research-agent · database.query · Blocked
  4. ops-agent · delete_record.delete · Blocked
  5. support-bot · read_ticket.read · Allowed
  6. repo-helper · shell.run · Needs approval
  7. ops-agent · pay_invoice.pay · Needs approval

Check the chain

Check the links, then change one entry and check again.

Read the limitations

Overview

Last 24 hours
Ran
102
last 24 hours
Waited for you
15
last 24 hours
Blocked
6
last 24 hours
Agents running
3
of 4

The day at a glance

What ran, what waited and what was blocked in the last 24 hours.

See Approvals

From your terminal

Read the log fromyour terminal.

List what TEND recorded for an agent, and check the chain. Keep the head hash somewhere outside TEND.

Read the docs
Terminal
$ npm run tend -- audit --agent "ops-agent" --last 3
2026-11-08 13:44:12  ops-agent: denied delete_record.delete C-311 (policy_denied)
2026-11-08 14:02:31  ops-agent: requested pay_invoice.pay 2026-118 (approval_required)
2026-11-08 14:03:05  ops-agent: a person approved a held request
$ npm run tend -- audit-verify
Audit chain intact: 7 event(s) checked. Head hash: 9c41e7…
Keep this hash outside TEND; a history rewritten later will not end in it.

Every tool call your agents make.Checked first.

Create an account
Dusk over forested hills