Why Context Files Matter
Without context, the AI plans in a vacuum — it makes assumptions about your architecture, naming conventions, and existing services that may be completely wrong for your codebase. With the right context files attached, it plans with the same background knowledge a senior developer would have. A plan built with context files will:- Reference existing services and patterns correctly instead of suggesting new ones
- Respect your team’s coding conventions and style
- Identify real dependencies rather than theoretical ones
- Produce an export that a coding agent can execute accurately on the first attempt
Attaching Files to a Session
- Open a session and click the File panel icon (usually in the right sidebar or bottom toolbar)
- Click Upload or drag and drop files into the panel
- Files are uploaded to the cloud and attached to this session immediately
- The AI will have access to all attached files in subsequent messages
The File Panel
The file panel (right side of the session) has two tabs:
Both are shown in the same panel for easy access.
Browsing and Previewing Files
Click any file to preview it inline. Brunel supports inline viewing for:- Plain text and Markdown — rendered directly in the panel
- Code files — syntax-highlighted preview
- Word documents (
.docx) — inline document viewer - Spreadsheets (
.xlsx) — inline spreadsheet viewer
Planning Documents (Agent-Written Files)
As the planning agent works through your session, it writes structured documents to the Planning tab — business requirements, technical design, acceptance criteria, and more. These documents are the primary output you hand off to your coding agent. To export planning documents:- Download individually — click any file in the Planning tab to preview it, then use the download icon to save it locally
- Download as ZIP — click the Archive icon in the Planning tab header to export all planning documents as a single ZIP file