@ch402 "This autocomplete AI can even write stories about helpful AI assistants. And according to our theory, that’s “Claude”—a character in an AI-generated story about an AI helping a human."
would claude say it is living in a simulation?
taken longer than expected, but latest version of computer use is finally there
still a bit slow, but works great and can be relied on in background async to take on complicated tasks with reliably strong results
anthropic has done it again
Imo, this is a legitimate attack vector and the right decision
It's still perfectly possible to model switch on a task by loading the message history into the initial message to a separate model instead of constructing a turn-based back and forth that gets passed in
As safety work continues maybe the models will be more resilient to these types of attacks and this capability can be returned
are we misunderstanding this?
the implication is you can't insert any content that anthropic didn't know to have generated
this breaks things like switching models mid session and a dozen other things harnesses rely on
i switch between claude and gpt all the time :(
tools creation evals are more interesting than tool use evals
as agents take on longer running tasks the ability to self reflect and create effective scaffolding is powerful
just can't be bullish enough on ramp - such a great product and culture, so many companies falling behind on eng but they continue to get it and stay on bleeding edge despite reaching larger scale
yes things are changing fast, but also I see companies (even faang) way behind the frontier for no reason.
you are guaranteed to lose if you fall behind.
the no unforced-errors ai leader playbook:
For your team:
- use coding agents. give all engineers their pick of harnesses, models, background agents: Claude code, Cursor, Devin, with closed/open models. Hearing Meta engineers are forced to use Llama 4. Opus 4.5 is the baseline now.
- give your agents tools to ALL dev tooling: Linear, GitHub, Datadog, Sentry, any Internal tooling. If agents are being held back because of lack of context that’s your fault.
- invest in your codebase specific agent docs. stop saying “doesn’t do X well”. If that’s an issue, try better prompting, https://t.co/SOjpn47yxo, linting, and code rules. Tell it how you want things. Every manual edit you make is an opportunity for https://t.co/S1ZvtYQwta improvement
- invest in robust background agent infra - get a full development stack working on VM/sandboxes. yes it’s hard to set up but it will be worth it, your engineers can run multiple in parallel. Code review will be the bottleneck soon.
- figure out security issues. stop being risk averse and do what is needed to unblock access to tools.
in your product:
- always use the latest generation models in your features (move things off of last gen models asap, unless robust evals indicate otherwise). Requires changes every 1-2 weeks - eg: GitHub copilot mobile still offers code review with gpt 4.1 and Sonnet 3.5 @jaredpalmer. You are leaving money on the table by being on Sonnet 4, or gpt 4o
- Use embedding semantic search instead of fuzzy search. Any general embedding model will do better than Levenshtein / fuzzy heuristics.
- leave no form unfilled. use structured outputs and whatever context you have on the user to do a best-effort pre-fill
- allow unstructured inputs on all product surfaces - must accept freeform text and documents. Forms are dead.
- custom finetuning is dead. Stop wasting time on it. Frontier is moving too fast to invest 8 weeks into finetuning. Costs are dropping too quickly for price to matter. Better prompting will take you very far and this will only become more true as instruction following improves
- build evals to make quick model-upgrade decisions. they don’t need to be perfect but at least need to allow you to compare models relative to each other. most decisions become clear on a Pareto cost vs benchmark perf plot
- encourage all engineers to build with ai: build primitives to call models from all code bases / models: structured output, semantic similarity endpoints, sandbox code execution. etc
What else am I missing?
Manus is entering the next chapter: we’re joining forces with Meta to take general agents to the next level.
Full story on our blog: https://t.co/huPrnbITCi
@BucknSF https://t.co/3PiA8hT4iv
prob less than 2yrs, this is like <1wk side project
added web search earlier today + could add anything with an api
clip doesn't do justice on larger models, does pretty decent work feels like 6mo away from strong on most modeling use cases
fun exploration from the past couple of days, an excel add in that can both:
- passively observe your work and suggest edits, like tab complete in an IDE
- create plans and build models
fun exploration from the past couple of days, an excel add in that can both:
- passively observe your work and suggest edits, like tab complete in an IDE
- create plans and build models
@modestproposal1 with the various params available via the api (reasoning level, token allocation, web search, etc) i think approximating this is definitely possible
it's possible to take X min as a target and work backwards on params to have it take about that long
will start posting about a handful of custom tools + MCPs I've built and use day-to-day and also various half-baked product explorations (probably some open source)
to start, just a pleasant image from image gen MCP
📣Calling all app developers! Starting today, you can submit your ChatGPT app for review.
Approved apps will be listed in the app directory, a new surface for users to search for apps directly in ChatGPT. https://t.co/bO1OfXb0Em
GPTs within ChatGPT that are just additional hidden information and prompts aren't interesting (the base model and web search can handle this)
GPTs within ChatGPT that expose new tools and capabilities will be interesting
ChatGPT via GPTs will become a distribution channel itself to ship to - a layer in front of almost everything else
This hasn't happened yet because remote MCPs are only available on Pro tier with Deep Research toggled on
You can start building and testing apps in ChatGPT with the Apps SDK preview, which we're releasing today as an open standard built on MCP.
Later this year, we’ll begin accepting app submissions for publication.
https://t.co/pj4gUgso22
on the things that really matter, the distance between anthropic's models and competing models is actually growing, not shrinking
they might be pulling away
@jerhadf Truly a great model - if I had to reach for critique, occasionally exhibits “overeager” behavior present in sonnet 3.7 being a bit too agentic/ambitious/confident