Projects stay where you put them
You select the project directory explicitly. Recent projects can be restored; changing the active document changes editing focus without switching the project or clearing the conversation. Automatic .chippo creation when opening files is retained.
.chippo stores project requirements and metadata. It does not move CAD files into a separate input directory. Project rules live in .chippo/rules.md.
Task targets
A task binds the document, configuration and in-context assembly edit target. A mismatch before execution should stop that operation to avoid changing the wrong model. To work on another object, stop the task, check the target and send a new request.
A project is not an extra execution gate
After selecting a project, you can inspect the current object, capture screenshots and execute tasks without configuring a separate specification scope. Legacy policy files are no longer read; a missing policy file does not block CAD tools.
Continue organizing specifications and standard parts according to engineering conventions. The current version does not enforce specification-directory isolation or read-only libraries. Existing assembly references do not imply a user request to modify their source files.
General C# execution and screenshots remain the core tools. Risk confirmation addresses concrete dangerous actions, while document binding helps prevent work on an unintended object. Neither provides a filesystem sandbox for arbitrary code.
Read current limitations for the boundaries enforceable at runtime.