johner

Ok will check it out. I run under root. Did you switch from root to non root and now trying back to root? Any context on what you were doing would be appreciated.

Hi both - it should be fixed now, would you mind giving it a test please?

ok should be fixed now, thanks for your feedback. Appreciate.

great, the latest version have them both integrated. Let me know if anything doesn;t work right, or too constrained in the framework. If you need to run these agents directly on the command line, use the little terminal icon on the drawer tab to launch bash directly in that workspace, you can then run kimi --login or whatever IF needed.

I have a fix prepared, let me see if I can before I release it. I won’t be able to test them well as I don’t have accounts.

thanks, I've fixed the plugin, I'm just testing before publishing. Thanks for your feedback!

oh wow! ok, sorry about that, let me check and fix. Have you been able to remove what ever is left behind manually? If not, point a local instance of one of your coding agents at the server via ssh, it'll figure it out and remove it. Out of interest, and feedback on what would have made it useful for you? Thanks John

Hi, thanks for reporting. This should be fixed now, I'd appreciate it if you could test and let me know as I wasn't able to reproduce on my servers, but claude found a reason why this would happen for some. Thanks John

Hi! So I assume the opencode agent works fine on its own? How are you launching ollama etc.? In the standard unraid terminal, the little terminal button on the workspace drawer tab or another way? Once I know I’ll see if I can get Claude to design a way to support this launch method. In the interim use kilo (or opencode) free models to config the local models in opencode so you can launch it as blower the current design :-)

I went with Orange as Unraid uses 'awesome fonts' for icons and I didn't find a suitable one, and the theme engine doesn't allow for multiple image files.

Hey! These should be fixed now, thx for the continued feedback.

I did think about this but went looking for a theme option and couldn’t find one, clearly I should have googled it! Let me explore the options.

Thanks for letting me know, I’ll get on it.

ok i went with one of yours in the end. let me know if it shows ok.

Thanks Ricardo777, to be honest, because i'm not very good with paint! I think I created that one with gemini originally and AI can't create transparent backgrounds. If you have time and want to tweak it or send another, I'd be happy to consider replacing it? Else, I'll probably have a play when i get a spare hour (which isn't looking likely for a while, I have a 3rd plugin in the creation!)

Antigravity Cli added, along with a number of fixes and a few other enhancements.

Hi @resin1980 @Joly0 I have almost finished a new version that should address both of these. @Joly0 To be sure, if your system still has the debug log, it would be helpful so I can double check not an unrelated issue to what I have fixed. Thanks John

I think you may have suffered from a defect where the agent sqlite DB can get corrupted. I've uploaded a new version with this fix. However, you may need to delete the codex folder from the home path. How to recover a stuck agentIf your agent gets stuck on the "Waking..." screen or starts but complains about a corrupted database, follow these steps. You'll lose the affected agent's conversation history (which is already broken), but everything else — your workspaces, settings, and other agents — stays intact. Step 1 — Open a terminalIn Unraid's top-right toolbar, click the >_ terminal icon. A black terminal window opens with a prompt like root@Tower:~#. Step 2 — Confirm you're looking at the right placeType each command and press Enter after each: cd /tmp/unraid-aicliagents/work/root/home ls -la You should see directories starting with a dot — .codex, .copilot, .local, etc. Those are the per-agent state folders. If the cd command fails ("No such file or directory") or ls -la shows an empty list, the plugin's overlay isn't mounted for your user. Open and immediately close the plugin's terminal once in the web UI (this triggers the mount), then re-run the two commands above. Step 3 — Delete the broken agent's folderRun one of these commands for the agent that's misbehaving: ┌────────────────┬──────────────────────────────┐ │ Agent │ Command │ ├────────────────┼──────────────────────────────┤ │ Codex CLI │ rm -rf .codex │ ├────────────────┼──────────────────────────────┤ │ GitHub Copilot │ rm -rf .copilot │ ├────────────────┼──────────────────────────────┤ │ Kilo Code │ rm -rf .local/share/kilo │ ├────────────────┼──────────────────────────────┤ │ OpenCode │ rm -rf .local/share/opencode │ ├────────────────┼──────────────────────────────┤ │ Goose │ rm -rf .local/share/goose │ └────────────────┴──────────────────────────────┘ If you're not sure which agent is at fault, run more than one — each agent rebuilds its folder from scratch the next time it starts. You'll only lose conversation history for the agents you delete; your workspaces, settings, and other agents stay exactly as they were. Step 4 — Re-launch the agent and verify1. Back in the plugin's web UI, open a workspace that uses the agent you just cleared. 2. The "Waking..." screen should clear within 5–15 seconds and you should see a normal agent prompt. 3. Type a quick message ("hello") and confirm the agent responds. 4. Close that workspace and re-open it — confirm the hang doesn't come back. If the problem still happens, please post the last 50 lines of the plugin's debug log to the support thread. You can grab it in the terminal with: tail -50 /boot/config/plugins/unraid-aicliagents/debug.log

Should be fixed now, upgrade and let me know please.

It's there now, I haven't done much to configure and test it, I'd appreciate if you could. If you need to run an initial command to set it up, click the terminal icon in the drawer tab, it'll load a terminal overlay in the same worksapce where you can run what you need.

I released a new version, let me know if you have any issues or requests. It's a big release under the covers, I already have a new release planned to fix a couple issues since Unraid 7.3.0. It works though.

ok new version up, with all fixes/changes. Let me know how you go! I was also able to include this request:

how weird I was thinking about this today! Let me get the release out, then I'll circle back to this one.

Ok I fixed the other issues, I’ll take a look at fixing this one and make the values more configurable. I think swappiness is system wide, but will double check.

Hi, ok let me check, I’ve been working on other updates, I’m now away for a few days, so might take a week or so. Did you get it running by forking it? Thanks for letting me know.