quint_decide fails with Transport Closed

[twilightsaurus]

For some reason using quint with Codex CLI in a WSL2 terminal always fails at the decide phase. It works for me through cursor ide, but not terminal.

Also, the slash commands are not correctly added to cursor when working in WSL.

Any idea what could be causing this and how to solve it?

Thanks

[m0n0x41d]

Hello @twilightsaurus

For Issue 1 (Codex CLI + WSL2 fails at decide phase):

What error do you see? "Fails" could mean many things:

• Precondition error ("no L2 hypotheses found")?
• Path error?
• Permission error?
• Silent failure?

Can you share the error output? Also:

• How are you running the MCP server? (quint-code mcp or via config, or just as intended auint-code init --cursor and all in?)
• Is .quint/ directory created? Does it have L2 files when you try to decide?

For Issue 2 (slash commands not in Cursor on WSL):

How did you install/configure quint-code for Cursor?

The Codex CLI has some quirks. It was mentioned in the README – Codex CLI does not support local MCP configs, so you need to re-init for Codex every time in every project. Unfortunately, it is the way it is working now. For Cursor, everything must be well after quint-code init --cursor plus enabling the MCP server in the Cursor config.

P.S. Please share more input and the version of Quint Code you are using. Thanks.

[twilightsaurus]

Hello m0n0x41d,

Yeah, sorry for my lousy report...

For Issue 1:
The whole process worked perfectly fine, there's no missing precondition, path error, or error of any kind actually, it just shows this at the decide stage:

Called
  └ quint-code.quint_decide({"title":"[My decision details]"})
    Error: tool call error: tool call failed for `quint-code/
        quint_decide`
        Caused by:
            tools/call failed: Transport closed

The DRR file actually gets created, but the Agent gets "stuck" because the tool call fails.

I tried restarting the terminal restarting cursor, re-starting quint via quint-code init --all again. Keeps getting this Transport closed at the decision stage.

I start the mcp via quint-code init --all, because i use both cursor and codex cli interchangably.

.quint directory is there, with everything in it, and there are L2s when i call decide.

For cursor commands, maybe i just dont understand, are they supposed to show up when I type / in a agent chat? or are they just available to the agent itself, because they are there for agent, and mcp works for cursor agents, but I thought I should be seeing commands show up when I type /.

I also wanted to ask, do you recommend committing the entire .quint directory? or should the db and state be excluded?

[m0n0x41d]

Hello there!
Regarding:

I also wanted to ask, do you recommend committing the entire .quint directory? Or should the db and state be excluded?

Quint code currently does not support collaboration between several users. The only way to collaborate fully is to ensure that no one edits the database. I mean, it might be really complex and frustrating trying to "merge" changes in the SQLite state when two people have made some reasoning cycles. So if your team has discipline and is able to sync carefully on Quint, it makes sense to commit the database too.

I mean, you need to decide on your own. You can commit DRR only, or you can ask LLM to convert and update your committed /docs directory or something like that, and keep DRR only on your machine.

Personally, I commit the .quint directory fully, at least for the sake of backing up the state in the remote.

[m0n0x41d]

This seems to be a fix for the same issue you have faced:
#22

I will merge it and roll out a bug fix release. Please test it afterward and let me know how it goes.

[m0n0x41d]

https://github.com/m0n0x41d/quint-code/releases/tag/v4.1.1 is out
you can reinstall qc with same script: curl -fsSL https://quint.codes/install.sh | bash