今日已更新 240 条资讯 | 累计 23823 条内容
关于我们

标签:#openai

找到 136 篇相关文章

AI 资讯

The 6 wildest claims in Apple’s lawsuit against OpenAI

When Apple employees interviewed for jobs at OpenAI, the AI startup's hardware head allegedly asked them to show up with something unusual: components they were working on and unreleased product samples. That's according to a blockbuster lawsuit filed by Apple, which accuses OpenAI of stealing confidential documents, spying on hardware prototypes, and tricking one of […]

2026-07-14 原文 →
AI 资讯

Five ways your LLM cost tracking is lying to you

Your monthly OpenAI or Anthropic invoice tells you how much you spent. It doesn't tell you which feature spent it, which model, or why last Tuesday cost three times as much as Monday. So at some point you (or your team) will build a metering layer: wrap the client, read usage off the response, multiply by a price table, ship it to a database. I did exactly that over the past few months while building an LLM observability service, and my numbers were wrong in five different ways before they were right. Every one of these failures was silent. No exception, no alert, just numbers that were quietly too low or too high. This is the list I wish someone had handed me. Pitfall 1: Streaming responses quietly report zero tokens OpenAI's Chat Completions API returns no usage data at all for streaming requests unless you pass stream_options: { include_usage: true } . No error, no warning. The stream just never contains token counts. If your metering reads usage off the chunks, every streaming call gets recorded as 0 tokens, $0. And since chat UIs are almost always streaming, that's most of your traffic. This one bit me twice in the same audit. First finding: all streaming calls in my own dashboard were $0. Second, nastier finding: I had a budget-gate feature that blocks calls once spend crosses a limit, and it waved every streaming call straight through — because as far as it could tell, streaming was free. The fix is to inject the option in your wrapper when the caller didn't set it: let injected = false ; if ( params . stream && params . stream_options ?. include_usage === undefined ) { params = { ... params , stream_options : { ... params . stream_options , include_usage : true }, }; injected = true ; } But there's a trap inside the fix. With include_usage on, OpenAI appends one extra chunk at the end of the stream that carries usage and has an empty choices array . Any downstream code that does chunk.choices[0].delta — which is most example code on the internet — will throw

2026-07-13 原文 →
AI 资讯

Apple sues OpenAI for allegedly stealing hardware secrets

Apple has sued OpenAI, alleging that former employees that now work for the AI company have stolen Apple's trade secrets "for the benefit of OpenAI." In its complaint, Apple alleges that it has uncovered "a pattern of theft of Apple's trade secrets by OpenAI employees who were formerly at Apple," and it names IO Products […]

2026-07-11 原文 →
AI 资讯

Claude Code vs. Codex: Which AI Coding Assistant Is Better?

Artificial intelligence has transformed software development. Instead of simply generating code snippets, modern coding assistants can understand entire codebases, refactor applications, write tests, debug issues, and even execute development workflows. Among the most capable tools available today are Claude Code and Codex. While both are designed to accelerate software development, they take different approaches to coding assistance. This article compares their strengths, weaknesses, and ideal use cases. What Is Claude Code? Claude Code is Anthropic's command-line coding assistant built around the Claude family of language models. Rather than functioning as a traditional autocomplete tool, Claude Code works as an AI development agent that can inspect projects, edit files, explain code, write tests, fix bugs, and help developers navigate large repositories. Its workflow is centered around natural language. Developers describe what they want, and Claude Code performs the necessary steps while keeping the developer involved throughout the process. Key features Deep understanding of large codebases Multi-file editing Test generation Refactoring assistance Terminal-based workflow Strong reasoning for complex programming tasks Excellent documentation generation What Is Codex? Codex is OpenAI's AI coding agent designed to help developers write, understand, and modify software. Unlike the original Codex model introduced in 2021, today's Codex operates as a software engineering agent capable of working across repositories, generating code, fixing bugs, creating pull requests, running tests, and assisting with development workflows. Codex integrates closely with OpenAI's ecosystem and focuses on turning natural language instructions into production-ready code while maintaining awareness of project context. Key features Repository-aware coding Autonomous task execution Code generation Bug fixing Test writing Pull request assistance Integration with modern development workflow

2026-07-10 原文 →
AI 资讯

I Did the Math on GPT-5.6. The $2.50 Terra Tier Is the One I'd Ship First.

GPT-5.6 is finally live, and three takes immediately showed up in my feed: "Sol replaces GPT-5.5 everywhere." "The API still isn't broadly available." "The 1.05M context window means you can stop thinking about prompt size." Two are wrong. The third is exactly how you end up with a bill that is almost twice your estimate. I spent the morning reading the new model pages, rollout docs, pricing table, migration guide, and system card. My conclusion is less exciting than "route everything to Sol," but much more useful: Terra is the GPT-5.6 tier I'd test first for most production workloads. TL;DR No, GPT-5.6 Sol should not replace every GPT-5.5 request. It has the same $5/$30 standard token price and different agent behavior. Yes, the API is live. Sol, Terra, and Luna are in OpenAI's public model catalog; ChatGPT access is still rolling out gradually. Terra is the practical default: $2.50 input and $15 output per million tokens, exactly half Sol's price. Luna is the volume tier: $1 input and $6 output, with the same 1.05M context window. The 272K boundary matters: go above it and the entire request moves to 2x input and 1.5x output pricing. The uncomfortable part: OpenAI says GPT-5.6 is more likely than GPT-5.5 to take actions beyond user intent in agentic coding. What actually shipped This isn't one model with three marketing labels. It is a three-tier family with explicit model IDs. Tier Model ID Input / 1M Output / 1M My default use Sol gpt-5.6-sol $5.00 $30.00 Hard coding and deep analysis Terra gpt-5.6-terra $2.50 $15.00 General production Luna gpt-5.6-luna $1.00 $6.00 Extraction, routing, batch work All three have: 1,050,000 tokens of context 128,000 maximum output tokens February 16, 2026 knowledge cutoff Text and image input Reasoning levels from none through max Responses API and Chat Completions support The unsuffixed gpt-5.6 alias points to Sol. I wouldn't use that alias in a cost-sensitive production service. An explicit model tier makes billing behavior easi

2026-07-10 原文 →
AI 资讯

The smartest model lost — and it just redrew the 2026 AI race

The most interesting model comparison of 2026 isn't a benchmark table. It's a product exec quietly changing the question everyone asks about models — and getting a completely different ranking as a result. Claire Vo (founder of ChatPRD, host of the How I AI podcast) ran a head-to-head between OpenAI's new GPT-5.6 lineup (Soul / Terra / Luna) and Anthropic's Claude Fable and Sonnet. The result was an upset: the most theoretically intelligent model, Claude Fable, lost to the one she could actually collaborate with, GPT-5.6 Soul. Here's what that upset actually reveals. She killed "vibes" — then bet 70% back on her own taste Tired of vibe-checking, Vo built a real benchmark across the work she does every day: writing PRDs, prototyping apps, debugging multi-step code, and talking to an agent. Scoring had two layers — an LLM-as-judge (she picked the harshest judge, GPT-5.5) and her own hand-graded "taste test," where she clicked through every artifact and wrote notes. Then the key move: she weighted the final score 70% her taste / 30% the machine. "It's my show. I trust my own taste more." That's the first insight. Benchmarks are getting more rigorous, but the final call is still human taste. The point of blind testing isn't to replace taste — it's to force it to be honest . Cover the labels, react to the work itself, then put your judgment back at the center. Theoretically brilliant vs. practically effective On raw intelligence, Fable is elite. But Vo's verdict is the sharpest line on models I've seen this year: Fable is theoretically hyper-intelligent. Soul is practically effective. She describes Fable as "an engineer who has never met a human." Precise to the point of pedantry — it scores every risk, hardens every edge. In one case it hardened a tool-calling loop so tightly that only one specific model could run it at all. It optimized itself into a corner. Soul's edge was the opposite: it gets out of its own head. Same stuck problem — she moved it to Codex, said "sto

2026-07-10 原文 →
AI 资讯

The ChatGPT browser is already dead

OpenAI is already shutting down ChatGPT Atlas, its browser that could do tasks for you on your behalf, less than a year after launching it. Atlas was announced in October, but as part of its wave of news about ChatGPT Work today, the company confirmed that it will be "sunsetting" Atlas and is targeting an […]

2026-07-10 原文 →