Team Collaboration Workflows

Set up OpenCode for team use. Learn configuration sharing, role-based access, collaborative patterns, and how to maintain consistency across your development team.

Why Team Configuration?

Benefit	Description
Consistency	Same behavior across team
Knowledge sharing	Shared skills and prompts
Security	Controlled permissions
Auditability	Track AI usage

Version Control Strategy

your-project/
├── .opencode/
│   ├── config.json          # ✅ Commit (team config)
│   ├── skills/              # ✅ Commit (shared skills)
│   └── memory/              # ❌ Don't commit (personal)
├── opencode.json            # ✅ Commit (legacy format)
└── .env                     # ❌ Don't commit (secrets)

.gitignore

git

# OpenCode
.env
.opencode/memory/
.opencode/sessions/
*.log

Shared Configuration

Create .opencode/config.json:

json

{
  "$schema": "https://opencode.ai/config.json",
  "agents": {
    "default": {
      "model": "gpt-4o",
      "description": "Team coding assistant"
    }
  },
  "permissions": [
    {
      "tool": "bash",
      "allow": ["npm *", "git *", "pytest *"],
      "deny": ["sudo *", "rm -rf /"]
    }
  ],
  "skills": {
    "code-review": {
      "manifest": ".opencode/skills/code-review/skill.yaml"
    }
  }
}

Role-Based Configuration

Different Roles, Different Configs

Create role-specific config files:

bash

.config/
├── opencode-developer.json
├── opencode-reviewer.json
└── opencode-lead.json

Usage

bash

# Developer mode
opencode --config .config/opencode-developer.json

# Reviewer mode
opencode --config .config/opencode-reviewer.json

Shared Skills

Create Team Skills

.opencode/skills/
├── code-review/
│   ├── skill.yaml
│   └── skill.md
├── api-design/
│   ├── skill.yaml
│   └── skill.md
└── testing/
    ├── skill.yaml
    └── skill.md

bash

git add .opencode/skills/
git commit -m "Add team skills"
git push

Collaborative Patterns

Code Review Workflow

💡 Tip: Use Ctrl + Mouse Wheel to zoom, or click the fullscreen icon

Pair Programming

> Switch to pair mode
> Load shared project context
> Let's work on the authentication module together

Knowledge Transfer

> Summarize our architecture decisions into a memory file
> Create a guide for new developers

Security Best Practices

Permission Isolation

json

{
  "permissions": [
    {
      "tool": "bash",
      "allow": ["npm test", "npm run lint"],
      "deny": ["npm publish", "git push --force"]
    },
    {
      "tool": "write",
      "allow": ["src/**", "tests/**"],
      "deny": [".env", "secrets/**", "*.key"]
    }
  ]
}

Secrets Management

Practice	Implementation
Use environment variables	`${API_KEY}` in config
Never commit secrets	Add .env to .gitignore
Rotate regularly	Update keys monthly
Audit access	Log all API calls

Monitoring and Auditing

Enable Logging

json

{
  "logging": {
    "enabled": true,
    "level": "info",
    "file": "opencode-audit.log"
  }
}

Track Usage

bash

# View audit log
tail -f opencode-audit.log

# Search for specific actions
grep "bash" opencode-audit.log

Onboarding New Team Members

Checklist

Clone repository
Install OpenCode
Copy .env.example to .env
Add API keys
Run opencode to verify

Documentation

Create docs/opencode-setup.md:

markdown

# OpenCode Setup

## Prerequisites
- Node.js 18+
- API key from OpenAI or Anthropic

## Setup
1. npm install -g opencode
2. cp .env.example .env
3. Add your API key to .env
4. opencode --version

## Usage
- `opencode` - Start interactive session
- `opencode run "task"` - Run single prompt