Compact Directory Path Listing (Flat Paths over Visual Trees)

Overview

When exploring a repository structure, naive agents frequently run commands like tree or generate nested Unicode ASCII branch diagrams (├── src/, │ └── components/, │ └── Button.tsx).

Visual ASCII trees suffer from severe token inefficiencies:

1. Tokenizer Fragmentation: Unicode branch glyphs (│, ├, ─, └) and leading whitespace consume 4 to 6 separate tokens per line.
2. Ambiguous Relative Paths: The model must reconstruct full paths by mentally tracing nested indentation levels, leading to file-not-found tool call errors.
3. Vendor Directory Bloat: Unbounded tree commands dump thousands of lines of node_modules, .git, and venv into context.

The Compact Path Listing Protocol replaces visual tree graphs with flat, slash-delimited relative path streams, cutting token consumption by 75% while providing unambiguous paths ready for instant tool invocation.

Visual ASCII Tree vs. Compact Flat Paths