Projects & parallel work

Choose a project

1. Switch to Neurion Code.
2. Open an existing project folder or create a new working folder.
3. State the task and identify the files or behavior that matter.
4. Review the task’s file and command scope before allowing implementation.

A project gives the task a working location. It does not authorize every path on the computer. Keep unrelated projects and private files outside the scope of the task.

For a repository you did not create, start with an explanation or review task. Inspect its instructions and setup steps before allowing commands that install dependencies or change your system.

Keep independent tasks separate

Use separate conversations for tasks with different goals. Each conversation retains its own history and task state. Conversations working in the same folder still see changes made to that shared folder.

A Git worktree provides a separate checkout for an independent coding change. Use one when two tasks should not write into the same checkout. A worktree separates files; it does not provide a separate computer or unlimited browser resources.

• Give each task a clear owner and scope.
• Avoid concurrent edits to the same files in one folder.
• Keep worktree changes until you have reviewed and applied the result.
• Check for running commands and shared services before deleting a working folder.

Review and apply changes

Inspect the changed files, diff, and validation results before applying worktree changes to your main project. Confirm which checks actually ran and which results remain unverified.

If the destination project changed during the task, resolve the conflict against its current state. Preserve your later edits and the task’s worktree until the combined result is clear.

A completed response is not a Git commit, merge, or deployment. Ask for those operations explicitly when you want them performed.

Files, results & history

Understand task permissions

• Previous Sign in & connect
• Next Your first task