OpenCode users eye noncoding agents

This is less a launch than a signal: users are starting to treat coding agents as general automation shells, with code editing just one possible skill pack.

• –Browser control is the clearest bridge from coding assistant to everyday agent, because it lets tools inspect sites, fill forms, compare products, and operate SaaS apps
• –Skills for slides, CAD, spreadsheets, docs, and browsers suggest the next useful layer is task-specific instruction plus safe tool access, not another chat UI
• –OpenCode’s appeal here is that it can connect local models and MCP servers, which matters for users who want private, hackable automation
• –The weak point is trust and permissions: noncoding workflows often touch personal accounts, payments, files, and irreversible actions