board_log_activity
Log arbitrary observations, decisions, or blockers to the write-only audit stream. Use for free-form comments or context that must persist across agent sessions.
Instructions
Append an entry to the activity_log — a write-only audit stream of what agents did, decided, or observed. Use this for: RESEARCH observations the next session should see, decisions made during PLAN/REVIEW, blockers, notable failures, or any context that shouldn't be lost. Most status/assignment changes via board_update_task and board_create_task already write their own activity_log entries automatically — call this explicitly for free-form comments (action='commented') or arbitrary actions. Read back via board_get_activity. Returns { id, action, message }.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| agent_name | Yes | Name of the agent (free-form string — e.g., 'main', 'code-reviewer', 'gcp-infra'). Used for filtering and audit. | |
| action | Yes | Action type. Fixed enum. Most values correspond to lifecycle events written automatically by other tools; use 'commented' for free-form notes/observations logged manually. | |
| details | No | Human-readable description of what happened. Required in practice for 'commented' — without it, the entry is empty. | |
| task_id | No | Related task ID if this activity is about a specific task. Enables filtering via board_get_activity(task_id=...). Omit for project-level or session-level events. | |
| session_id | No | Related session ID if this activity is scoped to a specific session. Enables filtering via board_get_activity(session_id=...). | |
| metadata | No | Optional structured payload (e.g., { commit_sha: 'abc123', build_id: 'build-456' }). Stored verbatim, not indexed. |