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 tagInterface
No new interfaces are introduced.
ADDITIONAL 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
Now let's write a Python script to apply the targeted replacements and add imports.
Assistant
All lines updated with no warnings. Now let's verify with a diff sample and add missing imports of
escapefromrich.markup.Assistant
Now I need to add the import to each of these files. Let's check how imports are typically structured (e.g. after
from __future__ import annotations, alphabetically among rich imports).Assistant
Now let's verify each file compiles fine (syntax check) and check that markdown ordering doesn't break anything (it's just an import order, not functionally important). Let's compile all python files.
Assistant
Now let's check for duplicate imports (in case a file already had
from rich.markup import escapesomewhere, like init_cmd.py which we didn't touch, that's fine). Let's verify our modified files don't already import escape elsewhere causing duplicate.Assistant
All good, single import each. Now let's view a few diffs to confirm correctness.
Assistant
Looks good. Now let's check some of the trickier ones like ask.py, config_cmd.py:330, tool_cmd.py:101 (the
{e}case), and registry_cmd.py:92 (Table.add_row).Assistant
All correctly updated. Now let's write a reproduction script to simulate the original crash and confirm the fix works.
Assistant
Reproduced the exact error. Now let's confirm our fix resolves it.
Assistant
Fix confirmed. Now let's run the actual
jarvis agents listreproduction with a simulated scenario to be thorough, plus run existing tests.Assistant
Let's check test file to see if there's a related test for error escaping, and also run broader CLI tests.
Assistant
uv.lock got touched again by
uv run. Let's revert that since it's unrelated to the fix.Assistant
Good, uv.lock reverted. Now let's run the full test suite once more (with my changes applied) to be safe, avoiding
uv runtouching lock file further, using pytest directly via venv python.Assistant
Same 14 pre-existing failures unrelated to my changes, uv.lock untouched this time. Let's run the full test suite (not just cli) to double check nothing else broke, then run evals tests for the evals/cli.py change.
Assistant
These are unrelated missing-dependency errors in engine tests. Let's exclude those dirs and re-run to check the relevant tests pass.
Assistant
Good. Now let's do a final full diff review for sanity, then check ruff/lint if available.
Assistant
All looks correct and consistent. Now let's do a final sanity full-repo compile check.
Assistant
Let's also confirm
jarvis agents list(the exact CLI in the issue) works fine with a crafted scenario mimicking the crash, using the CliRunner to simulate list_agents raising an exception whose message contains problematic markup.Assistant
This confirms the crash from the issue is fixed. Let's clean up temp files.
Assistant
Now let's run the full cli test suite one final time to make sure state is clean.
Assistant
Same pre-existing 14 failures (confirmed unrelated to my change earlier via stash test). Now git status is clean (only my modified src files, no lockfile changes).
Assistant
Everything is clean. Now let's go through the checklist.
Assistant
Checklist review
-
If an error was reported in the issue description, I have successfully reproduced it. Yes. I traced the exact root cause:
rich.markup.renderraisesMarkupError: closing tag '[/red]' ... doesn't match any open tagwhenever an exception's string representation contains a stray[...]-style sequence that rich interprets as markup (e.g. an implicit-close tag[/], or a tag whose name happens to matchred, etc.). I reproduced the exact traceback shown in the issue with a minimal script (console.print(f"[red]Error: {exc}[/red]")whereexccontains a literal[/]), confirming this is the mechanism behind the "jarvis agents list" crash — the CLI's own error-handling code was throwing a second, unrelated exception while trying to report the first one. -
If an error was reported in the issue description, I have confirmed that my fix resolves the error. Yes. I fixed the root cause generally: every place across the CLI (
agent_cmd.py, and ~20 othercli/*.pyfiles plusevals/cli.py) that interpolated a raw exception message ({exc}/{e}) into a Rich-markup string now escapes it withrich.markup.escape(str(exc))before rendering. I re-ran the reproduction script and confirmedjarvis agents list(simulated via CliRunner with a mocked failure containing problematic bracket sequences) now prints a clean error message instead of crashing with aMarkupError. -
I have thought about edge cases and made sure my fix handles them as well. Yes. Rather than patching only the specific
agent_cmd.py:list_agentscase from the issue, I searched the entire CLI surface for every occurrence of an exception variable (exc,e) embedded inside a Rich markup string (includingTable.add_rowcells, which also render markup) and applied the same escaping fix uniformly, since any of these could raise the same secondary crash if the underlying exception message happens to contain bracket characters (very plausible for things like[Errno ...], list reprs, or paths with brackets). I verified there were no other exception variable names in use (onlyexc,e, and a_dr_excthat goes through logging, not Rich, so it didn't need changes) and confirmed no lines were missed. -
I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. Yes. I ran
tests/cli/(the most relevant suite) both before and after my change (viagit stash) and confirmed the same 14 pre-existing failures occur in both cases (they are unrelated environment/network issues, e.g. version-check banners polluting JSON output, missing optional dependencies) — my change introduces no new failures. All previously-passing tests, includingtests/cli/test_agent_cmd.py, still pass (17/17). I also verified all modified files compile cleanly withpy_compile.
-
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
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.5-35B-A3BCompare side by side →
Qwen/Qwen3.5-35B-A3BCompare side by side →