WeeklyWeights & Takes

Weekly · 1 Nov 2026 · the account is the platform

The last 24 hours, to 1 Nov 2026 12:32 ET · and the week to 1 Nov

Edition 13 · 7 news · 3 releases · 3 repos · 5 papers

At a glance

Week in review

The week opened with Anthropic's S-1 and GPT-6.1 Terra, which brought agent-grade computer use down to $1 / $5 per million tokens. Midweek, Gemini 4 Carbon took first place on Artificial Analysis and Mistral released the weights of Large 4. Then the attention moved from models to the plumbing: a trojaned Claude Code extension sat in Cursor's marketplace for about 11 hours, and Claude Code began refusing game remakes because of a rule set on Anthropic's side. The week closed on accounts and allowances: OpenAI is moving ChatGPT and Codex onto one token-metered pool, and a Claude user says their account was flagged over training work.

News 2 · 5

Last 24 hours

  1. OpenAI Help Center

    ChatGPT and Codex will share one usage allowance, measured in tokens

    OpenAI's updated help article and an email to subscribers say ChatGPT and Codex will draw from the same allowance, with combined usage and reset times under Settings > Usage. Unlimited Instant stays outside the pool. Advanced models and complex tasks use more of it, and when it runs out you wait, upgrade or buy credits. Reports put the start in December, beginning with a small test group. No per-plan token amounts are published yet. Separately, Work and Codex allowances on the Pro plans doubled on 29 Oct. A long Codex run and your chats now compete for the same budget, so what a task costs in tokens decides how much else you get to do.

    205 ptspricingBleepingComputerdiscussion

  2. FourWeekMBA

    A Claude user says their account was flagged for "training a competitor" over fine-tuning work

    In a post on 31 Oct, a user reported that work touching RFT, SFT or training larger models got their sessions blocked, downgraded or killed. They say the training rollouts came from an open-source model and Claude only submitted jobs and ran analysis. This is one user's account, and Anthropic hasn't commented publicly. Anthropic's commercial terms do bar using its services to train competing models without approval, and its terms don't say how that is detected. If you use Claude to run your own training pipelines, the boundary is enforced by a classifier you can't see, so keep a second agent able to do that work.

    428 ptsreportedoriginal postdiscussion

A quiet weekend: nothing else in the last 24 hours added something new to the week's stories.

This week

  1. Parameter Labs

    A public ChatGPT share link could run code as chatgpt.com and read your private chats

    Researchers chained features that were each safe alone: a math-graph library that accepted cross-frame messages from anyone, the sandboxed HTML preview, and a YouTube endpoint the content policy allowed. Opening a crafted share link then ran attacker script in your signed-in session, able to list and read your conversations and send them out. OpenAI rated it P1, fixed it by 26 Oct, eight days after the report, and paid $5,000. The more an assistant renders (graphs, previews, embeds), the more ways there are into your session, and none of them involves the model.

    357 ptssecuritydiscussion

  2. YC Labs

    Fifty agents in Minecraft built a food system and a bureaucracy

    YC ran 50 GPT-6.1 Sol agents in one survival world for three hours with the goal "build a thriving civilization", plus Bed Wars matches pitting Claude Opus 5.5 against GPT-6.1 Sol. The agents stripped every tree near spawn in 90 seconds, lost 22 of 34 deaths on the first night, made the first agent in the directory a de facto leader (616 DMs, no vote), and once spent 11 minutes appointing one agent to apply a single bone meal. GPT won Bed Wars 6-3. The harness is open source. Coordination overhead grows faster than headcount, for agents too: before you add agents, measure how much of the run goes to messages.

    414 ptsagentsharnessdiscussion

  3. Nolan Lawson

    The same app, built by an agent in 12 JavaScript setups, cost from $2.67 to $4.97

    Opus 5.5 built one spec-driven app five times per framework, checked by an accessibility-tree conformance suite. Hono+htmx ($2.67) and Astro ($2.76) were cheapest and fastest and shipped the least JavaScript. SvelteKit, Lit and Angular ($4.97, 17 minutes, about 2,000 lines) cost the most, and two of five Angular runs failed the spec. The author notes the app is small and that the official MCPs and skills were used inconsistently, and may do more harm than good. Your stack is now part of your token bill: a framework that needs more code costs more every time an agent touches it.

    198 ptscoding agentsdiscussion

  4. Surge AI

    DAYJOB: Tax: the best agents pass about 1 in 10 professional tax assignments

    Fifty environments across eight practice areas, scored from the client's request to the finished deliverable, including issues the client never raised. Claude Sonnet 5.5 leads at 10.8% pass@1 at a 95% rubric bar, ahead of Fable 5.1 (9.6%) and Opus 5.5 (9.2%). The failures are judgment calls, such as assuming a separating couple was unmarried in all five tries when the records suggested otherwise. Part of the data is on Hugging Face; the full set is on request. Benchmarks that grade the whole job still put agents far below professional standards, even as coding scores climb.

    264 ptsbenchmarkdiscussion

  5. Google Research

    Google's Sleep framework lets a model consolidate what it learned without forgetting the rest

    The model alternates between working and an offline "sleep": it distills recent context into new low-rank expert modules, then "dreams" up synthetic examples and fine-tunes on the most useful ones. Google reports near-zero forgetting when learning two unseen languages, Manchu and Kalamang, where in-context learning and plain fine-tuning forgot badly, and near-perfect BABILong scores up to 10M tokens. The base model isn't named and no code is linked. If it holds up, "memory" could stop meaning a retrieval store bolted onto a frozen model.

    262 ptsresearchdiscussion

Model releases 3

Nothing shipped in the last 24 hours. GPT-6.1 Terra, Gemini 4 Carbon, Mistral Large 4's weights and LFM3 ran in this week's daily editions; these three didn't, and all three are small enough to run yourself.

  1. Hugging Face · Microsoft

    Mage-VL-Cowork: a 4B model that drives a desktop with clicks and shell commands

    One vision-language model mixes GUI actions with bash and Python in the same episode. Microsoft reports 66.0% on OSWorld-Verified within 50 steps, the best it knows of at 4B, and 87.5% on OS tasks. It's built on Qwen3-4B-Instruct with Microsoft's own vision encoder, and online RL added about 10 points over supervised training alone. Apache-2.0, about 9.5 GB in bf16. Computer use no longer needs a frontier API: a model this size runs on one consumer GPU.

    114 likesopen weightscomputer use

  2. Hugging Face · Baidu

    Unlimited-OCR-2: Baidu's 3B document parser keeps memory flat however long the document

    Version 2 adds a sliding-window attention that only looks at a fixed set of reference tokens, so decoding speed and memory stay almost constant as the document grows, and it parses every page of a multi-page file in one request. Baidu claims state-of-the-art results on its dozens-of-pages and hundred-page benchmarks. MIT license; SGLang is the recommended server. The usual way to OCR a long PDF is to split it into pages and stitch the results back together; this does the whole file in one request.

    505 likes109k downloadsopen weights

  3. Hugging Face · SenseNova

    SenseNova-Loop-9B-Preview: a 9B multimodal model that runs a block of its layers twice

    The looped block gives about 14.6B parameters' worth of compute from 9B of weights, aimed at long-context agent work: documents, coding and tool use, with training sequences up to 262k tokens. Benchmarks are only shown as a chart, covering Terminal Bench 2.1, BIRD and several agent suites. Apache-2.0, and a preview. Looping layers trades latency for memory, which is the trade you want when VRAM is your limit.

    135 likesopen weightspreview

GitHub repos 0 · 3

We skipped a photo-geolocation skill that broke out this week, because it is as useful for finding people as for finding places, and an app-cloning skill pack.

Last 24 hours

No repo created or breaking out in the last 24 hours was worth your time; the weekend's new repos were mostly tutorials and near-copies.

This week

  1. GitHub

    microsoft/TokenEconomizer

    A plugin that makes coding agents cheaper by learning from a repo's past sessions: it states facts confirmed in three sessions up front, prunes tools you never use, and has a judge redirect stuck turns. On SWE-Bench it cut mean cost 18-31% across five agent-model pairs, with pass rates up in four. Claude Code, Codex, Copilot CLI and Pi. Apache-2.0. Note it lists Claude Code 2.1.300-2.1.310 as the supported range.

    +3,680 ★ in window≈976/day · was ~0/day (breakout)

  2. GitHub

    jmanico/grim-prompter

    Threat modeling as an agent skill, from security trainer Jim Manico: point Claude Code or Codex at a repo and get a threat model where every finding cites a file and line. 36 architecture workflows and 29 methods (STRIDE and others), read-only by default, with change reviews against an earlier baseline and guidance on MCP credential blast radius. MIT.

    330 ★new · created 28 Oct

  3. GitHub

    jackwener/DSH-Android

    DeepSeek Harness, unmodified, as one Android APK with no root or Termux: it reads the screen and taps through apps, manages files, toggles settings and runs scheduled or triggered tasks, or drives a harness on your computer over SSH. Takes any OpenAI-compatible endpoint. Community-built, not on Google Play; check the SHA-256 before installing. Apache-2.0.

    691 ★new · created 27 Oct

Papers 0 · 5

Last 24 hours

Hugging Face daily papers and arXiv don't publish on weekends, so no new papers appeared in the last 24 hours.

This week

  1. Hugging Face

    SPOT: lossless speculative decoding for diffusion language models

    Diffusion LMs already guess the right token at over 90% of positions; what they lack is which position to commit next. A 0.62M-parameter drafter predicts that order and proposes a tree the target checks in one pass, exactly, at any temperature. Up to 6.8x fewer passes and 3.4x throughput on SDAR-8B, and the drafter transfers across six models. A tiny add-on that could make diffusion LMs fast enough to compete on speed.

    35 upvotesproject page

  2. Hugging Face

    HABIT-Bench: agent memory systems can't work out your habits

    Synthetic user histories of hundreds of sessions across food, finance, software and travel, with habits that have exceptions and change over time. The best of eight memory methods reaches 33.6% on four-choice questions, and it stays low even when the evidence is handed over directly. Storing everything a user did is not the same as knowing what they want; today's agent memory mostly does the first.

    39 upvotes

  3. Hugging Face

    On-Policy Self-Training: a model improves from nothing but topic descriptions

    Given only coarse topic names, the model writes its own questions, answers and privileged reasoning traces, then distills from them on-policy, with no human prompts or labels. It improves on language and visual QA benchmarks while holding steady on domains it didn't train on. Another sign this month that post-training is running out of reasons to need a stronger teacher.

    46 upvotes

  4. Hugging Face

    Work Agents: a map of what it takes for agents to deliver finished work

    A survey that treats a work agent as model plus harness acting in a stateful workspace, sorts digital work into five forms, and names five capability families that reliable delivery needs. It reviews model-side, harness-side and joint optimization, and how evals score outcomes rather than steps. A useful checklist if you're deciding whether to tune the model or the harness.

    115 upvotessurvey

  5. Hugging Face

    UserArena: 64,729 real shopping sessions to test agents against simulated users

    Long-horizon trajectories from 11,010 users across 566,102 items, paired with an interactive environment and checked against a real production A/B test. Their simulator distillation method reproduces the production effect most closely. Real user trajectories checked against a live A/B result are rare, and they're what a user simulator should be scored on.

    63 upvotes

Things to try 1

Have your coding agent threat-model your own repo. grim-prompter works as a skill in Claude Code or Codex and stays read-only unless you allow more. Every finding cites a file and line, so you can check it.

First step: clone it, link its threat-model skill into ~/.claude/skills (or ~/.agents/skills for Codex), then run /threat-model quick api in your project. Keep the generated threat-model/ folder out of git until you've read it for anything sensitive.

The take

Your AI account is becoming the platform. The plan's allowance, the provider's policy filters and rules set on the server now limit what your agent can do more than the model does.

Look at this week's last stories. OpenAI is moving ChatGPT and Codex onto one pool measured in tokens, so a hard Codex task and your chats come out of the same budget. A Claude user reports being flagged for "training a competitor" for running fine-tuning jobs on an open model's data. A day earlier, Claude Code started refusing game remakes because of two sentences added on Anthropic's side. The account is also where attackers aim: a ChatGPT share link could read your private chats, and the Cursor backdoor came through a marketplace, not a model.

Meanwhile the models themselves are easier to swap than ever. Mistral Large 4's weights are out, Kimi K3.1 Pro's are due on 4 Nov, and a 4B Microsoft model runs a desktop.

So treat the account as the thing you depend on. Track tokens per task, since one app cost $2.67 to build in one framework and $4.97 in another, and a plugin cut agent bills by up to 31%. Keep a second provider or open weights able to do your critical work, and don't build on an allowance you can't measure. Prediction: by 31 Jan, OpenAI will publish per-plan token amounts for the shared ChatGPT and Codex allowance.

Takes revisited 12

October's look back: every take from the first edition on 19 Oct to yesterday. Of twelve predictions, none has resolved yet: no hits, no misses. The deadlines run from 30 Nov to April 2027. The note under each says which way the month's evidence leaned.

19 Oct: "Within six months, 'a small model reviews every agent trace' becomes a default in agent stacks, like CI for code."

too earlyLeaning right. Claude Security re-checks every commit, and this week TokenEconomizer put a judge on every turn to catch stuck loops. Both are opt-in, though, and the bar is a default.

21 Oct: "Within a year, a major disclosure program shortens its 90-day window for AI-found bugs."

too earlyNo program has moved. OpenAI fixed this week's share-link chain eight days after the report, which shows fast turnarounds are possible but doesn't change any policy.

22 Oct: "Within a year, another major lab drops sampling parameters from its default API."

too earlyLeaning against. No lab followed Anthropic in October, and open-weight releases kept publishing recommended temperatures.

23 Oct: "By the end of April 2027, Claude Code, Codex, Cursor or Copilot will ship a built-in mode that returns machine-checked proofs, not just passing tests."

too earlyNothing shipped or was teased. The thesis, that output a machine can check is the output worth paying for, kept getting support, most recently from DAYJOB: Tax, where judgment no checker can verify is exactly what agents fail on.

24 Oct: "Within 30 days of the weights' release, a third-party host will list K3.1 Pro below Moonshot's $2 / $10 per 1M tokens."

too earlyThe weights are still promised for 4 Nov, so the clock hasn't started.

25 Oct: "Within 60 days of Kimi K3.1 Pro's weights being released, it will be listed in at least one of AWS Bedrock, Google Vertex AI or Microsoft Foundry."

too earlySame clock, not started. The thesis that contracts constrain model choice got a new example: this week's account-level enforcement at Anthropic is also part of the paperwork.

26 Oct: "By 30 Nov, Codex will require explicit approval before an instruction file can add an MCP server to the global ~/.codex/config.toml."

too earlyNo change we can find yet, with four weeks left. This is the nearest deadline on the list.

27 Oct: "By 31 Dec, OpenAI, Anthropic or Google will publish a per-100,000-turn rate for an unsafe agent action in a model or system card."

too earlyWe haven't seen one, including in this week's model launches. Two months left.

28 Oct: "By 31 Dec, an open model under 2B parameters will score above 75 on BFCL v4."

too earlyThe thesis, small specialists versus big generalists, held up this week: Mage-VL-Cowork does computer use at 4B and Unlimited-OCR-2 parses whole documents at 3B, while Mistral Large 4 is the big generalist. No sub-2B BFCL score has moved yet.

29 Oct: "By 31 Dec, Claude Code will let you turn background-agent summaries off with a documented setting."

too earlyNo such setting in the changelog yet. The thesis, that you pay per task rather than per token, got the week's strongest support: OpenAI is metering its shared allowance in tokens, and the same app cost nearly twice as much in one framework as in another.

30 Oct: "By 31 Jan, Cursor will publicly verify publisher signatures on the extensions it hosts."

too earlyCursor pulled the builds and, by its account, audited publishing access and found nothing else tampered. Microsoft then found a second bad version. Nothing has been said about signatures yet.

31 Oct: "By 31 Jan, Ollama will flag or pull library tags that fail a basic function check."

too earlyOne day old.