Skip to content

Context budget: large workspace metadata snapshot injected per session #450

@JustAGhosT

Description

@JustAGhosT

Problem

Each session starts with a full workspace snapshot including:

  • Git status, recent commits, branch info
  • Full repo metadata (file counts, structure)
  • Conversation summary from prior sessions
  • Memory index contents

For large monorepos like mystira-workspace (.NET + TS + Rust, 76+ projects), this snapshot is expensive.

Proposed Solutions

  1. Scoped metadata — retort should support a .retort/context-scope.yaml that defines which parts of the repo are relevant to the current work stream. A backend developer doesn't need frontend file counts.
  2. Compressed repo summary — instead of raw git status + file listings, generate a semantic summary ("3 modified files in apps/app, on branch dev, last commit: feat X").
  3. Session hooks for context pruning — retort's SessionStart hook could strip irrelevant metadata before it enters the context window.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions