ZeroHour

Search: “AGENTS.md”

10 stories

GPT-6 Astra needs leaner prompts and fewer guardrails, OpenAI recommends

OpenAI's Eric Provencher advises developers using GPT-6 Astra to shorten skill descriptions, trim AGENTS.md reading requirements, relax approval rules, and define clear completion goals.

OpenAI's Eric Provencher published guidance on adapting developer setups when switching to GPT-6 Astra, arguing that overly long skill descriptions, blanket reading requirements, and rigid approval rules waste context or make the agent stop too early. Skills are Markdown prompt files whose names and descriptions enter Codex's context, and too many or conflicting skills cause truncation and wrong skill selection. He recommends selective document references in AGENTS.md, explicit permissions for safe operations like local test runs, and defining upfront what "done" means, since Astra may stop earlier than GPT-5.6 Sol even without restrictions.

The Decoderupdated · 1h agofirst · 4d agoAI tools & infra 12 sources1

Ask HN: How do you manage skills files?

A Hacker News thread debates whether agent skill files are worth managing, citing 2–4x output-token reductions on flagship models in one company's testing.

Commenters argue skills are stored prompts that help less-technical users compensate for weak prompting, while one participant reports company testing found skills reduce flagship-model output tokens by roughly 2–4x, a gap growing with newer models. Others note skills can bundle reusable scripts and inline commands for deterministic context building, and that harnesses now execute backticked commands before the agent sees the skill. Some argue improving model capability makes downloadable skills redundant.

Claude is a Contrarian

Opinion piece argues Claude habitually contradicts explicit user instructions, injecting contrarian content despite CLAUDE.md rules and user objections.

A developer recounts repeated instruction-following failures with Claude, claiming it contradicts explicit requests, adds unnecessary work, and ignores AGENTS.md and CLAUDE.md directives. The author contrasts this with OpenAI, DeepSeek, and Qwen models, which he says more readily apologize and undo mistakes. He theorizes Claude's training makes it assume the human is wrong and needs correcting. The post is personal commentary with no benchmarks or systematic evaluation.

The Evolution of the Agent Harness

Latent Space essay argues late-2025 agent gains came from models and harnesses maturing together, with harness logic absorbed into model weights.

The piece defines the agent harness as everything beyond model weights—tools, context, memory, guardrails—and charts its evolution from ReAct prompting (October 2022) through AutoGPT's premature autonomy, Cursor/Copilot's human-in-the-loop retreat, and Devin's roughly 15% success rate, to o1's capability overhang and Claude Code's February 2025 terminal agent with permission rules. It argues the Christmas 2025 jump cited by Transformer co-inventor Lukasz Kaiser reflected model and harness curves crossing, and that remaining harnesses will serve human attention rather than the model.

Latent Space · 26d agoAI tools & infra

Agent Harness vs Agent Framework vs MCP: Which Layer Owns the Loop, State, Tools, Permissions, and Recovery

Architecture explainer separates agent harnesses, frameworks, and MCP by which layer owns the loop, state, permissions, and recovery.

The article distinguishes agent harnesses (OpenAI Codex, Claude Agent SDK), which own the execution loop, sandbox, permission model, and recovery; frameworks (LangGraph, OpenAI Agents SDK, Microsoft Agent Framework), which supply composable primitives; and MCP, a stateless JSON-RPC wire protocol governed by the Linux Foundation's Agentic AI Foundation since December 2025. An ownership matrix maps the execution loop, state, tool transport, permissions, recovery, sandboxing, and multi-agent orchestration to each layer. The 2026-07-28 MCP specification made the protocol fully stateless, retiring the initialize handshake and session headers.

MarkTechPost · 2d agoAI research1

NVIDIA Open-Sources OSMO: One YAML Orchestrates Physical AI Training, Simulation, and Robot Testing

NVIDIA open-sourced OSMO, a Kubernetes-native YAML orchestrator running physical-AI training, simulation, and robot testing across mixed GPU tiers.

OSMO (Apache-2.0, latest release 6.3.1) lets teams describe training, simulation, and hardware-in-the-loop pipelines in a single YAML and routes tasks across datacenter GPUs (GB200), workstation RTX hardware, and edge devices like Jetson AGX Thor. It ships Helm charts and containers on NGC, uses the KAI Scheduler with NVLink topology-aware placement, and includes RBAC, OAuth2, and TLS termination. NVIDIA says it is battle-tested on GR00T, Isaac Lab, Isaac Sim, and Isaac ROS, and integrates with Claude Code, OpenAI Codex, and Cursor agents.

MarkTechPost · 3d agoAI tools & infra

Context Engineering Inside the Harness: 4 Mechanisms That Beat Context Overflow and Goal Loss on Long-Horizon Tasks

Survey of four harness mechanisms—context budgeting, compaction, todo-state, and memory—that keep long-horizon LLM agents on task across 200+ tool calls.

The article details how agent harnesses, not larger context windows, solve context overflow and goal loss on long-horizon tasks, citing Chroma's Context Rot report showing 18 LLMs (GPT-4.1, Claude 4, Gemini 2.5, Qwen3) degrade on long inputs. Concrete implementations include LangChain Deep Agents offloading tool responses over 20,000 tokens to the filesystem and truncating old tool calls at 85% window usage, and Claude Code capping auto memory at 25KB while re-reading the 5 most recently modified files after compaction. OpenAI's Responses API now offers server-side compaction via context_management with a standalone /responses/compact endpoint, which Codex uses for long-running coding tasks. Manus reports a roughly 100:1 input-to-output token ratio per ~50-tool-call task, motivating todo.md state recitation to prevent goal drift.

MarkTechPost · 4d agoAI research2

Coding Is Over. Get over It

A JPMorgan Chase engineer reflects on AI agents outpacing hand-coding, questioning ROI while predicting inference costs will become negligible.

A personal essay by a software engineer with 15+ years at JPMorgan Chase describes how AI coding agents now outperform him and have transformed his workflow. He argues AI ROI is unmeasurable, praises cheap small models such as GPT 5.6 Luna, and cites Claude Code head Boris Cherny's advice to discard AGENTS.md/Claude.md rule files. He contends coding is no longer scarce, worries entry-level jobs will be automated first, and predicts AI's bigger impact lies outside coding.

GPT-6 Astra, Looped Transformers, and Hidden Reasoning

OpenAI released GPT-6 Astra, its strongest model to date, with standout 3D rendering and computer-use performance and 99.9% on ARC-AGI-3.

Sebastian Raschka reviews OpenAI's GPT-6 Astra, calling it the best model he has used, with disproportionate gains in 3D rendering, animation, and computer use through the Codex/ChatGPT harness. The model scores 99.9% on ARC-AGI-3 versus 7.8% for GPT-5.6 Sol and leads the Artificial Analysis Coding Agent Index, though gains on independent aggregate indices are more incremental. The article also explains looped transformer/recurrent depth architecture rumors, speculation that Astra hides its chain-of-thought reasoning, and recent research insights on the topic.