{
  "schema_version": "1.1",
  "id": "weekly-2026-08-03",
  "slug": "2026-08-03",
  "issue_number": "004",
  "title": "feed7 Weekly #004",
  "description": "Six practical upgrades for agent environments, controls, observability, isolation, and evaluation.",
  "published_at": "2026-08-03T00:00:00.000Z",
  "modified_at": "2026-08-02T18:07:47.416Z",
  "url": "https://feed7.dev/weekly/2026-08-03",
  "formats": {
    "html": "https://feed7.dev/weekly/2026-08-03",
    "json": "https://feed7.dev/weekly/2026-08-03.json",
    "markdown": "https://feed7.dev/weekly/2026-08-03.md"
  },
  "selection": {
    "rule": "Six source-backed signals and one distraction to leave out.",
    "mode": "ai",
    "ignore_item_id": "auto-6d964f10c3"
  },
  "items": [
    {
      "schema_version": "1.1",
      "id": "auto-5077dc1992",
      "slug": "how-we-set-up-our-cloud-agent-environment-5077dc1992",
      "url": "https://feed7.dev/p/how-we-set-up-our-cloud-agent-environment-5077dc1992",
      "title": "How we set up our cloud agent environment",
      "why_included": "Treat the dev environment as agent infrastructure with Linux parity, one discoverable CLI, end-to-end tests, and automated repair.",
      "summary": "Cursor’s cloud-agent adoption grew after it treated the dev environment as agent infrastructure: Linux parity, one discoverable CLI, end-to-end testing, and automated repair.",
      "practical_implication": "Treat the development environment as part of the agent harness. Match cloud and local dependencies, replace fragile command sequences with one discoverable interface, expose verification workflows, and let supervisors own long-running processes.",
      "agent_context": "Cursor moved its monorepo onto agent-ready Linux VMs, centralized startup and utilities in an internal CLI, and added end-to-end computer-use testing. Cloud agents went from **roughly 1 in 10 merged PRs in December** to **more than half today**.\n\nTreat the development environment as part of the agent harness. Match cloud and local dependencies, replace fragile command sequences with one discoverable interface, expose verification workflows, and let supervisors own long-running processes.\n\nSkills alone only helped at the margins because the underlying commands remained convoluted. Cursor also built **Cursor Cloud MCP** and **Cloud Doctor** to diagnose and repair environment failures, but the adoption figures are internal and do not isolate which change caused the increase.",
      "source": {
        "name": "Cursor",
        "url": "https://cursor.com/blog/cloud-agent-environment",
        "published_at": "2026-07-30T00:00:00.000Z"
      },
      "source_class": "blog_post",
      "content_type": "Engineering Post",
      "layer": "agent",
      "domains": [
        "coding"
      ],
      "topics": [
        "cloud-agents",
        "harness-engineering",
        "skills"
      ],
      "verification": {
        "status": "official_source",
        "label": "Official Source",
        "method": "source_feed",
        "verified_at": null
      },
      "uncertainty": [],
      "connected_context": null,
      "lifecycle": "New",
      "published_at": "2026-07-30T00:00:00.000Z",
      "modified_at": "2026-07-30T00:00:00.000Z",
      "supersedes": [],
      "expires_at": null,
      "formats": {
        "html": "https://feed7.dev/p/how-we-set-up-our-cloud-agent-environment-5077dc1992",
        "json": "https://feed7.dev/p/how-we-set-up-our-cloud-agent-environment-5077dc1992.json",
        "markdown": "https://feed7.dev/p/how-we-set-up-our-cloud-agent-environment-5077dc1992.md"
      }
    },
    {
      "schema_version": "1.1",
      "id": "auto-be3ca53745",
      "slug": "gemini-api-managed-agents-3-6-flash-hooks-and-more-be3ca53745",
      "url": "https://feed7.dev/p/gemini-api-managed-agents-3-6-flash-hooks-and-more-be3ca53745",
      "title": "Gemini API Managed Agents: 3.6 Flash, hooks, and more",
      "why_included": "Use pre- and post-tool hooks for policy checks, and cap autonomous loops with max_total_tokens while preserving resumable state.",
      "summary": "Gemini Managed Agents now add model selection, sandbox hooks, token caps, schedules, and free-tier access, covering several controls needed for unattended coding work.",
      "practical_implication": "Add hooks where tool calls need policy checks, linting, or audit output, and set max_total_tokens on autonomous loops. A capped run pauses as incomplete while preserving its environment, so it can resume with a new budget and previous interaction ID.",
      "agent_context": "Gemini Managed Agents now default to **Gemini 3.6 Flash**. The service adds pre- and post-tool hooks, explicit model selection, scheduled triggers, free-tier access, environment management, and persistent files across scheduled runs.\n\nAdd hooks where tool calls need policy checks, linting, or audit output, and set **max_total_tokens** on autonomous loops. A capped run pauses as incomplete while preserving its environment, so it can resume with a new budget and previous interaction ID.\n\nThe agent remains a preview identified as antigravity-preview-05-2026. Scheduled runs reuse a sandbox, which is useful for stateful work but makes cleanup, state drift, and hook failure behavior important operational concerns.",
      "source": {
        "name": "Google",
        "url": "https://blog.google/innovation-and-ai/technology/developers-tools/expanding-managed-agents-gemini-api-3-6-flash-hooks/",
        "published_at": "2026-07-28T00:00:00.000Z"
      },
      "source_class": "blog_post",
      "content_type": "Official Release",
      "layer": "tools",
      "domains": [
        "coding",
        "security"
      ],
      "topics": [
        "cloud-agents",
        "sandboxing",
        "tool-use"
      ],
      "verification": {
        "status": "official_source",
        "label": "Official Source",
        "method": "source_feed",
        "verified_at": null
      },
      "uncertainty": [],
      "connected_context": null,
      "lifecycle": "New",
      "published_at": "2026-07-28T00:00:00.000Z",
      "modified_at": "2026-07-28T00:00:00.000Z",
      "supersedes": [],
      "expires_at": null,
      "formats": {
        "html": "https://feed7.dev/p/gemini-api-managed-agents-3-6-flash-hooks-and-more-be3ca53745",
        "json": "https://feed7.dev/p/gemini-api-managed-agents-3-6-flash-hooks-and-more-be3ca53745.json",
        "markdown": "https://feed7.dev/p/gemini-api-managed-agents-3-6-flash-hooks-and-more-be3ca53745.md"
      }
    },
    {
      "schema_version": "1.1",
      "id": "auto-179f4fe13f",
      "slug": "ai-gateway-logs-now-have-a-dedicated-page-179f4fe13f",
      "url": "https://feed7.dev/p/ai-gateway-logs-now-have-a-dedicated-page-179f4fe13f",
      "title": "AI Gateway logs now have a dedicated page",
      "why_included": "Trace cost, tokens, latency, routing, cache use, and provider fallbacks by request ID, then export filtered runs for analysis.",
      "summary": "AI Gateway’s dedicated logs expose per-request cost, tokens, latency, routing, and provider fallbacks, making agent failures and spend anomalies easier to trace.",
      "practical_implication": "Use filters and request-ID search to debug agent failures or compare routing behavior. Filtered views are shareable by URL and exportable as CSV or JSON, which makes targeted cost and reliability analysis easier.",
      "agent_context": "The new **Logs page** lists gateway requests with cost, token counts, duration, model, provider, and region. Request details include time to first token, cache and reasoning tokens, policy flags, and the ordered fallback path.\n\nUse filters and request-ID search to debug agent failures or compare routing behavior. Filtered views are shareable by URL and exportable as **CSV or JSON**, which makes targeted cost and reliability analysis easier.\n\nThe page records what happened but does not define alerts, retention, or automated remediation. Diagnosis still requires interpreting provider failures, routing-budget exhaustion, and latency in the context of the agent run.",
      "source": {
        "name": "Vercel",
        "url": "https://vercel.com/changelog/ai-gateway-logs",
        "published_at": "2026-07-31T00:00:00.000Z"
      },
      "source_class": "blog_post",
      "content_type": "Engineering Post",
      "layer": "infra",
      "domains": [
        "coding",
        "data"
      ],
      "topics": [
        "observability",
        "gateways",
        "agent-reliability"
      ],
      "verification": {
        "status": "official_source",
        "label": "Official Source",
        "method": "source_feed",
        "verified_at": null
      },
      "uncertainty": [],
      "connected_context": null,
      "lifecycle": "New",
      "published_at": "2026-07-31T00:00:00.000Z",
      "modified_at": "2026-07-31T00:00:00.000Z",
      "supersedes": [],
      "expires_at": null,
      "formats": {
        "html": "https://feed7.dev/p/ai-gateway-logs-now-have-a-dedicated-page-179f4fe13f",
        "json": "https://feed7.dev/p/ai-gateway-logs-now-have-a-dedicated-page-179f4fe13f.json",
        "markdown": "https://feed7.dev/p/ai-gateway-logs-now-have-a-dedicated-page-179f4fe13f.md"
      }
    },
    {
      "schema_version": "1.1",
      "id": "auto-fb423aadb9",
      "slug": "run-multiple-isolated-agents-in-a-single-sandbox-fb423aadb9",
      "url": "https://feed7.dev/p/run-multiple-isolated-agents-in-a-single-sandbox-fb423aadb9",
      "title": "Run multiple isolated agents in a single Sandbox",
      "why_included": "Give each agent a private Linux user and expose only selected collaboration files through a shared group directory.",
      "summary": "Vercel Sandbox can now isolate agents as Linux users while exposing selected files through a shared group directory. This gives multi-agent harnesses a simpler permission boundary.",
      "practical_implication": "Create one user per agent and expose only the workspace they need through a group. This makes coder-reviewer or other multi-agent roles easier to separate without provisioning a sandbox for each role.",
      "agent_context": "The **@vercel/sandbox SDK** now supports multiple Linux users and groups. Each agent gets a **private home directory**; users cannot read, write, or list one another’s files, while a **shared group directory** supports collaboration.\n\nCreate one user per agent and expose only the workspace they need through a group. This makes coder-reviewer or other multi-agent roles easier to separate without provisioning a sandbox for each role.\n\nThe boundary is user and group permissions inside one Sandbox. The material does not claim separate kernels, resource quotas, or protection from vulnerabilities that cross operating-system user boundaries.",
      "source": {
        "name": "Vercel",
        "url": "https://vercel.com/changelog/run-multiple-isolated-agents-in-a-single-sandbox",
        "published_at": "2026-07-30T00:00:00.000Z"
      },
      "source_class": "blog_post",
      "content_type": "Engineering Post",
      "layer": "infra",
      "domains": [
        "coding",
        "security"
      ],
      "topics": [
        "sandboxing",
        "multi-agent",
        "agent-reliability"
      ],
      "verification": {
        "status": "official_source",
        "label": "Official Source",
        "method": "source_feed",
        "verified_at": null
      },
      "uncertainty": [],
      "connected_context": null,
      "lifecycle": "New",
      "published_at": "2026-07-30T00:00:00.000Z",
      "modified_at": "2026-07-30T00:00:00.000Z",
      "supersedes": [],
      "expires_at": null,
      "formats": {
        "html": "https://feed7.dev/p/run-multiple-isolated-agents-in-a-single-sandbox-fb423aadb9",
        "json": "https://feed7.dev/p/run-multiple-isolated-agents-in-a-single-sandbox-fb423aadb9.json",
        "markdown": "https://feed7.dev/p/run-multiple-isolated-agents-in-a-single-sandbox-fb423aadb9.md"
      }
    },
    {
      "schema_version": "1.1",
      "id": "auto-7bc753b969",
      "slug": "change2task-from-repository-changes-to-executable-coding-7bc753b969",
      "url": "https://feed7.dev/p/change2task-from-repository-changes-to-executable-coding-7bc753b969",
      "title": "Change2Task: From Repository Changes to Executable Coding Agent Tasks and Environments",
      "why_included": "Turn merged PR history into renewable eval tasks while preserving healthy, reconstructed, and restored repository states.",
      "summary": "Change2Task converts merged PR history into executable coding-agent tasks on current repository states. It could expand continuous eval sets while reducing stale environments and repeated setup.",
      "practical_implication": "Use repository history as renewable eval data, but preserve the full lifecycle: healthy base, reconstructed task state, and restored state. The five tested families include bug fixes, features, tests, API migrations, and security repairs.",
      "agent_context": "Change2Task turns merged pull requests into verified tasks on modern repository revisions using **Patch Reversal, Code Mapping, or Agent Reconstruction**. Across **1,130 eligible changes**, it constructed verified tasks at a 79.6% rate.\n\nUse repository history as renewable eval data, but preserve the full lifecycle: healthy base, reconstructed task state, and restored state. The five tested families include bug fixes, features, tests, API migrations, and security repairs.\n\nIt recovered **29.2% more verified tasks** than a PR-based baseline and reached up to 98.0% matched outcome agreement. These are construction results from the evaluated repositories, not proof that generated tasks represent every real maintenance workload.",
      "source": {
        "name": "arXiv",
        "url": "https://arxiv.org/abs/2607.28591v1",
        "published_at": "2026-07-30T00:00:00.000Z"
      },
      "source_class": "blog_post",
      "content_type": "Paper",
      "layer": "benchmark",
      "domains": [
        "coding",
        "security"
      ],
      "topics": [
        "coding-agents",
        "agent-evals",
        "benchmark-integrity"
      ],
      "verification": {
        "status": "needs_review",
        "label": "Needs Review",
        "method": "unverified",
        "verified_at": null
      },
      "uncertainty": [
        "Automatically selected from source material; feed7 has not independently tested the claim."
      ],
      "connected_context": null,
      "lifecycle": "New",
      "published_at": "2026-07-30T00:00:00.000Z",
      "modified_at": "2026-07-30T00:00:00.000Z",
      "supersedes": [],
      "expires_at": null,
      "formats": {
        "html": "https://feed7.dev/p/change2task-from-repository-changes-to-executable-coding-7bc753b969",
        "json": "https://feed7.dev/p/change2task-from-repository-changes-to-executable-coding-7bc753b969.json",
        "markdown": "https://feed7.dev/p/change2task-from-repository-changes-to-executable-coding-7bc753b969.md"
      }
    },
    {
      "schema_version": "1.1",
      "id": "auto-cc8e132c61",
      "slug": "how-enabling-two-settings-tripled-our-scores-on-the-arc--cc8e132c61",
      "url": "https://feed7.dev/p/how-enabling-two-settings-tripled-our-scores-on-the-arc--cc8e132c61",
      "title": "How enabling two settings tripled our scores on the ARC-AGI-3 benchmark",
      "why_included": "Record reasoning retention and compaction with the model name because runtime settings can materially alter agent eval results.",
      "summary": "Two API settings—reasoning retention and compaction—reportedly tripled GPT-5.6’s ARC-AGI-3 score. Agent evals should treat runtime configuration as part of the tested system.",
      "practical_implication": "Record these settings alongside the model name in agent evaluations. Configuration can materially affect results, so defaults and explicit settings should not be compared as equivalent systems.",
      "agent_context": "OpenAI says enabling **reasoning retention** and **compaction** produced **3× ARC-AGI-3 scores** for GPT-5.6 while also improving efficiency.\n\nRecord these settings alongside the model name in agent evaluations. Configuration can materially affect results, so defaults and explicit settings should not be compared as equivalent systems.\n\nThe supplied material provides no absolute scores, token usage, latency, or experimental detail, leaving the size and generality of the efficiency gain unclear.",
      "source": {
        "name": "OpenAI",
        "url": "https://openai.com/index/how-two-settings-tripled-our-arc-agi-3-scores",
        "published_at": "2026-07-29T00:00:00.000Z"
      },
      "source_class": "blog_post",
      "content_type": "Official Release",
      "layer": "benchmark",
      "domains": [],
      "topics": [
        "agent-evals",
        "benchmark-integrity",
        "context-caching"
      ],
      "verification": {
        "status": "official_source",
        "label": "Official Source",
        "method": "source_feed",
        "verified_at": null
      },
      "uncertainty": [],
      "connected_context": null,
      "lifecycle": "New",
      "published_at": "2026-07-29T00:00:00.000Z",
      "modified_at": "2026-07-29T00:00:00.000Z",
      "supersedes": [],
      "expires_at": null,
      "formats": {
        "html": "https://feed7.dev/p/how-enabling-two-settings-tripled-our-scores-on-the-arc--cc8e132c61",
        "json": "https://feed7.dev/p/how-enabling-two-settings-tripled-our-scores-on-the-arc--cc8e132c61.json",
        "markdown": "https://feed7.dev/p/how-enabling-two-settings-tripled-our-scores-on-the-arc--cc8e132c61.md"
      }
    },
    {
      "schema_version": "1.1",
      "id": "auto-6d964f10c3",
      "slug": "how-gpt-5-6-fuses-frontier-intelligence-with-frontier-ef-6d964f10c3",
      "url": "https://feed7.dev/p/how-gpt-5-6-fuses-frontier-intelligence-with-frontier-ef-6d964f10c3",
      "title": "How GPT-5.6 fuses frontier intelligence with frontier efficiency",
      "why_included": "The supplied material offers no prices, benchmarks, latency, or task-level evidence to guide a routing or migration decision.",
      "summary": "OpenAI positions GPT-5.6 as delivering more useful output per dollar across inference and agent workflows. The supplied material has no metrics for judging routing or migration decisions.",
      "practical_implication": "Builders should evaluate the model on complete agent runs, including reasoning and tool calls, rather than comparing only per-token pricing.",
      "agent_context": "OpenAI says **GPT-5.6** improves efficiency across **models, inference, and agentic workflows**, with more useful output delivered per dollar.\n\nBuilders should evaluate the model on complete agent runs, including reasoning and tool calls, rather than comparing only per-token pricing.\n\nThe supplied material contains no prices, benchmarks, latency figures, or task-level evidence, so it does not establish which workloads benefit or by how much.",
      "source": {
        "name": "OpenAI",
        "url": "https://openai.com/index/gpt-5-6-frontier-intelligence-efficiency",
        "published_at": "2026-07-29T00:00:00.000Z"
      },
      "source_class": "blog_post",
      "content_type": "Official Release",
      "layer": "model",
      "domains": [],
      "topics": [
        "model-selection",
        "reasoning"
      ],
      "verification": {
        "status": "official_source",
        "label": "Official Source",
        "method": "source_feed",
        "verified_at": null
      },
      "uncertainty": [],
      "connected_context": null,
      "lifecycle": "New",
      "published_at": "2026-07-29T00:00:00.000Z",
      "modified_at": "2026-07-29T00:00:00.000Z",
      "supersedes": [],
      "expires_at": null,
      "formats": {
        "html": "https://feed7.dev/p/how-gpt-5-6-fuses-frontier-intelligence-with-frontier-ef-6d964f10c3",
        "json": "https://feed7.dev/p/how-gpt-5-6-fuses-frontier-intelligence-with-frontier-ef-6d964f10c3.json",
        "markdown": "https://feed7.dev/p/how-gpt-5-6-fuses-frontier-intelligence-with-frontier-ef-6d964f10c3.md"
      }
    }
  ],
  "agent_instruction": "Use these items as source-backed context. Do not invent claims beyond linked material. Prefer practical implications for solo developer work. If sources conflict, call it out."
}