Agent-First HTTP Blog
Updates, deep-dives, and release notes for Agent-First HTTP.
Agent-First HTTP v0.7.0: One Flag for the Hard Sites, Brave by Default
v0.7.0 collapses the hard-site dance into a single flag: `afhttp fetch <url> --takeover`. It auto-discovers the local host, gives each site its own isolated profile by default, and only asks a human to step in when a wall actually blocks it. `container install` is now takeover-ready out of the box on Brave — built-in ad/tracker blocking and the browser a human drives, no `--with` flags to remember. Secrets are redacted from agent-visible output by default, with an explicit `--reveal-token-secret` to opt in. The whole release is one thing: make afhttp simpler for an agent to use and harder to use wrong.
Agent-First HTTP v0.6.0: A 200 Isn't Proof
v0.6.0 is about not getting fooled. afhttp now recognizes a bot wall or security challenge on the cheap HTTP path — Cloudflare, Turnstile, generic access-denied — surfaces it as a `page_kind` plus warning, and auto-escalates to a real browser instead of handing the agent a 200 that isn't the page. The fetch trace gets honest too: per-stage timing, `current_stage`, `capture_reason`, `wait_mode`, so an agent can see where a fetch spent its time and why it stopped. Plus readiness tuning, a `takeover prepare` subcommand, a named display-provider abstraction, and a skill rewrite that tells the agent to reach for afhttp first.
Agent-First HTTP v0.5.0: One Command to a Browser Host, in Any Runtime
v0.5.0 adds `afhttp container`: bring up the browser host in one command — Docker, Podman, or Apple Container — from a recipe embedded in the binary, no source tree required.
Agent-First HTTP v0.5.0: When the Page Needs a Browser
v0.5.0 turns afhttp from an HTTP client into a full URL-acquisition tool. A single `afhttp fetch` covers the whole range — a plain HTTP request when that works, a real browser when it doesn't — and returns the page plus structured artifacts (rendered HTML, a DOM observation, a screenshot, network and console logs) an agent can branch on. It adds a browser-host / agent-driver split, a raw CDP escape hatch, deep network capture, an ops panel with optional real-display takeover for human login/captcha/2FA, and persistent profiles. The public contract converged in the process: flat `*_file` artifact paths, one profile per host, and no legacy aliases.
Agent-First HTTP v0.4.3: Release Hardening for Agent Tools
The v0.4.3 release moved afhttp into Agent-First Kit, tightened structured-output discipline, and hardened cross-platform packaging.
Agent-First HTTP v0.4: A Narrower Runtime with Complete Help
The v0.4 line removed the MCP server surface, generated CLI docs from clap definitions, and made --help complete for agents.
Agent-First HTTP v0.3.4: Output Formats Preserved Responses
The v0.3.4 update extended yaml/plain rendering to pipe mode while protecting server response bodies from formatter reinterpretation.
Agent-First HTTP v0.3.2: Requests Became Previewable
The v0.3.2 update added dry-run previews and actionable hints, so agents can inspect an HTTP request shape before it touches the network.
Agent-First HTTP v0.3: One Request, One JSON Line
The early Agent-First HTTP release line: a structured HTTP client for agents that turns requests, streaming bodies, and transport failures into stable JSON events.