Codebase context

Context is the product. The agent gathers it with structured file reads, grep/glob, patch-aware edits, and semantic/codebase search over an index of your workspace.

Search and index

Eyeban maintains search indexes that support:

• Semantic / codebase search for conceptual queries
• Grep-style text search for exact strings and patterns

Re-open or refresh the folder if the tree changed drastically and results look stale.

Ignore files

Control what is indexed and offered as context with:

• .eyebanignore for Eyeban-specific excludes
• Standard .gitignore patterns (respected alongside Eyeban ignores)

Built-in ignores typically cover noisy or sensitive trees such as node_modules, .env files, and common build / output directories. Add project-specific patterns for generated assets and large vendor trees.

Rules

Place durable instructions in .eyeban/rules/*.mdc. Rules steer style, architecture constraints, and project conventions for agent runs. Prefer checked-in rules when the whole team should share the same guidance.

Optional legacy instruction files some editors use may also be present in a repository; prefer documenting and maintaining .eyeban/ paths as the primary source of truth.

Skills

Skills live under .eyeban/skills and package repeatable procedures the agent can follow. Keep skill text specific and actionable.

AGENTS.md

An AGENTS.md at the project root (when present) supplies high-level agent-facing project guidance. Treat it as team-visible documentation, not a place for secrets.