Real-Time Collaborative Coding in GoCodeMe IDE
GoCodeMe IDE supports real-time collaborative editing, letting multiple developers work on the same codebase simultaneously—similar to Google Docs for code. This guide explains how to start, manage, and get the most from collaboration sessions.
Starting a Collaboration Session
- Open your project in GoCodeMe IDE.
- Click the Collaborate icon in the left sidebar (two overlapping cursors).
- Select Start Session. A unique session link is generated.
- Share the link with your collaborators via chat, email, or Alfred ("Alfred, invite team to this session").
Joining a Session
Collaborators click the shared link, which opens GoCodeMe IDE in their browser. They are prompted to authenticate with their GoSiteMe account. Guest access can be enabled in Settings → Collaboration → Allow Guests, though guests receive read-only access by default.
Permissions & Roles
| Role | Capabilities |
|---|---|
| Owner | Full read/write, terminal access, can manage roles |
| Editor | Read/write access to files |
| Viewer | Read-only access, can leave comments |
Assign roles from the Participants panel on the right sidebar.
Features During Collaboration
- Live cursors: Each participant's cursor is displayed in a unique color with their username label.
- Follow mode: Click a participant's avatar to follow their cursor and scroll position.
- Integrated chat: A chat panel lets you discuss changes without leaving the IDE.
- Shared terminal: The session owner can share terminal access with editors for running builds and tests together.
- Conflict resolution: GoCodeMe uses operational transformation (OT) to merge concurrent edits seamlessly.
Best Practices
- Use branching to isolate experimental changes during pair programming.
- Commit frequently so the Git history reflects individual contributions.
- Limit shared terminal access to trusted collaborators for security.
- End the session when finished to free server resources.
Troubleshooting
If a collaborator cannot connect, ensure they are on a network that allows WebSocket connections (port 443). Corporate firewalls occasionally block these. Switching to a different network or using a VPN usually resolves the issue.