Open Source Factory

Gemini 4 Carbon: 59 Points and a $2/$10 Intro Price Open Source Factory · October 29, 2026 · Launch analysis and original cost calculations Watch the English motion graphic English conceptual motion graphic; not a Carbon recording or hands-on test. Animation, newly composed original music and sound design: Open Source Factory. Facts: Google and Artificial Analysis, linked below. The line I keep coming back to in Google's Carbon announcement is the pricing footnote: the introductory rates will eventually double. A model can look attractive on launch day and produce a very different budget later. That matters especially when the pitch is work that keeps running for hours or days. Google announced Gemini 4 Carbon on October 28, 2026 . Access begins with selected cyber defenders; a general consumer release date is not given. It also tops an independent intelligence index. Those are useful facts, but they answer different questions: capability, availability and the cost of actually fin...

POLICY & RESEARCH 1Password for Agents: Signing In Is Only the First Step Open Source Factory · Oct 23, 2026 · 7 min read Watch the English motion graphic The Secret Stays Behind. Original English motion graphics, music and sound design: Open Source Factory. Based on 1Password documentation; conceptual animation, not a product test. Rollout checked October 23, 2026. An agent needs to sign in before it can do useful work inside an account. Handing over the password creates an obvious problem; keeping the password hidden addresses only part of it. 1Password's proposal deserves a look at both the sign-in request and the access that remains afterward. In this article How can an agent sign in without seeing the password? Which agents can actually use it? Is it included in my current 1Password plan? What changes after the login succeeds? What would I check before connecting an account? Inspect access after sign-in That is what caught my eye in 1Password for Agents , announced on O...

POLICY & RESEARCH Gemini 4 Argon: A Long Output Needs a Budget Open Source Factory · Sep 30, 2026 · 5 min read A million-token output ceiling lets a generation continue for a long time. It does not tell you how much of the result will be usable. Argon's launch deserves a budget for accepted work, alongside the separate questions of API rates and initial access. In this article Output length and the context budget The coding rows Argon does not lead The initial access program Pricing a long run Availability at launch Image: Google. Official launch artwork; the following charts are our own redraws. Output length and the context budget Google raises its advertised output ceiling from 64K to 1M tokens. That describes how far a generation can run; it is separate from the input context window. Official output-limit announcement . I find the distinction more interesting than another giant-context headline. Reading a large repository and sustaining a long attempt to modify it sol...

POLICY & RESEARCH The Reported 53-Image Incident: What Users Can Check Open Source Factory · Sep 27, 2026 · 11 min read OpenAI's report leaves an uncomfortable gap: it describes 53 user images posted externally but says the affected users cannot be identified. Checking future training settings is actionable. It cannot answer whether an earlier upload was involved, so the incident and the available controls need separate explanations. In this article The reported incident What the count covers The path to an external image host Why individual notification is unavailable Limits on checking an individual image Data controls for future conversations Other incidents in the investigation The practical takeaway first, since it is the part you can act on: if you use ChatGPT on a personal account, check your training setting — one toggle, and I walk you to it below. The harder part is what you cannot do. There is no way to find out whether one of your images was among the 53, because...

POLICY & RESEARCH Pace the Frontier: Endorsements Are Not an Agreement Open Source Factory · Sep 13, 2026 · 9 min read Several rival AI leaders supported slowing capability growth during the same weekend. That is a notable set of statements. A shared timetable, independent evaluation and documented release decisions would be different evidence: signs that the proposal changed what the labs actually do. In this article The statements and their status The pacing proposal The incident reports behind the debate The reported hundred-hour activity Work continuing during the discussion The line that made me stop was about distance, not philosophy: “Given the accelerating rate of AI capability development, it's my worry that in 6–12 months such a swarm could be capable of taking over the entire internet with a persistent botnet (potentially causing hundreds of billions of dollars in damage).” That's 6–12 months, written by the person whose company is closest to the frontier al...