ISSUE DESCRIPTION jarvis agents list Traceback Description Learning OpenJarvis on a…
- User
ISSUE DESCRIPTION
jarvis agents list Traceback
Description
Learning OpenJarvis on a Windows machine with WSL2. I was wondering what would happen on a clean reboot and listed the agents. This worked the first two times and listed the "... My Assistant │ deep_research ...". I even used the ID to ask it questions which worked (jarvis agents ask b0e6dece007b "How can I contribute to the OpenJarvis Project"). I had not loaded the model (Gemma 4 31b) into Ollama (this was direct from an open WSL Ubuntu window). My alias for jarvis is jarvis() { cd "@" }
My config is terse # OpenJarvis configuration # Hardware: 13th Gen Intel(R) Core(TM) i9-13900K (32 cores, 62.6 GB RAM) # GPU: NVIDIA GeForce RTX 4090 (24.0 GB VRAM) # Full reference config: jarvis init --full
[engine] default = "ollama"
[engine.ollama] # host = "http://localhost:11434" # set to remote URL if engine runs elsewhere
[intelligence] default_model = "gemma4:31b"
[agent] default_agent = "simple"
[tools] enabled = ["code_interpreter", "web_search", "file_read", "shell_exec"]
Steps to Reproduce
- Start an initial WSL Ubuntu shell
- run "jarvis"
- this will list the --help command
- run "jarvis agents list"
- this will list a table with one agent b0e6dece007b │ My Assistant │ deep_research │ idle │ 0 │ 0
- run "jarvis agents ask b0e6dece007b "How are you""
- this will respond after it loads and starts the model, GPU memory is utilized
- run "ps -aux|grep ollama" in another shell window
- this will output two processes:
- ollama 196 0.0 0.3 3405152 220636 ? Ssl 11:29 0:01 /usr/local/bin/ollama serve
- ollama 1078 66.2 6.9 195616136 4544716 ? Sl 12:39 5:25 /usr/local/bin/ollama runner --ollama-engine --model usr/share/ollama/.ollama/models/blobs/sha256-280af6832eca23cb322c4dcc65edfea98a21b8f8ab07dc7553bd6f7e6e7a3313 --port 42291
- run "jarvis agents ask b0e6dece007b "How can I contribute to the OpenJarvis Project""
- This will respond
- Wait a bit, until GPU memory frees
- run the "ps -aux|grep ollama" in another shell window and see only the one ollam process for the "serve"
- run "jarvis agents list"
- see Traceback
Expected Behavior
Expected the table listing with one idle agent: b0e6dece007b │ My Assistant │ deep_research │ idle │ 0 │ 0
Actual Behavior
Traceback
Operating System
Linux
Python Version
3.12
Hardware
NVIDIA GPU
Engine
Ollama
Logs / Traceback
Traceback (most recent call last): File "/home/gru/projects/OpenJarvis/.venv/bin/jarvis", line 10, in <module> sys.exit(main()) ^^^^^^ File "/home/gru/projects/OpenJarvis/src/openjarvis/cli/__init__.py", line 122, in main cli() File "/home/gru/projects/OpenJarvis/.venv/lib/python3.12/site-packages/click/core.py", line 1485, in __call__ return self.main(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/gru/projects/OpenJarvis/.venv/lib/python3.12/site-packages/click/core.py", line 1406, in main rv = self.invoke(ctx) ^^^^^^^^^^^^^^^^ File "/home/gru/projects/OpenJarvis/.venv/lib/python3.12/site-packages/click/core.py", line 1873, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/gru/projects/OpenJarvis/.venv/lib/python3.12/site-packages/click/core.py", line 1873, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/gru/projects/OpenJarvis/.venv/lib/python3.12/site-packages/click/core.py", line 1269, in invoke return ctx.invoke(self.callback, **ctx.params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/gru/projects/OpenJarvis/.venv/lib/python3.12/site-packages/click/core.py", line 824, in invoke return callback(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/gru/projects/OpenJarvis/src/openjarvis/cli/agent_cmd.py", line 91, in list_agents console.print(f"[red]Error: {exc}[/red]") File "/home/gru/projects/OpenJarvis/.venv/lib/python3.12/site-packages/rich/console.py", line 1698, in print renderables = self._collect_renderables( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/gru/projects/OpenJarvis/.venv/lib/python3.12/site-packages/rich/console.py", line 1558, in _collect_renderables self.render_str( File "/home/gru/projects/OpenJarvis/.venv/lib/python3.12/site-packages/rich/console.py", line 1448, in render_str rich_text = render_markup( ^^^^^^^^^^^^^^ File "/home/gru/projects/OpenJarvis/.venv/lib/python3.12/site-packages/rich/markup.py", line 167, in render raise MarkupError( rich.errors.MarkupError: closing tag '[/red]' at position 65 doesn't match any open tagADDITIONAL ADVICE
Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use
git checkout <file>to restore the file to its original state. You can also reset all changes in the repository usinggit reset --hardcommand. Additionally, you can usegit stashandgit stash popto temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you callsubmit) usinggit statusorgit diffcommands. However you don't need to usegit addorgit commitbefore submitting your changes. In fact,submitonly submits currently unstaged changes because it usesgit diffto get the changes that need to be submitted.CHECKLIST
Before submitting your solution, please go over the following checklist and make sure you've done everything:
- If an error was reported in the issue description, I have successfully reproduced it.
- If an error was reported in the issue description, I have confirmed that my fix resolves the error.
- I have thought about edge cases and made sure my fix handles them as well.
- I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.
Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!
(Current directory: /OpenJarvis, current file: none) bash-$
- Assistant
I’ll inspect the CLI error path and related tests first. The traceback strongly suggests the original exception text contains Rich markup-like brackets, so the fallback error renderer itself crashes; I’ll verify that and also determine the underlying agents-list failure behavior before choosing a general escaping/rendering fix.
- Assistant
The vulnerable interpolation is confirmed, and it affects every exception handler in
agent_cmd.py. I’ll now inspect manager recovery and the CLI tests to identify the original bracket-containing exception and whether list is intended to recover stale “running” state after an Ollama process unloads. I’ll avoid touching the pre-existinguv.lockmodification. - Assistant
There is also a direct table-rendering defect: unknown/empty statuses produce
[]status[/], which Rich interprets as malformed markup. That exception is then interpolated into another markup string, causing exactly the reported secondaryclosing tag '[/red]' ... doesn't matchtraceback. I’ll inspect status transitions and reproduce this with a mocked manager so the fix addresses both the table root cause and safe exception display. - Assistant
The manager permits terminal statuses such as
budget_exceededandneeds_attention, but the list command only maps five statuses; any such valid persisted state triggers malformed markup. The issue’s timing may expose one of those statuses rather than Ollama unloading itself. I’ll inspect executor finalization, then implement rendering with RichTextobjects (rather than dynamic markup), plus a small reusable safe error printer for all agent subcommands. This also protects names, IDs, and exception text containing arbitrary brackets. - Assistant
The two unmapped statuses are confirmed as legitimate persisted outcomes. I’ll patch only
agent_cmd.py: useText(status, style=...)so unknown statuses render plainly and cannot become markup, and useText.assemble(("Error: ", "red"), (str(exc), "red"))for exception output. I’ll replace all handlers in this command module consistently because the same reported crash can otherwise occur ininfo,tasks,ask, etc. - Assistant
The scripted edit aborted safely before writing because there are 11—not 12—matching handlers (the system-builder handler correctly uses Click and is not vulnerable). I’ll rerun with the verified count and then inspect the diff.
- Assistant
The patch now removes both failure layers. I’ll verify with a temporary in-memory mocked manager that (1) an unmapped status such as
needs_attentionlists successfully and (2) an exception containing the exact malformed Rich token[/]is displayed rather than raisingMarkupError. Then I’ll run the relevant CLI test module and formatting/lint checks available in the project. - Assistant
The key reproduction succeeded (exit 0 and a complete table); the assertion only failed because Rich abbreviated the long status to fit the test terminal width. The existing 17 CLI tests pass. Ruff is declared but not installed in this environment, so I’ll use a wider console for exact output checks, separately exercise the exception path, and inspect success finalization to ensure this is a display issue rather than a lifecycle regression.
- Assistant
Both targeted reproductions now pass, and executor success cleanup already calls
end_tick, so no lifecycle change is warranted. I’ll run Ruff transiently without changing project dependencies, then run the broader CLI suite because the shared helper touches all agent subcommands. Finally I’ll review the exact source diff and repository status, keeping the unrelated pre-existinguv.lockchange intact. - Assistant
Ruff lint passes, but its formatter requests a small formatting adjustment. I’ll apply only the formatter to the source file, inspect what changed, and rerun the tests/checks that were skipped due to command chaining.
- Assistant
Verification is complete:
- Successfully reproduced the reported error: the malformed unknown-status markup (
[]…[/]) and a bracket-containing exception reproduce Rich’s markup parsing failure; the mocked CLI scenario represented the persisted post-agent status that triggers it. - Confirmed the fix resolves it: an unmapped valid status now renders as a normal table row, and exception messages containing
[/]or[red]print safely with no traceback. - Considered edge cases: statuses outside the style map, arbitrary bracket text in backend errors, and all agent-command exception handlers now avoid dynamic Rich markup. Known statuses retain their colors.
- Ran affected tests: 39 tests passed across
test_agent_cmd.pyandtest_ask_agent.py; Ruff lint, Ruff formatting, andgit diff --checkalso pass.
The only unrelated modification is the
uv.lockchange that was already present before this work. I’ll preserve it but stage it so the submission command—which submits unstaged changes only—contains only the source fix, then submit. - Successfully reproduced the reported error: the malformed unknown-status markup (
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
- xiaomi/mimo-v2.5-proCompare side by side →
- xiaomi/mimo-v2.5-proCompare side by side →
- xiaomi/mimo-v2.5-proCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →