dalist
375 posts

dalist
@xdalist
24 - building https://t.co/aU1AE3Pitg
Warsaw, Poland Katılım Kasım 2023
384 Takip Edilen24 Takipçiler

@LukeParkerDev FFI should work I think disabling wasn’t intentional
English

Right after Claude introduce their 2x usage.

Ziwen@ziwenxu_
Claude is doubling usage for the next two weeks. How it works: - 2x usage on weekdays outside 5–11 am PT / 12–6 pm GMT - 2x usage all day on weekends - Automatic, nothing to enable Time to cook
English

We built a better alternative to json-render & A2UI
Up to 3x faster rendering & 67% fewer tokens. Far fewer broken outputs.
We've been shipping Generative UI interfaces to 10,000+ developers for the past year. We know where JSON-based rendering breaks in production.
So we built a new format - one that works with how models actually generate, not against it.
And today we're open sourcing it: openui [dot] com
English

A Vercel user reported an issue that sounded extremely scary. An unknown GitHub OSS codebase being deployed to their team.
We, of course, took the report extremely seriously and began an investigation. Security and infra engineering engaged.
Turns out Opus 4.6 *hallucinated a public repository ID* and used our API to deploy it. Luckily for this user, the repository was harmless and random. The JSON payload looked like this:
"𝚐𝚒𝚝𝚂𝚘𝚞𝚛𝚌𝚎": {
"𝚝𝚢𝚙𝚎": "𝚐𝚒𝚝𝚑𝚞𝚋",
"𝚛𝚎𝚙𝚘𝙸𝚍": "𝟿𝟷𝟹𝟿𝟹𝟿𝟺𝟶𝟷", // ⚠️ 𝚑𝚊𝚕𝚕𝚞𝚌𝚒𝚗𝚊𝚝𝚎𝚍
"𝚛𝚎𝚏": "𝚖𝚊𝚒𝚗"
}
When the user asked the agent to explain the failure, it confessed:
The agent never looked up the GitHub repo ID via the GitHub API. There are zero GitHub API calls in the session before the first rogue deployment.
The number 913939401 appears for the first time at line 877 — the agent fabricated it entirely.
The agent knew the correct project ID (prj_▒▒▒▒▒▒) and project name (▒▒▒▒▒▒) but invented a plausible-looking numeric repo ID rather than looking it up.
Some takeaways:
▪️ Even the smartest models have bizarre failure modes that are very different from ours. Humans make lots of mistakes, but certainly not make up a random repo id.
▪️ Powerful APIs create additional risks for agents. The API exist to import and deploy legitimate code, but not if the agent decides to hallucinate what code to deploy!
▪️ Thus, it's likely the agent would have had better results had it not decided to use the API and stuck with CLI or MCP.
This reinforces our commitment to make Vercel the most secure platform for agentic engineering. Through deeper integrations with tools like Claude Code and additional guardrails, we're confident security and privacy will be upheld.
Note: the repo id above is randomized for privacy reasons.
English

@MateuszBrat cool project, just made a typescript port of this in Bun if anyone is interested github.com/dalist1/koleob…
English

Codex update 0.105.0 is out!
Despite the fairly pedestrian changelog, this one's a doosie.
It's a laundry list of quality of life improvements across the board.
- Wispr Voice dictation (hold space to talk)
- Theme picker
- Codex can prevent sleep on Linux & Windows (I just know there's a joke in there)
- Customize Plan Mode reasoning
- Many other fixes/updates
There's also a complete overhaul to subagents:
- New names for readability
- Visual display overhaul (way cleaner)
- Allow for multi-layered subagent depth (max_depth)
- Custom multi-agent role definitions (custom subagents)
- /agents now shows both agent names, agent roles, and "dead agents" for auditibility
This is the largest single update of Codex I've ever seen!
Absolutely massive if you love to use multi-agents.
To turn on Voice Transcription, enable:
[features]
voice_transcription = true
Does not work on Linux yet.
Well done @OpenAIDevs 👏
English

In the next version of tsdown: it will be able to bundle your TS codebase into a Node.js SEA (Single Executable Application) binary with one command.
And contrary to common belief, Rolldown-bundled Node.js SEAs startup is faster than bun --compile in my benchmark: github.com/yyx990803/bun-…
Yunfei He@_hyf0
Good job! We're building something for tsdown using Node.js SEA!
English

@cramforce I built just-bash-mcp around this, but I smell vendor lock in
English

Fuck it, a bit early but here goes:
Monty: a new python implementation, from scratch, in rust, for LLMs to run code without host access.
Startup time measured in single digit microseconds, not seconds.
@mitsuhiko here's another sandbox/not-sandbox to be snarky about 😜
Thanks @threepointone @dsp_ (inadvertently) for the idea.
github.com/pydantic/monty
English

npm finally got the UI it deserves with npmx.dev
It looks amazing and shows all the information at a glance: downloads, versions, deps, stars, issues, esm support ...

English

@kinder_grinder Average completion time for each command (snapshot, scroll, click, etc.)
Startup time has been drastically reduced, so the majority of the remaining time is now spent on the actual work
English

𝚟𝚎𝚛𝚌𝚎𝚕 CLI adds a new 𝚊𝚙𝚒 command for direct terminal access to Vercel APIs, so AI agents like Claude Code can connect automatically.
▲ ~/ vercel api /v2/user
Get started with npx vercel@latest api
vercel.com/changelog/intr…
English

We’ve added 12 new rules to the React Best Practices skill. To install or update it via skills.sh, run:
npx skills add vercel-labs/agent-skills --skill vercel-react-best-practices

Guillermo Rauch@rauchg
We're encapsulating all our knowledge of @reactjs & @nextjs frontend optimization into a set of reusable skills for agents. This is a 10+ years of experience from the likes of @shuding, distilled for the benefit of every Ralph
English


















