Docs › Studio › Studio on your computer
Code bases and components
For work beyond small apps: let your AI work in a real project's folder from a space, and keep shared pieces of code as tested components your apps use.
A space's code base
A space can be tied to a folder of code: a project on this computer, or on a server you reach with SSH. Open the space's Code tab, or choose ⋯ → Code base….
- Point Studio at the folder. Give the machine (empty for this computer) and the folder's whole path, then press Look at it. Studio says what it found, such as a Python or C++ project and its git branch.
- Add the project's commands, one per line as Name: command. For example, Test: pytest -q.
- Press Use this code base.
Then you have a chat with your AI working in that folder.
- It leaves its changes for you to review. Nothing is committed, pushed or deployed unless you ask.
- Changed files are listed, each with ↗ (open in VS Code) and Revert.
- Git: Commit…, Push, New branch….
- Your commands show as buttons. A failure offers Ask the AI to fix it.
- File references the AI names (file:line) open VS Code at that line.
- ⋯ has Open in VS Code and Continue a conversation from VS Code….
Components
Components are pieces of code your apps and services are built from: a feed handler, a framework, a calculator. Each has its code, its tests and a README. Find them under Apps → Components.
- Libraries. New library…, Add a folder… you already keep code in, or Add from git…. A library can be shared with a team through git, with Pull and Commit & push….
- A component:
- its version and tests;
- Build: a chat where the AI changes only this component, writes tests for each change, runs them and raises the version;
- Run tests and Code;
- Used by lists the apps holding a copy.
- Use in an app… gives one of your apps a copy, pinned to the current version.
- Update everywhere runs the tests first, then updates every app that uses it.
C++ workspaces
Add a C++ workspace… takes a folder or a .code-workspace file. Studio proposes the build and test commands; check
them and confirm. Each module then has its own Build chat and Build & test.