Team Development

Operaide is built for teams. Every developer works in their own isolated Studio instance, so there is no interference between team members — yet you have two ways to collaborate: direct workspace sharing for quick reviews and Git-based workflows for independent parallel development.

Sharing a Workspace

Administrators can view and open any workspace in their organization directly from the Workspaces panel.

1. Navigate to Workspaces in the sidebar
2. Toggle Show all in org — this reveals every workspace across all team members
3. Click Open in Studio on any workspace to open it in a new tab

You are now working in your colleague's workspace. Any changes they make appear in real time, and any changes you make are immediately visible to them.

This is useful for:

• Code review — inspect a colleague's implementation directly in the IDE
• Pair programming — work together on the same codebase in real time
• Onboarding — guide new team members through an existing project
• Troubleshooting — help debug an issue in someone else's environment

note

Shared workspace access requires System Administrator permissions. For independent parallel development where each developer works in their own workspace, use Git-based collaboration as described in the next section.

---

Collaborating with Git

For teams that need to develop independently and in parallel, Git is the recommended approach. Each developer works in their own isolated workspace, and a shared Git repository keeps the codebase synchronized.

How It Works

Each developer creates their own workspace, clones the shared repository, and works on feature branches. Changes flow through the Git remote — never directly between workspaces.

Prerequisites

Before setting up Git-based collaboration, make sure the following is in place:

• A Git server accessible from all Studio instances — this can be any Git hosting: a self-hosted solution like Gitea or GitLab CE, a bare Git repository over SSH, or a cloud provider like GitHub or Bitbucket
• Network access — Studio needs outbound connectivity to the Git server (HTTPS on port 443, or SSH on port 22)
• Credentials — each developer needs authentication credentials for the Git server: a personal access token (PAT) for HTTPS, or an SSH key

tip

If your Operaide installation is behind a corporate firewall or proxy, your administrator may need to configure outbound access to the Git server. See the On-Premises Installation guide for proxy and network configuration details.

First Developer: Create and Share the Project

The first developer sets up the project and pushes it to the shared remote.

1. Create a workspace from a Starter Template in the App Store

2. Develop the initial version — write your code, test, and iterate until you have a working baseline

3. Add the remote — open the terminal and connect your workspace to the Git server:

   git remote add origin https://your-git-server.example.com/your-org/your-app.git
   git push -u origin main

The project is now available for other team members to clone.

Additional Developers: Join the Project

Every additional developer creates their own workspace and clones the shared repository into it.

1. Create a workspace from the same Starter Template — this gives you a Studio workspace entry to work from

2. Open the terminal and clone the shared repository as a new workspace:

   cd ~/workspaces
   git clone https://your-git-server.example.com/your-org/your-app.git operaide-app-my-project

3. Install dependencies in the cloned workspace:

   cd operaide-app-my-project
   npm install

4. Switch to the cloned workspace — go back to the Workspaces panel and open operaide-app-my-project

5. Optionally, delete the initial template workspace if you no longer need it

You now have your own independent copy of the project, connected to the shared Git remote.

Daily Workflow

Once every developer has their workspace set up, the day-to-day collaboration follows a standard feature branch workflow:

1. Pull the latest changes before starting new work:

   git checkout main
   git pull

2. Create a feature branch for your work:

   git checkout -b feature/my-feature

3. Develop, deploy, and test in your own workspace

4. Push your branch when ready:

   git push -u origin feature/my-feature

5. Open a merge request on your Git server, get a code review, and merge into main

For more details on Git operations in Operaide Studio — including branching, conflict resolution, and terminal commands — see Code Management with Git.

---

Network Requirements

Team development adds the following network requirements to your Operaide installation:

Service	Protocol	Port	Purpose
Git server (HTTPS)	HTTPS	443	Clone, push, pull via HTTPS
Git server (SSH)	SSH	22	Clone, push, pull via SSH (alternative)

If your Operaide instance runs behind a proxy, ensure the Git server is included in the proxy allowlist or the NO_PROXY environment variable. See the On-Premises Installation guide for full network and proxy configuration.