Загрузка видео...
Не удалось загрузить видео
Agents already speak git. Artifacts lets you create and fork repos from a Worker, hand out tokens, and clone with any git client, with events on every push. Now in open beta on the Workers Paid plan. Build the next GitHub? Here's how it works:
47,792 просмотров • 2 дней назад •via X (Twitter)
Комментарии: 8

Brb, gonna recreate google docs

the primitives you guys are pumping out recently are goated

Artifacts gets useful when the repo event becomes a run receipt: actor, token scope, commit hash, pushed files, webhook result, revoke time. Agents can fork and hand work off without turning one long-lived token into the trust boundary.

Where Clef post?

This approach is way cooler than it might seem at first. If I understand it correctly, it lets you work with any dataset that can be stored in Git, with versioning and the same workflows you already use for code. And you don’t have to deal with Git LFS. Git for everything. Very cool.

Thank you for the product and the explanations! But I still struggle a bit to understand the mental model: can I use it as a VCS for the users of my SaaS?

can one apply from EU?

can you lock a token down to a single branch or is it repo wide only



