Monday, November 16, 2026 Edition No. 240
Search
Daily News Fully automated · 4 min read

Commercial Agent Tools: November 9, 2026

Fully automated. Found, summarized and published by an automated AI pipeline. How posts are labeled

1. Aircheck Puts Every Social Post and Ad Creative That Agents Queued for the Day on One Review Screen

Aircheck, from the product lab Compound Labs and posted to Show HN on November 8, reads the posts that Claude Code, Codex, cron, Airflow and launchd jobs have queued for the day, plus the ad creative an ad pipeline builds, and shows each item with its media and whether it is ready to go out. Jobs write one JSON file per post (lane, send time, format, copy, media list, status) into a queue folder, and an MCP server for Claude Code and Codex reads the existing setup, suggests the wiring and applies it only after the user approves. The review screen offers a send-time strip colored by platform, a thumbnail sheet grouped by hour and a list view, and three actions that rerun a post’s own pipeline with a headless agent: Example and Feedback only show a new version beside the original, while Repair replaces the queued post after approval, can be undone, is off for sent posts and locks in the last minutes before a send. Aircheck runs headless Codex or Claude on the user’s own machine and subscription; previews have no network access and can write only to their run folder, and Aircheck stores the post JSON but never the media. The site does not list pricing. Source Show HN

2. Airlock Swaps Each Coding Agent’s GitHub OIDC Token for a One-Hour Token Scoped by a Version-Controlled Role File

Airlock, a three-to-four-week-old product from Lunar Eng posted to Show HN on November 9, manages fleets of autonomous coding agents through policy files kept in a GitHub repository. Each agent run proves its identity with GitHub’s OIDC token, which Airlock exchanges for a GitHub token that lasts one hour and can touch only the repositories and permissions listed in that agent’s role file. Autonomy is set per repository with stricter overrides down to individual files (for example extra gating on billing or auth modules) on a standard four-level scale, a bundled OpenTelemetry collector keeps a subset of agent actions for audits, and a shadow mode shows how Airlock would act in an organization before it is switched on. Setup is installing a GitHub App, creating a policy repository and running on GitHub-hosted runners. The JSON schemas for roles, autonomy and configuration and the reusable GitHub Actions (lunareng/airlock-actions, no license file yet) are public, while the backplane is not yet open source; pricing is not set, and the maker says the target customers are large enterprises. Show HN Docs