Ever tried to automate a real website and ended up babysitting Playwright selectors, browser-use agents, or computer-use agents?
Watch me use Rindler to set up my plans for the world cup โฝ๏ธ๐
https://t.co/Ut39U6aVTm
We kept running into the same problem: the browser automation would work for a bit, then drift, break, or get lost.
So, we built Rindler to map websites into actions agents can use more reliably.
Today we're launching Inkbox: the identity and communication layer for AI agents. We give agents their own email, phone, iMessage, and an internet address. Install @inkbox_ai identity with one command: allow anyone to reach your Claude Code, Codex, or Hermes from anywhere, and let it reach anyone.
We heard you. And we agree.
In light of recent developments in physical media, GitHub is proud to announce that you can now obtain your public repo on CD-ROM.
Keep it. Lend it to friends. Pass it on to your children.
Your code is physically yours, forever. Until you lose it, let's be real.
Order yours today.
https://t.co/z041pdMH7h
Some takeaways:
1. Background agents no longer stop to ask permission when they finish they commit, push, and open a draft PR on their own. There are also new hooks that notify you when an agent needs input or completes. You can genuinely start a task and leave.
2. Subagents got better too. The Explore agent used to run on haiku regardless of what you were paying for, but now it inherits your session's model.
3. aaand the /agents wizard is gone. You just tell Claude to create or manage subagents, or edit .claude/agents/ yourself.
Claude Code 2.1.198 has been released.
32 CLI changes
Highlights:
โข Claude in Chrome is generally available, offering direct browser access to sessions and agents with no install
โข Background agents auto-commit, push, and open draft PRs in worktree after finishing code, automating delivery
โข Docs now advise grep for searches and clarify head_limit/unlimited/offset semantics to reduce surprises
Complete details in thread โ
how to maximize your fable 5 usage:
1. spend it on the one-way doors. data model, API contracts, the core abstraction - the calls that are expensive to reverse once your week ends
2. put GPT-5.5 in front as a context compressor. It reads the whole repo and hands Fable only the distilled data. Input tokens are precious
3. let fable do your planning. Fable writes the architecture/PRD. you can use the codex plugin inside cc to implement (https://t.co/zBIfEpYZWD)
4. have Fable write the artifacts that govern your cheap fleet - eval suites, grading rubrics, the system prompts GPT-5.5 runs against all week. One frontier session shapes thousands of downstream calls, so the cost amortizes to near zero per use.
REMEMBER: you need to reduce your opus 4.8 usage as well
Claude Fable 5 will be available again globally tomorrow.
After a series of productive conversations with the US government, we're redeploying the model with a new set of classifiers to target and block more cybersecurity tasks. In the near term, some routine tasks like coding and debugging will fall back to Opus 4.8. Weโll continue to refine these classifiers over the coming weeks to reduce false positives and better distinguish genuine misuse from legitimate requests.
Weโve also begun drafting a consensus frameworkโwith Amazon, Microsoft, Google, and other Glasswing partnersโfor assessing the severity of AI jailbreaks and how AI developers should respond to them. We invite other industry partners and model providers to join us in this effort.
Finally, weโre scaling up our collaboration with the US government on model testing and safeguards. This will include pre-release access to models and safeguards for evaluation, information sharing on jailbreaks and misuse, and dedicated resources for joint research.
Thank you to our users for your patience, and to our partners across the government, industry, and the research community who worked alongside us to make Fable 5 available again.
Read our full blog: https://t.co/VHyum831ri