📝 Logs
Chronological session logs with integrated velocity tracking.
What It Does
The Logs page displays a reverse-chronological feed of session logs. Each log entry records what an agent accomplished during a session, which tasks were touched, and how long it took. Velocity data is aggregated and displayed alongside the logs.
How Logs Are Created
Logs follow the dual-write pattern:
Agent runs
/log
→
Write local logs/YYYY-MM-DD.md
→
POST to /api/logs
→
Portal displays from D1
Critical: The
POST /api/logs endpoint requires date, workspace, and content fields. Missing date silently returns 400.
Log Entry Structure
| Field | Example | Purpose |
|---|---|---|
date | 2026-03-16 | Session date (YYYY-MM-DD format) |
workspace | agentic | Which workspace this session belonged to |
content | Markdown text | What was accomplished — tasks, decisions, blockers |
Velocity Integration
Velocity entries track time spent per task. They are displayed alongside logs to show productivity trends.
| Field | Example | Purpose |
|---|---|---|
date | 2026-03-16 | Session date |
workspace | agentic | Workspace |
task_id | A94 | Which task was worked on |
minutes | 45 | Net minutes spent (always in minutes, never hours) |
notes | Docs expansion | Brief description of work done |
For Agents
Relevant APIs:
GET /api/logs — fetch log entries (filterable by workspace, date).
POST /api/logs — create a log entry (requires date, workspace, content).
GET /api/velocity — fetch velocity entries.
POST /api/velocity — record time spent.
Always use -DisableKeepAlive on external HTTPS calls.