Recently, I’ve been extensively using the opencode/claude code combination for development and have explored three particularly useful tools.

They address several issues:

1. Parallel development on a single server; controlling tmux: tmux and tmux-mcp
2. Preventing claude code from stopping at meaningless points: ralph-loop
3. End-to-end automated testing: playwright mcp

Tool List

tmux mcp

First, configure tmux in the Linux environment with opencode, then have opencode install https://github.com/rinadelph/tmux-mcp.git. Once installed, you can use oc to control tmux content.

This method can be used to reactivate stopped opencode sessions. For example, you can open multiple tmux sessions and have one opencode monitor, start, and stop tasks through the tmux tool.

ralph-loop

Ralph is an autonomous AI agent loop that repeatedly runs Amp until all PRD items are completed. Each iteration creates a brand new Amp instance with a clean context.

Ralph likely originated from here: https://github.com/snarktank/ralph

Due to its effectiveness (which actually occurred after further improvements in model performance), it was also introduced to claude code.

Ralph-loop is a Claude Code plugin that allows Claude Code to automatically restart when tasks are completed, forming a loop execution mechanism. This is particularly useful for tasks that require continuous improvement or iteration.

Installation Method

1. Install through Claude Code official plugin market:

   • /plugin install ralph-wiggum@claude-plugins-official or cc '/plugin install ralph-wiggum@claude-plugins-official'

2. Configuration and Usage:

   • After installation, you can start it in Claude Code via the /ralph-loop command
   • Set tasks and termination conditions, Claude Code will automatically restart each time it stops
   • This is particularly useful for scenarios requiring multiple iterations of code improvement, debugging, or testing

Use Cases

• Code Refactoring: Have Claude Code continuously improve code quality
• Test-Driven Development: Write tests, then have Claude Code continuously improve implementations
• Debugging Loops: Automatically restart debugging sessions
• Continuous Integration: Simulate CI/CD processes locally

The drawback of this plugin is that it consumes a lot of tokens; without a max20 subscription, it’s better not to use it. However, for tasks requiring high-quality output, this tool can significantly improve work efficiency.

playwright mcp

This plugin can launch browsers to complete end-to-end testing or write end-to-end test code. It can better form loops to have cc or oc improve code.

Installation method: claude 'help me install playwright mcp'

Rewriting as Agents

I recommend directly rewriting these tools and MCPs as agents through opencode or claude code.

Compared to skills commands, these tools are more suitable for invocation through agents. Agent context is very clean, making tool invocation almost inevitable.

Summary

As LLMs become increasingly powerful, numerous MCPs that rely on LLM capabilities naturally gain improvements. Tools that weren’t very useful before become more effective. This aligns with the saying: “Don’t build things that become meaningless after large model capability enhancements.” Large model capabilities continue to improve, and prices keep decreasing.

I believe the next step is to bridge interactions between different modalities and tools, as well as endowing tools with large model capabilities, which is one of the inevitable development directions for agent engineers.