-
Notifications
You must be signed in to change notification settings - Fork 0
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
docs/mcp-fleet.md: separate probe-attributed andrena facts from issue-body observations
epic-followup-2026-08-07-recover2-402-404Follow-ups from epic 2026-08-07-recover2-402-404Follow-ups from epic 2026-08-07-recover2-402-404P3Priority 3 — lowPriority 3 — lowStatus: Open.#424 In orrinfrazier/netops-agent;Upgrade the #404 name-lookup drift guard from line-local matching to a balanced-span call scanner
epic-followup-2026-08-07-recover2-402-404Follow-ups from epic 2026-08-07-recover2-402-404Follow-ups from epic 2026-08-07-recover2-402-404Status: Open.#423 In orrinfrazier/netops-agent;prompts/routing.md is never loaded — the incident-routing + hard-key contract reaches no live inference call
epic-followup-2026-08-07-recover2-402-404Follow-ups from epic 2026-08-07-recover2-402-404Follow-ups from epic 2026-08-07-recover2-402-404Status: Open.#422 In orrinfrazier/netops-agent;feat(mcp): invert zabbix method control to a $-anchored ZABBIX_API_WHITELIST
epic-followup-2026-08-07-recover2-402-404Follow-ups from epic 2026-08-07-recover2-402-404Follow-ups from epic 2026-08-07-recover2-402-404Status: Open.#421 In orrinfrazier/netops-agent;fix(prompts): few-shot exemplars and two playbooks still teach the nonexistent zabbix__icmppingloss
epic-followup-2026-08-07-recover2-402-404Follow-ups from epic 2026-08-07-recover2-402-404Follow-ups from epic 2026-08-07-recover2-402-404Status: Open.#420 In orrinfrazier/netops-agent;fix(eval): audit the 75 zabbix capability-probe triples that flipped to Present in #402
epic-followup-2026-08-07-recover2-402-404Follow-ups from epic 2026-08-07-recover2-402-404Follow-ups from epic 2026-08-07-recover2-402-404Status: Open.#419 In orrinfrazier/netops-agent;fix(mcp-client): redact_call_result skips unstructured content blocks, so zabbix_api output is never redacted
epic-followup-2026-08-07-recover2-402-404Follow-ups from epic 2026-08-07-recover2-402-404Follow-ups from epic 2026-08-07-recover2-402-404Status: Open.#418 In orrinfrazier/netops-agent;agent-core: is_error outcomes bypass --max-tool-output-bytes entirely, so a large error payload is unbounded
epic-followup-2026-08-07-382-386-402-385-404Follow-ups from epic 2026-08-07 recover 382/386/402/385/404 (name shortened: 50-char GH limit)Follow-ups from epic 2026-08-07 recover 382/386/402/385/404 (name shortened: 50-char GH limit)Status: Open.#415 In orrinfrazier/netops-agent;agent-core: fast_path::execute bypasses the #385 tool-output trim seam
epic-followup-2026-08-07-382-386-402-385-404Follow-ups from epic 2026-08-07 recover 382/386/402/385/404 (name shortened: 50-char GH limit)Follow-ups from epic 2026-08-07 recover 382/386/402/385/404 (name shortened: 50-char GH limit)Status: Open.#414 In orrinfrazier/netops-agent;context: --max-tool-output-bytes cannot reach the keep_fields projection; empty allowlist shrinks arrays by dropping whole elements
epic-followup-2026-08-07-382-386-402-385-404Follow-ups from epic 2026-08-07 recover 382/386/402/385/404 (name shortened: 50-char GH limit)Follow-ups from epic 2026-08-07 recover 382/386/402/385/404 (name shortened: 50-char GH limit)Status: Open.#413 In orrinfrazier/netops-agent;- Status: Open.#411 In orrinfrazier/netops-agent;
sessions: errored runs persist cost_usd = 0.0 — AgentError carries no usage
epic-followup-2026-08-06-382-402-384-386-385-404Follow-ups filed during epic 2026-08-06 (#382 #402 #384 #386 #385 #404)Follow-ups filed during epic 2026-08-06 (#382 #402 #384 #386 #385 #404)Status: Open.#407 In orrinfrazier/netops-agent;