connecting to bifrost over SOCKS5 proxy fails

[Ricardo Wurmus <rekado@elephly.net>]

Hi,

thank you for kaagum.  I'm trying to use it with a bifrost 
installation on a network that I can only access with an SSH 
tunnel.  I've configured agent-shell like so:

--8<---------------cut here---------------start------------->8---
(require 'agent-shell-kaagum)

(setq agent-shell-kaagum-command "proxychains4"
      agent-shell-kaagum-parameters
      '("-f" "/path/to/proxychains.conf"
        "/path/to/bin/kaagum"
        "--api-base-uri=https://llm.example.net"
        "--api-key-command=gpg -dq /path/to/password.gpg"
        "--model=vllm/Qwen/Qwen3.8-27B"))

(add-to-list 'agent-shell-agent-configs
             (agent-shell-kaagum-make-agent-config))
--8<---------------cut here---------------end--------------->8---

This seems to work fine up to the first request from the agent 
shell:

--8<---------------cut here---------------start------------->8---
[proxychains] config file found: /path/to/proxychains.conf
[proxychains] preloading 
/gnu/store/djhjgy1j0iqd317pmgazv9wng249q0df-proxychains-ng-4.17/lib/libproxychains4.so
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] Strict chain  ...  127.0.0.1:8022  ... 
llm.example.net:443  ...  OK
Backtrace:
In ice-9/boot-9.scm:
  1791:12  9 (with-exception-handler _ _ #:unwind? _ 
  #:unwind-for-type _)
In unknown file:
           8 (apply-smob/0 #<thunk 7fde38d193a0>)
In ice-9/boot-9.scm:
    740:2  7 (call-with-prompt _ _ #<procedure 
    default-prompt-handler (k proc)>)
In ice-9/eval.scm:
    619:8  6 (_ #(#(#<directory (guile-user) 7fde38d1cc80>)))
In kaagum/tea.scm:
   970:19  5 (tea-loop #<<state> client-request-id: #f 
   agent-request-id: 0 next-session-id: 0 requests-alist: () 
   sessions: ()> "https://llm.example.net" "[MY API KEY]" 
   (("vllm/Qwen/Qwen3.8-27B" . #<<model> name: #f description: #f 
   context-length: #f>) ("vllm/Aleph-Alpha/Kolibri-1" . #<<model> 
   name: #f description: #f context-length: #f>) 
   ("vllm/google/medgemma-27b-it" . #<<model> name: #f 
   description: #f context-length: #f>)) (("read" . #<<tool> 
   descript…>) …) …)
In kaagum/monads.scm:
    139:2  4 (run-with-state _ _)
In kaagum/tea.scm:
   971:20  3 (_ _)
   971:20  2 (_ _)
   205:21  1 (_ _)
In rnrs/records/procedural.scm:
   143:10  0 (_ _)

rnrs/records/procedural.scm:143:10: ERROR:

  1. &assertion-failure

Process acp-client(proxychains4)-36 stderr finished
--8<---------------cut here---------------end--------------->8---

I have installed kaagum 0.1.0 with Guix.

I have no experience with agent-shell, nor do I have access to any 
other LLM server.  Am I doing something obviously wrong?

I've also changed the URL to https://llm.example.net/v1 and it 
fails at a different point:

--8<---------------cut here---------------start------------->8---
[proxychains] config file found: /path/to/proxychains.conf
[proxychains] preloading 
/gnu/store/djhjgy1j0iqd317pmgazv9wng249q0df-proxychains-ng-4.17/lib/libproxychains4.so
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] DLL init: proxychains-ng 4.17
[proxychains] Strict chain  ...  127.0.0.1:8022  ... 
llm.example.net:443  ...  OK
Backtrace:
In ice-9/boot-9.scm:
  1791:12  7 (with-exception-handler _ _ #:unwind? _ 
  #:unwind-for-type _)
In unknown file:
           6 (apply-smob/0 #<thunk 7fa0ce1193a0>)
In ice-9/boot-9.scm:
    740:2  5 (call-with-prompt _ _ #<procedure 
    default-prompt-handler (k proc)>)
In ice-9/eval.scm:
    619:8  4 (_ #(#(#<directory (guile-user) 7fa0ce11cc80>)))
In kaagum/tea.scm:
  1015:17  3 (run-tea-loop "https://llm.example.net/v1" "[MY API 
  KEY]" "vllm/Qwen/Qwen3.8-27B" (("read" . #<<tool> description: 
  "Read whole text file, or optionally a subset of its 
  lines.\n\nLine numbers start from 1. Output is the raw file 
  contents without line numbers." parameters: (("path" 
  . #<<tool-parameter> type: "string" description: "File path to 
  read" required?: #t>) ("start-line" . #<<tool-parameter> type: 
  "integer" description: "Read file start…>) …))
In kaagum/openai.scm:
    67:29  2 (openai-models _ _)
In json/parser.scm:
   404:20  1 (json->scm _ #:null _ #:ordered _ #:concatenated _)
     40:2  0 (json-read-number #<input:delimited input port 
     7fa0ce03ed40>)

json/parser.scm:40:2: In procedure json-read-number:
Throw to key json-invalid' with args (#<input:delimited input port 
7fa0ce03ed40>)'.

Process acp-client(proxychains4)-39 stderr finished
--8<---------------cut here---------------end--------------->8---

In the Bifrost admin interface I see that my "hello" message has 
been processed, but the response never made it to Emacs.

-- 
Ricardo