This document describes how to manually verify the plugin works correctly in OpenCode.
- OpenCode installed (version >= 1.0.0)
- Node.js >= 18.0.0
- This plugin built and ready to install
npm install -g opencode-cline-modeThen add to your OpenCode config (~/.config/opencode/opencode.json):
{
"plugin": ["opencode-cline-mode"]
}# Build the plugin
npm run build
# Symlink to OpenCode plugins directory
ln -s $(pwd) ~/.config/opencode/plugins/opencode-cline-modeImportant: When using local installation, do NOT add to plugin array in config.
Steps:
- Start OpenCode:
opencode - Press
Tabto see available agents
Expected Result:
- You should see only 2 agents:
cline-plan- Planning modecline-act- Execution mode
- Default OpenCode agents (plan, build, etc.) should NOT be visible
Evidence: Screenshot of agent list
Steps:
- Start OpenCode with cline-plan:
opencode --agent cline-plan - Ask the AI to analyze a file: "Read package.json and tell me the project name"
- Try to ask it to edit a file: "Add a new dependency to package.json"
Expected Result:
- Reading files should work: AI successfully reads and analyzes package.json
- Editing should be blocked: AI should refuse to edit or explain it cannot modify files
Evidence: Chat logs showing successful read and refused edit
Steps:
- Switch to cline-act: Press
Taband selectcline-act - Ask the AI to create a test file: "Create a file test.txt with content 'hello world'"
Expected Result:
- AI should be able to create the file
- Bash commands should ask for permission (if configured to
ask)
Evidence: Chat logs showing successful file creation
Steps:
- Start with cline-plan agent
- Ask: "Analyze the project structure and create a plan to add a new feature"
- Wait for the plan to complete (you should see "📋 Plan Complete!" notification)
- Switch to cline-act agent: Press
Taband selectcline-act
Expected Result:
- The first cline-act message should contain:
- "📋 Inherited Plan from cline-plan" header
- The full plan content from cline-plan
- "Starting step-by-step execution..." footer
Evidence: Chat logs showing plan inheritance
Steps:
- In cline-plan mode, create a plan
- After plan completion, type:
/start-act - The tool should execute
Expected Result:
- Tool executes without requiring approval
- Message: "🚀 Switching to Execution Mode"
- Instructions to press
Taband selectcline-act
Evidence: Chat logs showing /start-act execution
Steps:
- In cline-plan mode, try to use
write_to_fileorexecute_command - In cline-act mode, try to use
execute_command(should ask permission)
Expected Result:
- cline-plan: Edit/bash commands are denied
- cline-act: Edit allowed, bash asks for permission
Evidence: Chat logs showing permission enforcement
Fill in after running tests:
- Test 1: Plugin loads - Only cline-plan and cline-act visible
- Test 2: cline-plan read-only mode works
- Test 3: cline-act full access mode works
- Test 4: Plan inheritance works when switching agents
- Test 5: /start-act tool works
- Test 6: Permission enforcement works correctly
Symptom: Default agents still visible
Solutions:
- Check
~/.config/opencode/opencode.jsonhas"plugin": ["opencode-cline-mode"] - Check plugin is installed:
npm list -g opencode-cline-mode - Check OpenCode version:
opencode --version(must be >= 1.0.0)
Symptom: Switching to cline-act doesn't show plan
Solutions:
- Make sure you completed a plan in cline-plan first
- Check the transform hook is registered (check logs)
- Verify message structure in debug mode
Symptom: Typing /start-act doesn't work
Solutions:
- Make sure
enable_execute_command: truein config - Check tool hook is registered
- Try using
Tabto switch agents manually
If tests fail:
- Save chat logs showing the failure
- Note OpenCode version:
opencode --version - Note plugin version:
npm list -g opencode-cline-mode - Create issue at: https://github.com/trry-hub/opencode-cline-mode/issues
Include:
- Which test failed
- Expected vs actual behavior
- Chat logs
- OpenCode and plugin versions