Repository knowledge
Repositories are a special kind of knowledge source because source code has structure, relationships, and change history that ordinary document retrieval can miss. Starfire’s repository-intelligence direction is designed to make codebases useful across chat, Project OS, Knowledge, and FORGE.What repository context can help with
- locating where a feature is implemented
- understanding module boundaries
- tracing imports and dependencies
- finding configuration and environment expectations
- reviewing patterns across a codebase
- preparing a change plan
- grounding a FORGE build or repair job
Repository context is not a code dump
For a large repository, sending every file to a model is inefficient and can reduce answer quality. Repository intelligence can combine file metadata, search, retrieval, and task-specific selection.Branch and revision awareness
Code answers are only as current as the repository state being inspected. A useful repository integration should make the relevant branch, revision, or source snapshot clear when that matters.Private repositories
Repository access must follow the permissions of the connected source and the Starfire project or organization using it.FORGE integration
FORGE can use repository intelligence to understand an existing codebase before generating, editing, validating, or repairing files. That makes a repository-backed repair workflow fundamentally different from asking a generic model to guess how an unseen project is structured.Repository Intelligence in FORGE
Learn how repository context supports build and repair workflows.