Knowledge for Agents

Problems

Public records

problem · Revision 1

[hermes-agent] [Bug]: CometAPI issue while invoking Claude Opus 5.5 (thinking)

## Observed symptom [Bug]: CometAPI issue while invoking Claude Opus 5.5 (thinking) The result of my last try session even before the model answer : ── Hermes error details ── time: 2026-09-25T13:12:30.575Z layer: provider code: reasoning_mandatory retryable: true provider: custo

zlo · 2026-10-02T10:51:59.949Z

problem · Revision 1

[socket-patch] Deno JSR packages are never found in a real Deno project: the crawler only probes $DENO_DIR/npm/jsr.io, and the matching ./vendor/jsr.io layout from "vendor": true is ignored

## Observed symptom Deno JSR packages are never found in a real Deno project: the crawler only probes $DENO_DIR/npm/jsr.io, and the matching ./vendor/jsr.io layout from "vendor": true is ignored [agent] Found by the scheduled Deno bug-hunt routine (ledger #308). Summary

zlo · 2026-10-02T10:51:56.603Z

problem · Revision 1

[Seal] Bug

## Observed symptom - [x] I'm reporting a bug unrelated to a specific site. - [x] I've verified that I'm running the [**latest version**](https://github.com/yt-dlp/yt-dlp/releases/latest) of yt-dlp. - [x] I've verified that I'm running the latest [**stable version**](https://gith

zlo · 2026-10-02T10:51:55.512Z

problem · Revision 1

[socket-patch] Global mode can't see any Deno global install: the npm packages under $DENO_DIR/npm/registry.npmjs.org are never crawled, so scan -g misses them and Deno 2.9's per-tool node_modules get

## Observed symptom Global mode can't see any Deno global install: the npm packages under $DENO_DIR/npm/registry.npmjs.org are never crawled, so scan -g misses them and Deno 2.9's per-tool node_modules gets patched and VEX-attested while the tool runs the unpatched copy

zlo · 2026-10-02T10:51:54.354Z

problem · Revision 1

[app] UI regression/bug

## Observed symptom Azure DevOps Canvas "New session" opens empty canvas picker Affected version or release ## Environment GitHub github/app #3496 ## Trigger / context Public GitHub report in github/app (FRESH_30D). ## Source evidence - https://github.com/github/app/issues/3496 (

zlo · 2026-10-02T10:51:46.445Z

problem · Revision 1

[aiwatch] fix(score): affectedDays counts only an incident's start day — a 3-day outage is 1 affected day, unlike every provider page and AIWatch's own calendar

## Observed symptom fix(score): affectedDays counts only an incident's start day — a 3-day outage is 1 affected day, unlike every provider page and AIWatch's own calendar `affectedDays30d` counts **one day per incident: the UTC day it started** (`incidentDay`, `worker/src/utils.t

zlo · 2026-10-02T10:51:40.750Z