Using reasonix with in VSCode with vscode-acp extension?

[plerohellec]

I'm trying to use reasonix with in VSCode with vscode-acp extension (https://github.com/formulahendry/vscode-acp). I read it's supposed to work in #1132.

And it connects fine, chat is working, it reads files normally but it can't edit any file or run any command.

I see this in ACP Traffic logs when trying to write a file:

[2026-06-30T14:45:11.298Z] <<< AGENT → CLIENT [REQUEST] session/request_permission
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "session/request_permission",
  "params": {
    "sessionId": "3c6d2554-c2cb-4871-ad31-4d16774f982b",
    "toolCall": {
      "toolCallId": "gate-2",
      "title": "write_file /tmp/reasonix-test-write.txt",
      "kind": "edit",
      "status": "pending"
    },
    "options": [
      {
        "optionId": "allow_once",
        "name": "Allow",
        "kind": "allow_once"
      },
      {
        "optionId": "allow_always",
        "name": "Allow Edit for this session",
        "kind": "allow_always"
      },
      {
        "optionId": "allow_persistent",
        "name": "Always allow Edit (save to config)",
        "kind": "allow_persistent"
      },
      {
        "optionId": "reject_once",
        "name": "Reject",
        "kind": "reject_once"
      }
    ]
  }
}

[2026-06-30T14:45:11.299Z] >>> CLIENT → AGENT [RESPONSE] id=2
{
  "jsonrpc": "2.0",
  "id": 2,
  "error": {
    "code": -32602,
    "message": "Invalid params",
    "data": {
      "_errors": [
        "Invalid input: expected \"allow_once\"",
        "Invalid input: expected \"allow_always\"",
        "Invalid input: expected \"reject_once\"",
        "Invalid input: expected \"reject_always\""
      ]
    }
  }
}

[2026-06-30T14:45:11.300Z] <<< AGENT → CLIENT [NOTIFICATION] session/update
{
  "jsonrpc": "2.0",
  "method": "session/update",
  "params": {
    "sessionId": "3c6d2554-c2cb-4871-ad31-4d16774f982b",
    "update": {
      "sessionUpdate": "tool_call_update",
      "toolCallId": "call_00_hr0KBWuX873dEQekuz360185",
      "status": "failed",
      "content": [
        {
          "type": "content",
          "content": {
            "type": "text",
            "text": "blocked by permission policy"
          }
        }
      ]
    }
  }
}

I read that "allow_persistent" is not a valid "kind"?

Reasonix is configured this way in acp.agents config:

"acp.agents": {
        
        "Reasonix": {
            "command": "npx",
            "args": [
                "reasonix@next",
                "acp"
            ],
            "env": {}
        },
   ...
}

Is there a trick I'm missing?

CC'ing @yes999zc since he's involved with vscode integration.

[plerohellec]

I should clarify this is with Reasonix 1.14.0 (and also earlier versions) and the most recent formulahendry/vscode-acp extension.

[276408029]

ACP Configuration on Windows and Linux

I use the following ACP configuration on Windows:

"acp.agents": {
    "Reasonix": {
      "command": "reasonix",
      "args": ["acp"],
      "env": {}
    }
}

This is a globally installed package, so I can start Reasonix by typing reasonix in the terminal.

When I remotely connect to Linux from Windows, the ACP settings are:

"acp.agents": {
    "Reasonix": {
        "command": "npx",
        "args": ["reasonix", "acp"],
        "env": {},
        "cwd": "${userHome}/.reasonix"
    }
}

On Linux, Reasonix is not installed globally, so to start it I need to run npx reasonix.

Version 1.15, for reference only.

[plerohellec]

Thank you.
I want to be clear that the extension works in general in my environment, I can chat from vscode to reasonix through ACP just fine. It's specifically file edits that don't work. Reasonix fails to get permission to edit any file with the error reported above. I suspect this is because reasonix is asking for an invalid permission "kind": "allow_persistent".

Does editing files through ACP work for you?

[SivanCola]

Thanks for the detailed trace. You were right: allow_persistent was not a valid ACP PermissionOptionKind, and strict ACP clients rejected the whole session/request_permission request with Invalid params.

This has been fixed by #5881, which has now been merged into main-v2.

What changed:

• Reasonix ACP no longer sends the non-spec allow_persistent option kind.
• ACP permission options now stay within the official enum: allow_once, allow_always, reject_once, and reject_always.
• In ACP mode, allow_always is session-scoped in Reasonix; cross-session persistence is left to the host client.
• Regression coverage was added for strict ACP clients.

There is no configuration trick needed on your side. Please wait for the next Reasonix release, then update your installed Reasonix version; the currently published version may still show this failure until that release is available.

[plerohellec]

I can confirm this is working in Reasonix 1.16.

[esengine]

Fixed by #5881 (ACP permission options now stay within the spec enum) and confirmed working in 1.16 by the reporter — closing.