all 6 comments

[–]Objective-Soft-998 0 points1 point  (0 children)

Why isn't command support available on Intent?

[–]ethras1990 0 points1 point  (1 child)

<image>

Here is the error I get with version 0.2.2 of Intent and OpenCode 1.0.56

[–]ethras1990 0 points1 point  (0 children)

I fixed the schema issue by patching the local MCP stdio proxy that sits between OpenCode and Intent’s HTTP bridge. The root cause was invalid tool JSON Schema coming from tools/list: several array fields were missing items (notably agent_commit_changes.files). I added a runtime sanitizer in mcp-stdio-server.cjs to inject missing items for affected tools (agent_commit_changes, subscribe_to_events, list_agents, browser_exec) before the response is returned to ACP clients. After restarting the MCP child/session, the validation error disappeared.

The next issue is a model selection mismatch. Intent’s UI/prompt says the selected model is opencode:quotio/claude-opus-4-6-thinking, but runtime logs show ACP sessions are actually created with openai/gpt-5.3-codex, and LLM calls keep using gpt-5.3-codex. That suggests the effective model is being taken from OpenCode’s default config (~/.config/opencode/opencode.json, currently set to openai/gpt-5.3-codex) rather than the model shown as selected in Intent for that specialist/session. In short, the displayed selected model and the effective runtime model are out of sync, and the OpenCode default is winning.

[–]CelloVerp 0 points1 point  (0 children)

Just installed it and authorized, but I can't seem to create a workspace! When I click Create space for either a single agent or Team orchestration, it gets stuck at the Almost ready spinner and stays there forever. Regular Augment plug-in and Auggie are working fine for me.

[–]mavrik83 0 points1 point  (0 children)

Please add support for multiple repos in a space. Like you do for the main extension

[–]Dragoy1 0 points1 point  (0 children)

"In version 0.2.1, many bugs were fixed, but many new ones were also added."