Skip to content
TheChatArchiveThe Chat Archive
gpt-5.6-luna· openaiHugging 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
    

    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

    I’ll inspect the agent CLI and its tests first, then reproduce the Rich markup failure with an exception containing markup-like characters. The likely fix is to render dynamic errors as plain text (or escape them) so malformed [ sequences from an underlying Ollama/database error cannot trigger a second exception. I’ll then add the smallest source-only change, run focused and relevant tests, and review the diff.

  3. Assistant

    The traceback confirms the secondary failure is in the exception handler: exc is interpolated into a Rich markup string, so an error such as an Ollama response containing [ can make the closing [/red] invalid. I’m checking the remainder of this command module and project CLI conventions so the fix is consistent rather than only masking this one line.

  4. Assistant

    The module has the same unsafe pattern in every jarvis agents subcommand, so fixing only list would leave the same crash reachable through create, info, and others. I’ll replace those dynamic Rich markup messages with markup=False while retaining red styling; this preserves the user-facing output and treats arbitrary exception text literally. I’ll then invoke agents list with a mocked manager failure containing an unmatched bracket.

  5. Assistant

    The source diff now makes all agent-command exception output literal, including unmatched brackets, while keeping the error visually red. Next I’ll run a direct reproduction through Click with _get_manager patched to raise an Ollama-like bracketed error, followed by the existing agent CLI tests.

  6. Assistant

    The reproduction is fixed: the command exits cleanly and prints the literal bracketed error without MarkupError; the existing 17 agent CLI tests also pass. I’ll run the related agent manager tests and a lightweight formatting/status check before submitting, then provide the requested checklist rationale.

  7. Assistant

    The related test run reached 210 passing tests but stopped on an unrelated pre-existing TestLoopGuard.test_identical_calls_blocked failure (the Rust backend did not block the second call). Since it does not involve the changed CLI module, I’ll record it and separately verify the changed file’s whitespace and final diff.

  8. Assistant

    The validation command revealed an unrelated uv.lock modification (likely produced by the repository environment/test tooling); it is not part of this fix and must not be submitted. I’ll restore only that unrelated file, confirm the source-only diff, and perform one final focused reproduction check.

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