[Bug] Fail to Load Agent Properly When Opening

[jollyxenon]

App Variant

Electron

Operating System & Version

Windows 11 24H2

Issue Summary

CodeNomad launches its own OpenCode server with a CodeNomad-specific OPENCODE_CONFIG_DIR, which prevents user-configured OpenCode plugins and agents from being loaded.

As a result, agents provided by user plugins such as oh-my-openagent are missing from the bottom-left agent selector. After merging the user OpenCode config, another issue appears: native agents such as build can be auto-selected and temporarily shown in the primary agent selector, even though they should not be selectable as primary agents.

Steps to Reproduce

Create a new instance and then enter a conversation.

Current Behavior

1. CodeNomad starts OpenCode with its packaged config directory.
2. User OpenCode config from ~/.config/opencode is not loaded.
3. Plugin-provided primary agents such as Sisyphus and Hephaestus do not appear in the CodeNomad agent selector.
4. When plugin agents are available, the selector may still auto-load build.
5. build can appear in the selector because the current session agent is forced back into the list.

Expected Behavior

1. CodeNomad should preserve its own bridge plugin while also loading the user's OpenCode config.
2. User-configured OpenCode plugins should be available in CodeNomad-launched OpenCode instances.
3. The primary agent selector should only include selectable primary agents.
4. Native/internal agents such as build should not be auto-selected or shown in the primary selector.
5. New sessions should default to a valid selectable primary agent.

Logs & Screenshots

Though we expect to see "Sisyphus" and other agents here, it only loaded default agents.

Root Cause

There are two related issues:

1. CodeNomad sets OPENCODE_CONFIG_DIR to its own bundled config directory, so user OpenCode plugins are isolated from the OpenCode process launched by CodeNomad.
2. The UI treats any non-subagent agent as selectable. This allows native/internal agents to be used as default primary agents. The selector also force-adds the current agent back into the list, which can make invalid agents such as build appear temporarily.

[hugalafutro]

i'm running into the same issue and it honestly sends me crazy

everything was working until about 30minutes ago - orchestrator, council agents from omo-slim in codenomad no problem.
I know it's the old "I swear I changed nothing", but what can I say. I connected to the codenomad as always and suddenly only have build and plan models, which are configured as disabled in openconde.json, but all plugins and mcps from the same opencode.json show up as loaded and work within codenomad it's just i can't access the agents from omo-slim suddenly.

there is only single opencode binary on the system and lunching it shows all agents. But it literally sends me crying I saw all the omo-slim agents in codenomad up until something happened between last time i turned it off and on again...

[jollyxenon]

Though unmerged, my latest PR has solved this problem (I hope). I'm now running my own dev version CodeNomad, and everything is okay! I mean, I really sincerely cordially recommend that you may have a try. Maybe you can find more details to polish this : )

[hugalafutro]

i'm too stupid to make it work,i got as far as merging the pr locally and can launch codenomad with the dev command, but it tries to open gui i need it to accept arguments with ip and apssword, but then it doesn't launch and npm tries to use the arguments instead

i'm literally at the verge of punching a hole through my monitor

1. i spent about 5 hour is in codenomad working with agents from omo-slim as i always do.
2. i turned it off went to eat
3. i turned it back on - only build and plan agent shows

[jollyxenon]

The real problem

There are two separate issues:

1. The agent loading bug (fixed in PR #385)

CodeNomad launches an OpenCode server in the background, but it points OpenCode to its own empty config directory instead of your ~/.config/opencode. PR #385 fixes this by merging your user OpenCode config into CodeNomad's config directory. After merging that PR, the agent list should be complete again.

2. You can't pass CLI flags through npm run dev (NOT a bug — here's why)

When you run npm run dev, the Electron app starts the server internally using its own parameters. Anything after -- goes to the Electron dev process, not to the server.

The fix: Every CLI flag has an equivalent environment variable. Set them before running npm run dev:

Windows (PowerShell):

$env:CLI_HOST = "0.0.0.0"
$env:CODENOMAD_SERVER_PASSWORD = "your-password"
$env:CLI_HTTPS = "true"
$env:CLI_HTTP = "false"
npm run dev

Linux/macOS:

CLI_HOST=0.0.0.0
CODENOMAD_SERVER_PASSWORD=your-password
CLI_HTTPS=true
CLI_HTTP=false
npm run dev

Hope this helps!

[hugalafutro]

Ok that got it running, appreciate the help! But that made things even worse, now there is no agents Just an unclickable button that says Select agent...

[hugalafutro]

and it still loads all the mcps and plugins from my opencode.json, but agents are gone and no models show... I just don't get it

[jollyxenon]

Oops…… It could be caused by two reasons.

Firstly, I used a extreme strategy to filter "build" and "plan" with !agent.hidden && !agent.native && agent.mode === "primary". However, I just modified for my OMO but haven't validate with OMO-Slim.

Secondly, omo-slim may load failed. If you install it by quote it in opencode.json with inner bunx, it may function normally. However, if you use npm to globally install it, it may go wrong.

I'll fix the first posible reason immediately. Please check the second reason. 🥹

[hugalafutro]

I'm not really sure what you mean I installed it with bunx oh-my-opencode-slim@latest install is there another way i could've installed it I can check?

[jollyxenon]

Ahha! I guess its cause is the recent commit of omo-slim. Just 2 hours ago.

Maybe you should check whether there is oh-my-opencode-slim@latest in your opencode.json firstly. Then, considering CodeNomad has its own setting directory, we can copy C:\Users\YOURUSERNAME\.config\opencode to C:\Users\YOURUSERNAME\.config\codenomad\opencode-config. Lastly, you may pull my recent commit as a stopgap measure. If none of these methods works, I really can't help it! >_<

[hugalafutro]

i tried with both @latest and without (thats how the bunx script puts it there) and deleting node_modules and letting opencode reinstall it to no avail
there is no opencode-config subdirectory (I'm on linux is it elsewhere?)

 ╭─sammael@viglen in ~ via 🥟 v1.3.13 took 0s
 ╰─λ ls ~/.config/codenomad/
drwxr-xr-x    - sammael  1 May 14:30  instances
drwxr-xr-x    - sammael 22 Apr 15:43  tls
.rw-r--r-- 1.3k sammael  2 May 20:48  config.yaml
.rw-r--r-- 1.5k sammael  2 May 20:48  state.yaml

at this point I guess I'll start getting used to opencode's webui and update codenomad and omo-slim few days later and see if anything changed

[hugalafutro]

So, uhh as I was "getting used to the opencode-desktop" it asked to update opencode. So I updated opencode on my dev machine as well.

And uhhh

I have no words... but I am not touching anything ever again

[jollyxenon]

Hahahahaha, what an O. Henry ending. Glad you solved the problem : )

[shantur]

Check comments here - #385 (comment)