Skip to content
TheChatArchiveThe Chat Archive
x-ai/grok-4.5· unknownHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

ISSUE DESCRIPTION jarvis agents list Traceback Description Learning OpenJarvis on a…

  1. 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 "OPENJARVISHOME"∣∣return1uvrunjarvis"OPENJARVIS_HOME" || return 1 uv run jarvis "@" }

    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

    1. Start an initial WSL Ubuntu shell
    2. run "jarvis"
    3. this will list the --help command
    4. run "jarvis agents list"
    5. this will list a table with one agent b0e6dece007b │ My Assistant │ deep_research │ idle │ 0 │ 0
    6. run "jarvis agents ask b0e6dece007b "How are you""
    7. this will respond after it loads and starts the model, GPU memory is utilized
    8. run "ps -aux|grep ollama" in another shell window
    9. this will output two processes:
    10. ollama 196 0.0 0.3 3405152 220636 ? Ssl 11:29 0:01 /usr/local/bin/ollama serve
    11. 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
    12. run "jarvis agents ask b0e6dece007b "How can I contribute to the OpenJarvis Project""
    13. This will respond
    14. Wait a bit, until GPU memory frees
    15. run the "ps -aux|grep ollama" in another shell window and see only the one ollam process for the "serve"
    16. run "jarvis agents list"
    17. 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 tag
    

    Interface

    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 using git reset --hard command. Additionally, you can use git stash and git stash pop to temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you call submit) using git status or git diff commands. However you don't need to use git add or git commit before submitting your changes. In fact, submit only submits currently unstaged changes because it uses git diff to 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-$

  2. Assistant

    The traceback shows a Rich markup error when printing an exception in list_agents. I'll inspect that code path and reproduce the failure.

  3. Assistant

    The Rich error comes from markup in the exception text. I'll trace AgentManager.list_agents and what can raise after the model unloads.

  4. Assistant

    Checking recover logic and how list_agents interacts with agent status after the model unloads.

  5. Assistant

    Looking at schema/migrations and list_agents implementation for column mismatches.

  6. Assistant

    Let me look at how agents ask works - maybe something in the agent record changes after ask, and then list fails. Also the MarkupError - when exception contains brackets, it's a known issue. The exc...

  7. Assistant

    Inspecting _row_to_agent and status values written during ask.

  8. Assistant

    There's something odd - I went to manager.py 680但 the open showed agent_cmd.py still? Wait, the tool said:

  9. Assistant

    Reproducing the markup failure with empty status styles and exception messages that contain brackets.

  10. Assistant

    Empty status style is the bug. Checking which status values lack a style mapping:

  11. Assistant

    Found unmapped statuses budget_exceeded and needs_attention. Checking when the executor sets them:

  12. Assistant

    Also need to check end_tick - when does it set status. Looking at start_tick/end_tick.

  13. Assistant

    There's also "stalled" status mentioned in agent_manager_routes.py. Let me check all statuses used.

  14. Assistant

    Inspecting the ask agent flow for status transitions after a successful response:

  15. Assistant

    Confirming which status produces the exact secondary error at position 65:

  16. Assistant

    Confirmed: budget_exceeded and needs_attention match the report. Checking how the frontend styles those statuses for consistency.

  17. Assistant

    Implementing the fix: map all known statuses, handle unknown ones safely, and escape exception text.

  18. Assistant

    I'll add a helper function for status styling and safe error printing at the top of the file. Given the scattered console.print(f"[red]Error: {exc}[/red]") patterns, I should fix them all with escap...I see the issue now—it's a classic Rich markup error where the closing tag [/red] doesn't match any open tag because the exception message itself contains brackets that break the parsing. The traceback you shared is exactly what happens when `console.

  19. Assistant

    Now add helper functions and fix list_agents.

  20. Assistant

    Updating remaining error prints in this file to use the same safe helper:

  21. Assistant

    I'll replace all of these with _print_error using replace --all

  22. Assistant

    Verifying the fix with temporary scripts that cover all statuses and exception escaping:

  23. Assistant

    Running an end-to-end test through the CLI with real agent statuses:

  24. Assistant

    List works (exit=0); re-running with a looser assertion:

  25. Assistant

    CliRunner API might have changed.simplifying.

  26. Assistant

    Running related existing tests:

  27. Assistant

    All tests passed. Reviewing the final diff before submit:

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.