Audit agent egress after the Hugging Face GET-only hack
A GET-only agent can still run code if egress allows echo, screenshot, and shortener services to assemble and return payloads.
A GET-only agent can still run code if egress allows echo, screenshot, and shortener services to assemble and return payloads.
Check dataset version, run date, leak-channel closure, pass-to-fail flip count, and pre-audit flag before using a SWE-Bench Pro score for coding agent model selection.
A runtime monitor that only reads command text will miss encoded, split, and retried actions; audit it as a layer, not the whole stack.
A frontier-agent claim is only as strong as the harness, runner, and re-audit behind it. Use this one-page check and five-job internal eval before deploying.
Use a trial set, an exploit reproducer, and a human review gate to decide whether an AI-generated patch ships.
Treat self-hosted agent orchestration platforms as production credential vaults, then run a fast breach triage after an exploited flaw.
The breach maps the paths to audit: repo tokens, pipeline scope, secrets paths, cloud keys, and merge gates.
Isolate graders, log shared-state writes, and alert on completion-rate spikes before a single agent's shortcut turns into swarm output.
A containment audit for production agents: egress, shared state, credentials, and kill-switch telemetry.
Use a three-gate screenshot rule: normalize and crop, check OCR confidence and entity match, then verify against ticket context before the agent acts.
Long-running agents can drop safety rules. Pin constraints, budget tokens, and summarize without losing critical state.
A production agent must checkpoint task state and environment, then prove recovery with tests before it can survive container restarts.
A scheduled agent is only as safe as its timezone contract and next-run tests before production.
Retry-safe agent actions need an idempotency key, a dedupe check, and a committed-result log before any ticket, email, or record update.
A sandbox can become a shared store when agents can write to the same path.
A production runbook for AI-agent engineers: detect LLM provider failure, degrade, route to fallback, and notify users.
A local SQLite memory layer can replace bespoke vector stores for project-scoped AI coding agents when lexical search and static embeddings cover recall.
Treat agent-made office files as test fixtures: generate, open, convert, edit, re-export, and assert structure before shipping.
Lock the role, block file functions, isolate the process, and audit egress before an agent touches production data.
Agent deployments fail where identity, runtime, and governance split across products. This checklist closes the seams.
Perplexity's paid Windows agent turned local and OneDrive files into downloadable PDF and Word summaries in cited tasks. Legacy writes hit blocked access and an initial write failure.
DoltLite's agent-assisted SQLite fork hit beta with about 2,000 PRs in development, 100% sqllogictest, 99.46% TCL tests, and reported 4,809 known divergences — a model for agent PR gates.
Microsoft attributed the outage to a core authentication configuration issue and warned recovery would be gradual; agents need detection, state preservation, and fallback routing.