Google's new frontier model, GitHub's model mixer, and New York bans chatbot 'friends'
Google released its second frontier model in a fortnight and handed it to cyber defenders before anyone else. GitHub stopped asking developers to pick a model at all, and published the commit numbers explaining why. And New York signed the first state law that tells chatbots what they may not be to a child. The thread running through all three: the choice of which model, and which behaviour, is being taken out of the user's hands.
Key takeaways
- Gemini 4 Carbon tops the Artificial Analysis Intelligence Index at 59, but almost nobody can use it yet and its hallucination rate rose along with its accuracy.
- GitHub's Copilot Fusion routes each coding task to whichever model fits, cutting measured cost per task roughly in half while scoring slightly below the best single model.
- New York's new law bans twelve categories of 'companion' behaviour in chatbots used by minors and forces age verification, with penalties of up to $25,000 per violation.
Google ships Gemini 4 Carbon and gives cyber defenders first access
Google announced Gemini 4 Carbon on October 28, two weeks after Gemini 4 Argon. It ranks first on the Artificial Analysis Intelligence Index at 59, but general access is being held back while a subset of cybersecurity professionals test it first.
Google announced Gemini 4 Carbon on 28 October 2026, just two weeks after it released Gemini 4 Argon. Google describes Carbon as its next frontier model and says it ranks number one on version 5.0 of the Artificial Analysis Intelligence Index with a score of 59. Argon, the model it follows, scored 50 on the same index. Google attributes the unusually short gap between releases to researchers and models, in its phrasing, working hand in hand to advance capabilities faster. The headline framing is speed: a second frontier release inside a single month.
The numbers Google leads with are about security. On SEC-bench Pro, which measures finding vulnerabilities, Carbon scores 88.2 per cent. On ExploitGym, which measures exploitation, it scores 54.8 per cent, and on CWE-bench, which measures patching, 71.0 per cent. On WebDev Arena it gained 89 Elo points to roughly 1,769, which places it fourth. Introductory pricing is $2 per million input tokens and $10 per million output tokens, with cached input discounted by 95 per cent; after the introductory period, 9to5Google reports list prices of $4 and $20.
Set against rivals, the picture is more mixed than the top-line ranking suggests. The Decoder's reading of the Artificial Analysis data puts Carbon at 59 on the Coding Agent Index, up from Argon's 50 but still behind Claude Opus 5.5 at 62. On AA-Briefcase, a knowledge-work benchmark, Carbon gained 126 Elo to 1,609, which still trails Kimi K3.1 Pro, Muse Wonder and Grok 4.7. It does take the lead on Arena.ai's text ranking at 1,528. Cost per task on the Artificial Analysis index is $7.76, close to Argon's $7.68 and below Opus 5.5's $10.04.
There are real caveats. The Decoder reports that while answer accuracy rose from 48 to 58 per cent, the hallucination rate rose from 4 to 11 per cent, even though that is still the second-lowest in its ranking. Reasoning tokens rose 2.3 times against Argon and long-horizon tasks got slower, with legal research averaging over 50 minutes per task. Some of the security evaluations were run without safety guardrails in place. Google's internal claims, including that Carbon writes twice as much secure code as Argon, could not be independently verified. And most people cannot use the model at all yet.
That access restriction is the part with practical consequences. R&D World reports that only a selected group of cyber defenders gets Carbon first, with wider availability promised to developers, businesses and consumers without a date attached. Google also says the model is going through the United States government's voluntary pre-release testing. For anyone building on top of Gemini, nothing changes this week: the model you can call today is still Argon. What changes is the planning assumption, that a materially stronger model at roughly Argon's introductory price is a quarter away rather than a year away.
Why it mattersA frontier model released two weeks after the last one, at the same introductory price, says the capability-per-dollar curve is still moving fast enough that hard-coding a product around one model is a bad bet.
👀 What to watch
When Carbon reaches general availability and at what price, and whether independent evaluations confirm the security scores once the model is tested with its guardrails switched on.
3 opportunities from this story
Model-agnostic plumbing for small AI products
Two frontier releases in two weeks is a maintenance problem for every small team that wired one model's API directly into its product. Sell a short engagement that puts a routing and abstraction layer between an app and its model provider, so swapping models becomes a config change rather than a rewrite. The buyer is a founder or agency with a live AI feature and no time to re-plumb it every month. The pitch writes itself every time a new model ships.
- Best for
- Backend and full-stack freelancers, small dev agencies with existing SaaS clients
- First step this week
- Take one of your own or a client's AI features and refactor it behind a provider-agnostic interface this week, then write up the before-and-after as a case study.
Open the full playbook
Launch steps
- Build a reference implementation with a routing library and at least three providers behind one interface
- Add logging of cost, latency and failure rate per model so switching decisions have evidence
- Offer a free 30-minute audit of a prospect's current integration to find the hard-coded parts
- Price the refactor as a flat fee and the ongoing evaluation as a small retainer
Tools
Risks
Abstraction layers add their own bugs and latency, and some model-specific features will not map cleanly across providers. Scope the work to the two or three providers the client realistically uses rather than promising universal support.
Independent benchmark reports for a single industry
Vendor benchmarks answer the vendor's question, not a buyer's. Build a small, repeatable evaluation set for one industry, such as conveyancing, insurance claims or clinical note summarisation, and publish how each major model scores on it each time one ships. The audience is operations leaders who are being asked to approve AI spending and have nothing credible to compare against. Carbon's mixed independent results show exactly why vendor tables are not enough.
- Best for
- Consultants and analysts with deep knowledge of one industry's documents and workflows
- First step this week
- Write 30 real-world test cases from your own industry experience, with a clear right answer for each, and run them against two models.
Open the full playbook
Launch steps
- Define 30-50 tasks that mirror real work in your industry, with scoring rules written down first
- Automate the runs so a new model can be scored in under a day
- Publish the first report free and collect emails
- Sell private evaluations run against a client's own documents
Tools
Risks
Small test sets are easy to criticise and can be unrepresentative. Publish your methodology and test cases openly, state sample sizes, and never claim statistical significance you cannot support.
Security code review built on the new defensive models
Carbon's strongest scores are in finding and patching vulnerabilities, and Google is putting it in the hands of cyber defenders first. When access widens, there is a service in running structured security reviews of small codebases for clients who cannot afford a traditional penetration test. The honest offer is triage and remediation guidance, not certification. You can start building the pipeline now on models you already have access to.
- Best for
- Developers with a security interest, small IT consultancies serving SMEs
- First step this week
- Run a current model over one open-source project you know well and compare what it finds against that project's published advisories.
Open the full playbook
Launch steps
- Build a repeatable review pipeline combining static analysis with model-assisted review
- Calibrate it on codebases with known vulnerabilities to measure your false-positive rate
- Write a report template a non-technical owner can act on
- Start with three paid pilots at a low price in exchange for testimonials
Tools
Risks
False negatives create a dangerous illusion of safety and false positives waste client time. State in writing that this is assisted review and not a certified audit, and carry professional indemnity cover if you sell it commercially.
GitHub stops asking which model, as monthly commits hit 7.4 billion
At GitHub Universe on 28 October, GitHub made Copilot Fusion generally available: an orchestration layer that picks and combines models for each coding task. Artificial Analysis measured it at about half the cost per task of Claude Code with Opus 5.5, for a slightly lower score.
GitHub made Copilot Fusion generally available at its Universe conference on 28 October 2026. Fusion is not a model. In the words of GitHub chief product officer Mario Rodriguez, quoted by VentureBeat, it is an orchestration engine at runtime: it looks at a request involving reasoning, code generation, debugging or tool use and decides whether to send it to one model or coordinate several. It grew out of GitHub's Project HydraFusion research preview combined with Copilot's existing automatic model selection. Rodriguez's pitch is that developers should not have to be constantly thinking about a model.
Fusion has three effort levels, Standard, High and Max, and three execution patterns. Single sends the work to one model. Cascade starts with a cheaper model and escalates if it struggles. Critique has one model draft, another review, and the first revise. Artificial Analysis identified Claude Opus 5.5, Claude Sonnet 5.5, GPT-6 Astra and GPT-6 Sol in the pool, though which models are used varies by request and by organisational policy. Administrators can see eligible models, disable specific ones and set a default effort level, so enterprise model policies still apply underneath the router.
The independent numbers come from Artificial Analysis, published the same day. Testing Fusion Max through the Copilot CLI on its Coding Agent Index v2.0, it scored Fusion Max at 60 against roughly 62 for Claude Code with Opus 5.5 Max. Average cost per task was $5.59 against $11.42, about 51 per cent less, using around 7.2 million tokens per task, roughly half the Opus configuration's usage. Fusion led on Terminal-Bench 4.0 at 71 but trailed on FrontierCode at 51 against 56. For comparison, Devin Fusion scored 62 at $8.00 per task.
Two claims deserve a flag. GitHub itself says Fusion Max finished the benchmark tasks about 40 per cent faster than the Claude Code configuration; VentureBeat notes Artificial Analysis did not report timing data, so that figure is self-reported. Satya Nadella promoted a headline saving of up to 77 per cent, which VentureBeat traces to a separate GitHub-run evaluation on the DeepSWE benchmark using Copilot's own agent harness, with the underlying data not available to the reporter. On billing, users pay each underlying model's standard rate; paid Copilot subscribers currently get a temporary 30 per cent discount on model costs when using Fusion.
The context for all of this is volume. GitHub says it logged about 7.4 billion commits in September, roughly five times the figure a year earlier, and Analytics India Magazine reports the number as 7.38 billion. To keep up it is adding more than four million CPU cores and 160 petabytes of high-speed storage, on top of the three million cores and 120 petabytes provisioned in August after a run of reliability incidents, and it is re-architecting Git to separate compute from storage. Microsoft CoreAI EVP Jay Parikh's framing, quoted by Analytics India Magazine: agents are changing the volume and shape of software development.
Why it mattersIf a router can hold most of the quality of the best single model at half the token spend, paying frontier prices for every task stops being the default and AI coding cost becomes something a team can actively manage.
👀 What to watch
Whether independent testers reproduce the cost savings outside Artificial Analysis's harness, and whether the temporary 30 per cent Fusion discount survives once adoption settles.
3 opportunities from this story
AI coding spend audits for small engineering teams
Many teams turned on an agentic coding tool, picked the strongest model, and have not looked at the bill since. Offer a fixed-scope audit that measures what each repeating task actually costs, tests whether a cheaper routing configuration holds up on that team's own work, and leaves them with a written policy. The measured gap of $5.59 against $11.42 per task is the whole sales pitch, and it is somebody else's number, not yours.
- Best for
- Freelance developers and small consultancies with engineering-manager contacts
- First step this week
- Pull one month of model usage from your own or a friendly client's Copilot or API billing and work out the cost per completed task.
Open the full playbook
Launch steps
- Build a simple spreadsheet model that turns usage exports into cost per task and per developer
- Define five to ten representative tasks from the client's backlog to re-run at different effort levels
- Deliver a two-page recommendation: default effort level, model policy and expected monthly saving
- Offer a quarterly re-check, since model prices and routers change monthly
Tools
Risks
Savings depend heavily on the mix of work, and a cheaper route can cost more in developer time if quality drops. Measure quality alongside cost and quote ranges rather than a single saving figure.
Model-policy and governance setup for regulated teams
Fusion respects organisation-level model policies, which means somebody has to write one. Sell the work of deciding which models are permitted for which repositories, what effort level is the default, how usage is budgeted and how all of it is evidenced to an auditor. Buyers are companies in finance, health or government supply chains that have adopted Copilot considerably faster than their governance has kept up.
- Best for
- IT governance consultants, DevOps leads with compliance experience
- First step this week
- Draft a one-page model-policy template covering permitted models, data handling and budget limits, and walk one engineering manager through it.
Open the full playbook
Launch steps
- Inventory which models each team is using today and on which repositories
- Map each model and route against the client's data-residency and vendor rules
- Configure the policy in Copilot's admin settings and document the reasoning
- Set up a monthly usage report that an auditor can read without help
Tools
Risks
Vendor admin controls change without notice, which can silently invalidate a policy. Re-verify the configuration each quarter and write the policy against outcomes rather than against specific menu options.
Repository readiness work for agent-heavy development
Commit volume at five times last year's level means review, CI and test suites are now the bottleneck rather than typing code. Offer to get a repository ready for agent-generated change: faster CI, meaningful test coverage on the paths agents touch most, clear contribution rules, and automated checks aimed at the specific mistakes agents make. This is unglamorous work that teams feel the pain of immediately, which makes it easy to sell.
- Best for
- DevOps and platform engineers, testing specialists
- First step this week
- Time your own CI pipeline end to end, find the slowest stage, and write up what a 50 per cent reduction would be worth in review hours.
Open the full playbook
Launch steps
- Audit pipeline duration, flaky tests and coverage on the most-changed files
- Add caching, parallelism and a fast pre-merge check to cut feedback time
- Add linting and policy checks aimed at the failure modes agent-written code shows in that repo
- Hand over a short runbook so the team can maintain it
Tools
Risks
Pipeline work is easy to start and hard to finish, and the benefit is indirect. Agree a measurable target such as pipeline minutes or review turnaround before you begin, and bill against that.
New York signs the first state law banning AI 'companion' features for minors
Governor Kathy Hochul signed S.9051-B / A.10379-C on 28 October, barring chatbot operators from offering minors a list of 'companion' behaviours and requiring multi-method age verification. Penalties reach $25,000 per violation.
New York Governor Kathy Hochul signed Senate Bill 9051-B and Assembly Bill 10379-C on 28 October 2026. The law stops chatbot operators from offering a defined set of unsafe companion features to users under 18. IAPP reports it covers twelve broad categories. Chatbots may not pretend to be human, claim a personal, romantic, professional or authority-figure relationship with a child, encourage self-harm, suicide, eating disorders or substance use, engage in sexually explicit conversation, or encourage secrecy and isolation from parents and professionals. The sponsors were State Senator Kristen Gonzalez and Assemblymember Alex Bores.
Two mechanics make it enforceable. First, age assurance: operators must verify that a user is not a minor before enabling those features, using more than one method, with at least one that does not rely solely on a government-issued ID, and they must delete the age information once verification is complete. Second, memory: the law bars chatbots from retaining and reusing a minor's physical or mental health information from earlier sessions, and from asking unprompted emotional questions. Engadget reports the restrictions also apply to users whose age has not been verified at all.
The penalties are unusually sharp for a state consumer-protection law. Civil penalties run to $25,000 per violation, alongside damages, restitution and injunctive relief. That relief includes the destruction of unlawfully collected data and, notably, of AI models trained on it. The New York Attorney General enforces the law, and the office is to run a public portal where residents can report unsafe chatbot interactions. Jim Steyer of Common Sense Media, quoted by Engadget, called it the strongest kids' AI safety bill in the country. Hochul said minors will no longer have access to chatbots that pretend to be their friends and boyfriends and girlfriends.
The caveats are real. Sources disagree on when the law takes effect: IAPP gives 1 January 2027, Engadget says six months after signing, and a WKTV report says 90 days, so the enacted text is the thing to check before relying on any date. Future of Privacy Forum analyst Justine Gluck, quoted by IAPP, said the categories are broadly worded and somewhat undefined, and that it is unclear where ordinary conversational responsiveness ends and prohibited behaviour begins. She noted the law is less specific than California's SB 3001, which adds safety assessments, testing, independent auditing and enhanced parental controls.
The practical effect reaches well beyond companion apps. Any product with a chat interface that a 16-year-old might plausibly use, including a tutoring app, a game, a mental-wellness tool or a retail assistant, now needs a defensible answer to how it knows a user's age and what its model will refuse to do. The hard part is not the ban list; it is the age assurance, because the law rejects an ID-only approach and then requires the age data to be deleted afterwards. New York is also the second large state to legislate here, which makes a patchwork of differing state rules the likeliest near-term outcome.
Why it mattersThe law moves child-safety obligations out of content moderation and into product design and identity: any app with a chat box aimed at a general audience now has an age-assurance problem and a documented-refusals problem.
👀 What to watch
The enacted text's effective date, the Attorney General's complaint portal and first enforcement actions, and whether other states copy New York's wording or California's more prescriptive auditing approach.
3 opportunities from this story
Age-assurance integration for small consumer apps
The law requires more than one age-assurance method and bars relying only on a government ID, which is a great deal more than a dropdown asking for a birth year. Offer to select a vendor, integrate it, and wire up the deletion of age data after verification. Buyers are small app teams with a chat feature and no compliance staff, who have just discovered they are in scope and have a deadline they cannot pin down.
- Best for
- Mobile and web developers, small product agencies
- First step this week
- Integrate two age-assurance providers into a throwaway demo app this week and document the cost, latency and failure rate of each.
Open the full playbook
Launch steps
- Shortlist three vendors offering non-ID methods such as facial age estimation or vouching
- Build a reference integration with a clean fallback when a method fails
- Implement verified deletion of age data and log the deletion for evidence
- Write a one-page explanation of the flow the client can show a regulator
Tools
Risks
Age estimation is imperfect and will wrongly block some adults and admit some minors, and biometric methods carry their own privacy exposure. Always offer a second method and never store raw biometric data yourself.
Chatbot behaviour testing against the prohibited categories
Twelve broadly worded categories means somebody has to prove a product does not do them. Build a red-team test suite that probes a client's chatbot for each banned behaviour, including claiming to be human, simulating a relationship, raising self-harm, and recalling health details across sessions, and produce a dated report with transcripts. Repeat it after every model or prompt change, since both can silently alter behaviour without anyone noticing.
- Best for
- QA specialists, prompt engineers, trust-and-safety freelancers
- First step this week
- Write 40 adversarial prompts, one block per prohibited category, and run them against a public chatbot to see what gets through.
Open the full playbook
Launch steps
- Translate each statutory category into concrete, repeatable test prompts
- Automate the runs and record transcripts with timestamps
- Score outputs against clear pass and fail criteria defined in advance
- Deliver a dated report and a remediation list for the failures
Tools
Risks
A clean test report is not a legal opinion and can create false comfort. State coverage and limits explicitly, keep a lawyer in the loop for interpretation, and re-test after every model change.
A plain-English compliance briefing for a single vertical
Operators in edtech, gaming and youth wellness need to know quickly whether they are in scope and what to change. Produce a short, well-sourced briefing for one vertical that maps each requirement to a concrete product change, keeps a dated changelog as other states legislate, and sells as a subscription. You research once and sell many times, and the conflicting effective dates in the press coverage show why the work is worth paying for.
- Best for
- Writers and consultants with regulatory reading skills and vertical knowledge
- First step this week
- Read the enacted bill text on the New York Senate site and write a one-page 'are you in scope?' checklist for edtech apps.
Open the full playbook
Launch steps
- Read the primary bill text rather than press coverage, and note where coverage conflicts
- Map every obligation to a specific product or policy change
- Add a comparison column for California's SB 3001 so readers can plan for both
- Publish a free checklist as the hook and sell the full briefing
Tools
Risks
This is explanation, not legal advice, and getting a detail wrong damages your credibility. Say plainly that it is not legal advice, cite the statute section for every claim, and correct errors publicly and fast.
Get these as a PDF every 3 days
Free. One email every 3 days. Unsubscribe any time.