{
  "schema_version": "1.1",
  "id": "weekly-2026-08-31",
  "slug": "2026-08-31",
  "issue_number": "008",
  "title": "feed7 Weekly #008",
  "description": "Six practical upgrades for safer tools, cleaner traces, stronger evals, and more portable agent sessions.",
  "published_at": "2026-08-31T00:00:00.000Z",
  "modified_at": "2026-08-30T18:04:42.666Z",
  "url": "https://feed7.dev/weekly/2026-08-31",
  "formats": {
    "html": "https://feed7.dev/weekly/2026-08-31",
    "json": "https://feed7.dev/weekly/2026-08-31.json",
    "markdown": "https://feed7.dev/weekly/2026-08-31.md"
  },
  "selection": {
    "rule": "Six source-backed signals and one distraction to leave out.",
    "mode": "ai",
    "ignore_item_id": "auto-d34e82eae2"
  },
  "items": [
    {
      "schema_version": "1.1",
      "id": "auto-105166eadd",
      "slug": "ai-agents-are-just-distributed-systems-now-salman-munaf--105166eadd",
      "url": "https://feed7.dev/p/ai-agents-are-just-distributed-systems-now-salman-munaf--105166eadd",
      "title": "AI Agents Are Just Distributed Systems Now — Salman Munaf, TikTok",
      "why_included": "Make mutating tools idempotent, persist each step, bound retries and spend, and treat timeouts as unknown outcomes.",
      "summary": "Once agents mutate external state, timeouts mean unknown outcomes. Builders need idempotent tools, bounded retries, scoped credentials, durable traces, and explicit recovery paths.",
      "practical_implication": "Design every agent tool like a distributed-system boundary. Persist each step, define the source of truth, treat memory as an invalidatable cache, and bind approvals to the exact action, actor, timestamp, parameters, and expiration.",
      "agent_context": "A tool timeout does not prove failure: the remote side may already have committed the action. The talk recommends request IDs, **idempotency keys**, status lookups, circuit breakers, compensation operations, and limits on turns, spend, and parallel calls.\n\nDesign every agent tool like a distributed-system boundary. Persist each step, define the source of truth, treat memory as an invalidatable cache, and bind approvals to the exact action, actor, timestamp, parameters, and expiration.\n\nA stronger model can reduce reasoning mistakes but cannot remove network ambiguity, stale state, or adversarial input. Some irreversible actions cannot be truly undone, so compensation and human approval remain domain-specific safeguards.",
      "source": {
        "name": "AI Engineer",
        "url": "https://www.youtube.com/watch?v=hD9-V56FNRI",
        "published_at": "2026-08-29T00:00:00.000Z"
      },
      "source_class": "video",
      "content_type": "Video",
      "layer": "agent",
      "domains": [
        "coding"
      ],
      "topics": [
        "harness-engineering",
        "tool-use",
        "agent-reliability"
      ],
      "verification": {
        "status": "source_linked",
        "label": "Source Linked",
        "method": "source_feed",
        "verified_at": null
      },
      "uncertainty": [],
      "connected_context": null,
      "lifecycle": "New",
      "published_at": "2026-08-29T00:00:00.000Z",
      "modified_at": "2026-08-29T00:00:00.000Z",
      "supersedes": [],
      "expires_at": null,
      "formats": {
        "html": "https://feed7.dev/p/ai-agents-are-just-distributed-systems-now-salman-munaf--105166eadd",
        "json": "https://feed7.dev/p/ai-agents-are-just-distributed-systems-now-salman-munaf--105166eadd.json",
        "markdown": "https://feed7.dev/p/ai-agents-are-just-distributed-systems-now-salman-munaf--105166eadd.md"
      }
    },
    {
      "schema_version": "1.1",
      "id": "auto-7a4a8849cf",
      "slug": "how-to-get-your-org-to-adopt-coding-agents-without-shipp-7a4a8849cf",
      "url": "https://feed7.dev/p/how-to-get-your-org-to-adopt-coding-agents-without-shipp-7a4a8849cf",
      "title": "How to Get Your Org to Adopt Coding Agents (Without Shipping Garbage) — Eyal Blum, Figma",
      "why_included": "Write executable checks before implementation, then split agent plans into independently validated, reviewable phases.",
      "summary": "Figma’s cautious agent adopters expose missing safeguards, not resistance. Use their feedback to improve verification, plans, review size, and the labeling of AI-generated work.",
      "practical_implication": "Make verification executable before implementation: use TDD, encode repeated checks deterministically, and split plans into independently validated, reviewable phases. Put the reason for the change first, and use skeptical maintainers’ feedback as the safety roadmap.",
      "agent_context": "Figma reports uneven agent adoption and says experienced engineers may be slowest because they see codebase risks first. One detailed plan turned an estimated **six weeks of coding into about one week**, including review.\n\nMake verification executable before implementation: use TDD, encode repeated checks deterministically, and split plans into independently validated, reviewable phases. Put the reason for the change first, and use skeptical maintainers’ feedback as the safety roadmap.\n\nThe workflow is still evolving and depends on planning and review effort that raw generation metrics can hide. AI also increases communication volume, so clearly separate human-written intent from generated descriptions to protect scarce reviewer attention.",
      "source": {
        "name": "AI Engineer",
        "url": "https://www.youtube.com/watch?v=5Bn0xro2ol8",
        "published_at": "2026-08-28T00:00:00.000Z"
      },
      "source_class": "video",
      "content_type": "Video",
      "layer": "agent",
      "domains": [
        "coding"
      ],
      "topics": [
        "coding-agents",
        "agent-reliability",
        "harness-engineering"
      ],
      "verification": {
        "status": "source_linked",
        "label": "Source Linked",
        "method": "source_feed",
        "verified_at": null
      },
      "uncertainty": [],
      "connected_context": null,
      "lifecycle": "New",
      "published_at": "2026-08-28T00:00:00.000Z",
      "modified_at": "2026-08-28T00:00:00.000Z",
      "supersedes": [],
      "expires_at": null,
      "formats": {
        "html": "https://feed7.dev/p/how-to-get-your-org-to-adopt-coding-agents-without-shipp-7a4a8849cf",
        "json": "https://feed7.dev/p/how-to-get-your-org-to-adopt-coding-agents-without-shipp-7a4a8849cf.json",
        "markdown": "https://feed7.dev/p/how-to-get-your-org-to-adopt-coding-agents-without-shipp-7a4a8849cf.md"
      }
    },
    {
      "schema_version": "1.1",
      "id": "auto-f8c22d41c8",
      "slug": "cursor-is-now-available-in-the-ai-sdk-harness-layer-f8c22d41c8",
      "url": "https://feed7.dev/p/cursor-is-now-available-in-the-ai-sdk-harness-layer-f8c22d41c8",
      "title": "Cursor is now available in the AI SDK harness layer",
      "why_included": "The HarnessAgent interface can reduce application changes when testing or switching among eight coding-agent harnesses.",
      "summary": "Vercel’s AI SDK can now run Cursor behind the same HarnessAgent interface as seven other coding agents, reducing application changes when swapping harnesses.",
      "practical_implication": "Use HarnessAgent as the application boundary if you expect to test or switch among Cursor, Claude Code, Codex, Cline, Deep Agents, Grok Build, OpenCode, and Pi. That keeps agent selection out of the surrounding application code.",
      "agent_context": "The official **@ai-sdk/harness-cursor** adapter adds Cursor to Vercel’s AI SDK harness layer. It connects through **Agent Client Protocol (ACP)** and joins seven other supported coding-agent harnesses.\n\nUse **HarnessAgent** as the application boundary if you expect to test or switch among Cursor, Claude Code, Codex, Cline, Deep Agents, Grok Build, OpenCode, and Pi. That keeps agent selection out of the surrounding application code.\n\nThe announcement establishes interface compatibility, but does not compare feature parity, behavior, or portability across harnesses. Agent-specific capabilities may still require separate validation.",
      "source": {
        "name": "Vercel",
        "url": "https://vercel.com/changelog/cursor-ai-sdk-harness-adapter",
        "published_at": "2026-08-27T00:00:00.000Z"
      },
      "source_class": "blog_post",
      "content_type": "Engineering Post",
      "layer": "tools",
      "domains": [
        "coding"
      ],
      "topics": [
        "agent-sdks",
        "coding-agents",
        "harness-engineering"
      ],
      "verification": {
        "status": "official_source",
        "label": "Official Source",
        "method": "source_feed",
        "verified_at": null
      },
      "uncertainty": [],
      "connected_context": null,
      "lifecycle": "New",
      "published_at": "2026-08-27T00:00:00.000Z",
      "modified_at": "2026-08-27T00:00:00.000Z",
      "supersedes": [],
      "expires_at": null,
      "formats": {
        "html": "https://feed7.dev/p/cursor-is-now-available-in-the-ai-sdk-harness-layer-f8c22d41c8",
        "json": "https://feed7.dev/p/cursor-is-now-available-in-the-ai-sdk-harness-layer-f8c22d41c8.json",
        "markdown": "https://feed7.dev/p/cursor-is-now-available-in-the-ai-sdk-harness-layer-f8c22d41c8.md"
      }
    },
    {
      "schema_version": "1.1",
      "id": "auto-790b02624c",
      "slug": "vercel-cli-expands-commands-for-dns-domains-and-projects-790b02624c",
      "url": "https://feed7.dev/p/vercel-cli-expands-commands-for-dns-domains-and-projects-790b02624c",
      "title": "Vercel CLI expands commands for DNS, domains, and projects",
      "why_included": "CLI 59.6.2 adds structured JSON for new admin commands while retaining confirmation gates for billable or destructive actions.",
      "summary": "Vercel CLI 59.6.2 adds agent-friendly control over DNS, domains, projects, observability, and membership, with JSON output and confirmation gates for risky actions.",
      "practical_implication": "Coding agents can now handle more Vercel administration without dashboard automation. Use the JSON surfaces for parsing, while retaining the built-in confirmation boundary around billable or destructive actions.",
      "agent_context": "**Vercel CLI 59.6.2 or later** adds commands for DNS record updates, domain renewal, project pause and resume, observability settings, and project membership. Every new command supports **structured JSON output**.\n\nCoding agents can now handle more Vercel administration without dashboard automation. Use the JSON surfaces for parsing, while retaining the built-in confirmation boundary around **billable or destructive actions**.\n\nTerminal access increases the impact of an over-broad agent instruction. Scope credentials and permissions carefully, and do not treat confirmation prompts as a substitute for reviewing the intended target and change.",
      "source": {
        "name": "Vercel",
        "url": "https://vercel.com/changelog/vercel-cli-expands-commands-for-dns-domains-and-projects",
        "published_at": "2026-08-28T00:00:00.000Z"
      },
      "source_class": "blog_post",
      "content_type": "Engineering Post",
      "layer": "infra",
      "domains": [
        "coding"
      ],
      "topics": [
        "tool-use",
        "dev-ux",
        "observability"
      ],
      "verification": {
        "status": "official_source",
        "label": "Official Source",
        "method": "source_feed",
        "verified_at": null
      },
      "uncertainty": [],
      "connected_context": null,
      "lifecycle": "New",
      "published_at": "2026-08-28T00:00:00.000Z",
      "modified_at": "2026-08-28T00:00:00.000Z",
      "supersedes": [],
      "expires_at": null,
      "formats": {
        "html": "https://feed7.dev/p/vercel-cli-expands-commands-for-dns-domains-and-projects-790b02624c",
        "json": "https://feed7.dev/p/vercel-cli-expands-commands-for-dns-domains-and-projects-790b02624c.json",
        "markdown": "https://feed7.dev/p/vercel-cli-expands-commands-for-dns-domains-and-projects-790b02624c.md"
      }
    },
    {
      "schema_version": "1.1",
      "id": "auto-7ebecc7b84",
      "slug": "swe-prime-fewer-trajectories-better-performance-7ebecc7b84",
      "url": "https://feed7.dev/p/swe-prime-fewer-trajectories-better-performance-7ebecc7b84",
      "title": "SWE-Prime: Fewer Trajectories, Better Performance",
      "why_included": "SWE-Prime's filtered 10% of coding traces beat the full resolved set, showing that passing outcomes are not automatically clean supervision.",
      "summary": "SWE-Prime finds that filtering coding-agent traces by process and segment quality can beat training on every resolved trajectory, reducing noisy imitation from redundant or risky steps.",
      "practical_implication": "The reported 10% trajectory subset beat training on the full resolved dataset, with relative gains up to 12.2% on SWE-Bench Pro and 24.2% on SWE-Bench Verified. Teams training coding models should evaluate how an issue was solved, not treat a passing outcome as clean supervision.",
      "agent_context": "SWE-Prime filters successful coding-agent traces in **two stages**: whole trajectories are screened for process quality, result quality, and representativeness, then semantic segments are judged for contribution, learnability, and risk. Only selected segments contribute to the training loss.\n\nThe reported **10% trajectory subset** beat training on the full resolved dataset, with relative gains up to **12.2% on SWE-Bench Pro** and **24.2% on SWE-Bench Verified**. Teams training coding models should evaluate how an issue was solved, not treat a passing outcome as clean supervision.\n\nAll segments remain in the input sequence to preserve context, so this is selective loss computation rather than simply deleting weak steps. The material reports benchmark results but does not establish whether the selection criteria transfer to other repositories, agents, or training setups.",
      "source": {
        "name": "arXiv",
        "url": "https://arxiv.org/abs/2608.27449v1",
        "published_at": "2026-08-27T00:00:00.000Z"
      },
      "source_class": "blog_post",
      "content_type": "Paper",
      "layer": "benchmark",
      "domains": [
        "coding",
        "data"
      ],
      "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-08-27T00:00:00.000Z",
      "modified_at": "2026-08-27T00:00:00.000Z",
      "supersedes": [],
      "expires_at": null,
      "formats": {
        "html": "https://feed7.dev/p/swe-prime-fewer-trajectories-better-performance-7ebecc7b84",
        "json": "https://feed7.dev/p/swe-prime-fewer-trajectories-better-performance-7ebecc7b84.json",
        "markdown": "https://feed7.dev/p/swe-prime-fewer-trajectories-better-performance-7ebecc7b84.md"
      }
    },
    {
      "schema_version": "1.1",
      "id": "auto-83d31714cc",
      "slug": "unclecode-crawl4ai-83d31714cc",
      "url": "https://feed7.dev/p/unclecode-crawl4ai-83d31714cc",
      "title": "unclecode/crawl4ai",
      "why_included": "Update exposed Crawl4AI deployments: v0.9.2 fixes streaming leaks, while older releases had critical RCE, SSRF, and auth flaws.",
      "summary": "Crawl4AI turns browser-rendered pages into Markdown or structured data for agent and RAG pipelines. v0.9.2 fixes streaming leaks and deployment issues after two security-focused releases.",
      "practical_implication": "Builders using web retrieval should update rather than pinning older Docker images, keep API authentication enabled, and treat crawl requests as untrusted input. v0.9.0 made the Docker server secure by default, while crash recovery and prefetch support help longer jobs.",
      "agent_context": "Crawl4AI provides async browser crawling, Markdown generation, schema-based extraction, sessions, proxies, caching, deep crawls, and an MCP connection. **v0.9.2** fixes a streaming task/page leak plus Docker auth, packaging, and GPU-build issues.\n\nBuilders using web retrieval should update rather than pinning older Docker images, keep API authentication enabled, and treat crawl requests as untrusted input. **v0.9.0** made the Docker server secure by default, while crash recovery and prefetch support help longer jobs.\n\nThe broad feature set increases deployment and browser-state complexity. **v0.8.7** fixed critical RCE, SSRF, auth-bypass, file-write, XSS, and JWT-secret problems, so exposed legacy servers warrant particular scrutiny; the synchronous Selenium path is also deprecated.",
      "source": {
        "name": "GitHub",
        "url": "https://github.com/unclecode/crawl4ai",
        "published_at": "2026-08-30T00:00:00.000Z"
      },
      "source_class": "tool",
      "content_type": "GitHub Repo",
      "layer": "tools",
      "domains": [
        "coding",
        "data"
      ],
      "topics": [
        "retrieval",
        "mcp",
        "tool-use"
      ],
      "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-08-30T00:00:00.000Z",
      "modified_at": "2026-08-30T00:00:00.000Z",
      "supersedes": [],
      "expires_at": null,
      "formats": {
        "html": "https://feed7.dev/p/unclecode-crawl4ai-83d31714cc",
        "json": "https://feed7.dev/p/unclecode-crawl4ai-83d31714cc.json",
        "markdown": "https://feed7.dev/p/unclecode-crawl4ai-83d31714cc.md"
      }
    },
    {
      "schema_version": "1.1",
      "id": "auto-d34e82eae2",
      "slug": "how-loveholidays-is-making-everyone-a-builder-with-codex-d34e82eae2",
      "url": "https://feed7.dev/p/how-loveholidays-is-making-everyone-a-builder-with-codex-d34e82eae2",
      "title": "How loveholidays is making everyone a builder with Codex",
      "why_included": "It offers no workflow, governance details, adoption data, or measured outcomes that a solo builder could reuse next session.",
      "summary": "loveholidays is extending Codex beyond software teams so more employees can turn ideas into products, but the supplied material gives no implementation details or measured outcomes.",
      "practical_implication": "Builders evaluating broader agent access should consider which product work non-engineers can safely own and what review boundaries they need.",
      "agent_context": "loveholidays says it is using **Codex** to make software development accessible **across the business**, not only within engineering.\n\nBuilders evaluating broader agent access should consider which product work non-engineers can safely own and what review boundaries they need.\n\nThe material provides no workflow, governance model, adoption numbers, or measured delivery gains, so it is evidence of direction rather than a reusable playbook.",
      "source": {
        "name": "OpenAI",
        "url": "https://openai.com/index/loveholidays",
        "published_at": "2026-08-26T00:00:00.000Z"
      },
      "source_class": "blog_post",
      "content_type": "Official Release",
      "layer": "industry",
      "domains": [
        "coding"
      ],
      "topics": [
        "adoption",
        "enterprise"
      ],
      "verification": {
        "status": "official_source",
        "label": "Official Source",
        "method": "source_feed",
        "verified_at": null
      },
      "uncertainty": [],
      "connected_context": null,
      "lifecycle": "New",
      "published_at": "2026-08-26T00:00:00.000Z",
      "modified_at": "2026-08-26T00:00:00.000Z",
      "supersedes": [],
      "expires_at": null,
      "formats": {
        "html": "https://feed7.dev/p/how-loveholidays-is-making-everyone-a-builder-with-codex-d34e82eae2",
        "json": "https://feed7.dev/p/how-loveholidays-is-making-everyone-a-builder-with-codex-d34e82eae2.json",
        "markdown": "https://feed7.dev/p/how-loveholidays-is-making-everyone-a-builder-with-codex-d34e82eae2.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."
}