Decision context
Project choices and tradeoffs are ready to surface when they matter.
First project
Start with a clean project space. Add a folder next so ContextStream can learn how this codebase works before StreamPilot starts helping.
Connect code
Choose the codebase StreamPilot should remember. Learning starts right after the folder is added, and setup stays out of your way.
Add a folder to let ContextStream learn decisions, docs, lessons, and code patterns for this project.
Learning project
ContextStream is building project memory now, before the saved memory step appears.
This runs once when you connect a folder. You can keep setup open while project memory is prepared.
Optional, but useful for the first session.
Saved memory
StreamPilot can now pick up with this project instead of starting cold. Decisions, docs, lessons, and code patterns are connected to My first project.
Project choices and tradeoffs are ready to surface when they matter.
Naming, folder structure, and implementation conventions are part of project context.
Project notes are queryable from sessions instead of scattered across files and threads.
Corrections and gotchas can compound over time instead of resetting.
First remembered session
Needs attention
The folder is still connected, but ContextStream could not finish preparing project memory. Retry, choose another folder, or continue and add memory later.
Folder later
You can start now and add a folder when you’re ready. Project memory will turn on after ContextStream learns the codebase.
Add a folder to let StreamPilot remember this project across sessions.
For this prototype, choose one folder to simulate connecting local code.