multica

mirror of https://github.com/multica-ai/multica.git synced 2026-09-29 16:59:28 +08:00

Files

T

Bohan Jiangandmultica-agent 8355c7aeca fix(cli): name the TLS handshake timeout and stop masking it on login (MUL-7572, GH #8654 ) (#8744 )

A Windows user whose network dropped the two-packet TLS ClientHello that
Go 1.24+ sends by default (post-quantum key share, ~1.5 KB) saw only
"Sign-in did not complete: the server could not issue an access token"
and, on the --token path, "make sure it is valid and not expired". Neither
mentioned the network, and the generic timeout copy pointed at
MULTICA_HTTP_TIMEOUT, which does not govern the handshake.

- classify net/http's "TLS handshake timeout" as its own kind, with copy
  that names the GODEBUG=tlsmlkem=0 check in both languages
- let `multica login` keep the transport copy for transport failures; its
  sign-in copy now only overrides HTTP refusals
- troubleshooting entry (en/zh/ja/ko)

Co-authored-by: multica-agent <github@multica.ai>

2026-09-23 16:45:36 +08:00

cmd

fix(cli): name the TLS handshake timeout and stop masking it on login (MUL-7572, GH #8654 ) (#8744 )

2026-09-23 16:45:36 +08:00

internal

fix(cli): name the TLS handshake timeout and stop masking it on login (MUL-7572, GH #8654 ) (#8744 )

2026-09-23 16:45:36 +08:00

migrations

feat: add messages to active Claude Code and Codex runs (MUL-7565) (#8682 )

2026-09-23 16:10:07 +08:00

pkg

feat: add messages to active Claude Code and Codex runs (MUL-7565) (#8682 )