Skip to content

Projects and Workspaces

A project identifies the repository or folder you are developing. Its selected workspace/environment determines where tools execute. The session retains its associated working context.

Open the right project

Use Open existing project, Open Folder, or Add under Projects on desktop. In VS Code, open the folder using the editor’s workspace controls. For conversation without an existing repository, setup’s Start chatting opens a conversation without creating a project folder.

Opening a folder gives AlphaBase a working location and access governed by tools and permissions. It does not automatically send every file to the model. Attach or reference the relevant material when explaining a task.

Organize a large codebase

Keep source, tests, dependencies, and configuration in the project’s established structure. Use deliverable or export folders for finished output that needs review or sharing. Putting everything in a deliverable folder cannot replace repository structure, version control, tests, or a configured execution environment.

Before accepting a task as complete, inspect the actual output and recorded outcome. A plan file is useful work context, but not proof that the requested application is finished.

Select, transfer, and archive environments

Use the Environment selector or workspace controls to inspect supported local and remote environments. Project defaults and session-specific selections can differ. Check the selected location before running commands or changing files.

A Git worktree, where offered, is a separate checkout; uncommitted changes are not automatically copied to it. For a transfer or copy, review the target and verified result before switching. Move active project/session bindings before archiving a workspace. Archiving and permanent removal are different actions; retain important managed output before permanent removal.

Connections can be shared across projects on the same host and account, while local paths, project rules, and tool availability still differ. A different account, profile, or environment can need separate authorization.