Re: [PATCH] Remove #:streaming? #t from HTTP requests to fix JSON parsing

[Arun Isaac <arunisaac@systemreboot.net>]

Hi jgart,

> Sorry about this. I used a DeepSeek model in the pi agent harness to
> work on the patch and description, and it looks like it hallucinated
> the technical details. The claim about gzip/streaming causing invalid
> JSON, and the openai-models workaround with accept-encoding: identity,
> don't seem to be real.

Dangers of vibe coding, best to avoid!

> Looking back at what I actually have, the closest thing to evidence is
> an error like this I took from an earlier screenshot when I captured
> the error:
>
> (error (code . -32603)
>        (message . "Agent process ended before completing request: exited abnormally with code 1"))
>
> This looks like a crashed subprocess, not a JSON parsing issue.

This prompted me to improve our debugging situation. So, I implemented
detailed tracing.
https://klaus.systemreboot.net/kaagum/commit/7918c9d422962d8dec4fb9fa410a51daa6d6ebe7/

Now, if you run kaagum with the "--trace-file=/path/to/some/file"
option, we should be able to see what's going on.

If you are on Emacs agent shell too, here's my setup:

(setq agent-shell-kaagum-command
      ;; replace with path to your kaagum
      "/gnu/store/lvxz7hdcwydhv7w8rnnhczl0xl6jlh7q-kaagum-0.1.0/bin/kaagum"
      agent-shell-kaagum-parameters
      '("--api-key-command=pass dev/openrouter.ai | awk '/^API Key:/ {print \$3}'"
        "--model=anthropic/claude-sonnet-4.6"
        "--trace-file=/tmp/logs"))

Regards,
Arun