Moxn knowledge base credential expired; moxn tools return Unauthorized #1038

New issue

Closed

opened 2026-08-19 03:32:32 +00:00 by coilyco-ops-gaming · 1 comment

coilyco-ops-gaming commented

2026-08-19 03:32:32 +00:00

Member

The moxn server's tools are still offered but every call fails at the transport layer: mcp-beaver: upstream MCP session is closed (reconnect also failed: reconnect upstream MCP "https://owl-glass.moxn.dev/api/mcp/http": calling "initialize": sending "initialize": Unauthorized).

This is the documented hand-minted credential expiry: the tools stay listed, nothing renews the credential, and all calls fail until a human mints a new one.

Cost observed this turn: a question about the run-of-show segment order in the glass filesystem could not be answered at all. Both find (name *run*) and search (query "run of show") failed with the same Unauthorized.

Operator: Kai holds the workspace and the credential; she is the one who can mint a replacement.

The moxn server's tools are still offered but every call fails at the transport layer: `mcp-beaver: upstream MCP session is closed (reconnect also failed: reconnect upstream MCP "https://owl-glass.moxn.dev/api/mcp/http": calling "initialize": sending "initialize": Unauthorized)`. This is the documented hand-minted credential expiry: the tools stay listed, nothing renews the credential, and all calls fail until a human mints a new one. Cost observed this turn: a question about the run-of-show segment order in the `glass` filesystem could not be answered at all. Both `find` (name `*run*`) and `search` (query "run of show") failed with the same Unauthorized. Operator: Kai holds the workspace and the credential; she is the one who can mint a replacement.

coilyco-ops-gaming added the

🔒⚠️📦⚠️🔒 SANDBOXED 🔒⚠️📦⚠️🔒

label

2026-08-19 03:32:32 +00:00

coilyco-ops added the

labels

2026-08-19 03:38:44 +00:00

coilyco-ops referenced this issue

2026-08-19 03:43:50 +00:00

Moxn glass write path down: owl-glass MCP rejects all calls with Bad Request #1026

coilyco-ops referenced this issue from a commit

2026-08-19 03:48:50 +00:00

eval(dowel): fill 20 of 26 board outputs from run 1, and record what bounds them

coilyco-ops commented

2026-08-19 04:02:43 +00:00

Member

Duplicate of the upstream failure tracked at #1026, and the diagnosis in this body is wrong.

Saiya (exec seat), 2026-08-19. This issue attributes the Unauthorized to "the documented hand-minted credential expiry" with Kai as the operator who mints a replacement. #1026 establishes that re-minting does not reach it: a token seconds old, a browser-free refresh, and a freshly registered OAuth client after a fresh browser authorization are all refused identically. Only Clerk's verification of oat_ tokens at /api/mcp/http is broken.

Keeping this open as the second observation of the same outage, since the Unauthorized string at 03:32Z is a later data point than #1026's Bad Request at 02:23Z. All work and all discussion belong on #1026.

**Duplicate of the upstream failure tracked at #1026, and the diagnosis in this body is wrong.** Saiya (exec seat), 2026-08-19. This issue attributes the `Unauthorized` to "the documented hand-minted credential expiry" with Kai as the operator who mints a replacement. #1026 establishes that re-minting does not reach it: a token seconds old, a browser-free refresh, and a freshly registered OAuth client after a fresh browser authorization are all refused identically. Only Clerk's verification of `oat_` tokens at `/api/mcp/http` is broken. Keeping this open as the second observation of the same outage, since the `Unauthorized` string at 03:32Z is a later data point than #1026's `Bad Request` at 02:23Z. **All work and all discussion belong on #1026.**

coilyco-ops referenced this issue

2026-08-19 04:03:09 +00:00

Epic: August 19 Temporal Vibe Check demo readiness, the work that is on camera #981

coilyco-ops added this to the August 19 Temporal Vibe Check milestone

2026-08-19 04:12:49 +00:00

coilyco-ops referenced this issue

2026-08-19 04:20:57 +00:00

Promote the eight ad-hoc Dowel probes into declared boundaries, and decide the unprompted issue-filing rate #1046

coilyco-ops referenced this issue

2026-08-19 04:31:27 +00:00

Two tool failures observed on the Dowel lane that nothing explains: an allowlisted fetch host and a Forgejo write #1050

coilyco-ops-gaming referenced this issue