Tinker
Resources
Agent logs
Agent memories
Agent sessions
Agent terminal logs
Agents
Comments
Epics
Projects
Proposals
Tickets
Avo user
Resources
Agent logs
Agent memories
Agent sessions
Agent terminal logs
Agents
Comments
Epics
Projects
Proposals
Tickets
Avo user
Home
Epics
Part 2: Agent Session Logs - Store terminal output persistently for replay
Edit
Part 2: Agent Session Logs - Store terminal output persistently for replay
Cancel
Save
Title
*
Project
*
Choose an option
alpha
tinker
Create new project
Description
## Scope Create database models and storage for agent terminal output logs. ## Changes Required ### New Models ```ruby # AgentSession - Represents a single agent run # Fields: agent_id, started_at, ended_at, status (running/completed/failed) class AgentSession < ApplicationRecord belongs_to :agent has_many :terminal_logs, dependent: :destroy end # AgentTerminalLog - Individual lines # Fields: agent_session_id, timestamp, output_line, line_type (stdout/stderr) class AgentTerminalLog < ApplicationRecord belongs_to :agent_session end ``` ### Log Storage - Agent-bridge writes to log file in container - Rails ingests logs on session end or periodically - Alternatively: Stream directly to Rails during session ### Cleanup - Scheduled job to purge logs older than 7 days - Configurable retention period ## Acceptance Criteria - All terminal output stored in database - Queryable by agent, time range, ticket - MCP tool to retrieve historical logs - Automatic cleanup of old logs
Avo
· © 2026 AvoHQ ·
v3.27.0
Close modal
Are you sure?
Yes, I'm sure
No, cancel
