2026 – Deuts.NET

Why OpenCode Go Is Worth It — An Honest Take for Coders and Automators

I’ve been using OpenCode Go for about two weeks now, and it’s become my go-to for coding, AI agents, and automation. Here’s an honest take on whether it’s worth it.

What Is OpenCode Go?

A $5 first month, $10/month after subscription that gives you access to 13 top open coding models. No per-token charges — just a flat fee with usage limits.

Subscribe to OpenCode Go

The Models

DeepSeek — V4 Pro, V4 Flash
GLM — 5.2, 5.1
Kimi — K2.7 Code, K2.6
Qwen — 3.7 Max, 3.7 Plus, 3.6 Plus
MiniMax — M3, M2.7
MiMo — V2.5, V2.5 Pro (with vision!)

WordPress MCP Setup for Claude Code

The WordPress MCP Adapter plugin exposes a WordPress site as an MCP server. Combined with Automattic’s @automattic/mcp-wordpress-remote package, Claude Code can create and edit posts, manage pages, and interact with WordPress directly from a session.

Architecture

Claude Code
  └── stdio
      └── npx @automattic/mcp-wordpress-remote
              └── HTTPS (Application Password auth)
                      └── WordPress REST API (/wp-json/mcp/...)
                              └── MCP Adapter plugin
                                      └── WordPress Abilities API

Requirements

WordPress 6.9+
Node.js (installed via nvm)
MCP Adapter plugin activated on the WordPress site

Continue reading WordPress MCP Setup for Claude Code

Setting Up Mnemosyne Memory for Claude Code

Mnemosyne is a local-first AI memory system that integrates with Claude Code via MCP, giving Claude persistent memory across sessions.

Why MCP Instead of CLI

The CLI (mnemosyne store, mnemosyne recall) is a manual tool — you run it yourself and paste results back. The MCP integration makes Mnemosyne a first-class tool Claude can call directly, just like any other tool in a session.

Concretely, with MCP:

Claude automatically stores and retrieves memories during a conversation without any manual intervention
Memory reads and writes happen inline, so context is enriched transparently
No copy-pasting: Claude calls mnemosyne_remember or mnemosyne_recall the same way it calls any other tool

The CLI remains useful for inspection (mnemosyne stats), backup (mnemosyne export), and manual management — but it is not a substitute for the MCP integration when Claude is the one that needs to remember things.

Continue reading Setting Up Mnemosyne Memory for Claude Code

Connecting WordPress MCP via Tailscale

Most guides for connecting AI assistants to a self-hosted WordPress site via MCP suggest using Cloudflare Tunnel or ngrok to expose the site publicly. This works, but it also reintroduces infrastructure layers that can interfere with MCP: WAFs, bot-fight rules, page caches, and host-level rewrites that intercept REST API requests before WordPress ever handles them.

A cleaner alternative, if your machines are already on Tailscale: skip the public internet entirely.

Continue reading Connecting WordPress MCP via Tailscale

When Security Becomes Friction for Meralco Online

Meralco is a good example of a company overdoing online security in places where the actual risk is low.

Meralco is a utility company. It is not a bank, an e-wallet provider, or a financial institution holding customer funds. The information it needs to protect—customer name, service address, and billing amount—is important, but it does not carry the same risk profile as banking credentials or stored monetary value. The security approach should reflect that difference.

Continue reading When Security Becomes Friction for Meralco Online