What Makes Coding Mode Different

Coding bots add repository-aware behavior on top of the same OpenCode session model used by conversation bots.

• Project context can be attached from the current OpenCode project.
• Referenced files can be looked up and inserted into the prompt.
• Coding plans can be returned as ocs-task cards.
• Approved commands can run through OpenCode session execution flows.
• Session diffs can be surfaced back into Mattermost.

API Boundaries

The plugin keeps coding mode inside OpenCode server capabilities. Project context, file lookup, search, shell, command execution, and diffs are routed through OpenCode APIs instead of hidden local filesystem execution in the plugin.

Recommended Bot Profiles

• implementer: for focused code changes
• reviewer: for change analysis and risk spotting
• triage: for reproduction, root-cause narrowing, and issue shaping
• release: for packaging and rollout checklists

Prompt Enrichment

Use workspace snapshots sparingly and keep referenced file limits tight. It is usually better to attach a few highly relevant files than to overload the model with a large repository dump.

Approval Flow

1. The bot returns a coding plan and optional commands.
2. The plugin renders a task card in Mattermost.
3. A user explicitly approves a safe command.
4. The result is reflected back into the same task context.