Agentic AI Atlasby a5c.ai
/
GitHubDocsDiscord
iiRecord
Agentic AI Atlas · GAP-SESSION-001: Session-to-Run One-to-Many Relationship
page:docs-harness-features-backlog-gaps-session-management-gap-session-001a5c.ai
II.
Page reference

page:docs-harness-features-backlog-gaps-session-management-gap-session-001

Reading · 1 min

GAP-SESSION-001: Session-to-Run One-to-Many Relationship reference

Model sessions as containers for multiple runs. A session represents a user intent; runs are individual orchestration attempts. Enable session continuity across runs.

Pagewiki/docs/harness-features-backlog/gaps/session-management/GAP-SESSION-001.mdOutgoing · 0Incoming · 1

GAP-SESSION-001: Session-to-Run One-to-Many Relationship

FieldValue
Categorysession-management
PriorityCritical
EffortL
StatusMissing

Description

Model sessions as containers for multiple runs. A session represents a user intent; runs are individual orchestration attempts. Enable session continuity across runs.

Current State

Session binds to single runId via YAML frontmatter. No multi-run sessions.

Target State

Sessions contain multiple runs. Session state persists across runs. Session history browsable. Runs within a session share context and accumulated knowledge.

Dependencies

  • None (foundation gap for session management)

Key Files

ComponentPath
Session managementpackages/sdk/src/session/
Run directory.a5c/runs/

Recommendation

Phase 1 implementation. Extend session schema to track multiple runIds. Add session:list-runs command. Preserve session context across run boundaries.