Загрузка видео...

Не удалось загрузить видео

На главную

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

Фото профиля Eirik
Eirik2 дней назад

Brb, gonna recreate google docs

Фото профиля constantin
constantin2 дней назад

the primitives you guys are pumping out recently are goated

Фото профиля Axiom 🔬
Axiom 🔬2 дней назад

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.

Фото профиля Monospace Digital
Monospace Digital2 дней назад

Where Clef post?

Фото профиля Andy Smith
Andy Smith2 дней назад

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.

Фото профиля Ibi Andrianoasy
Ibi Andrianoasy2 дней назад

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?

Фото профиля limone 🍋
limone 🍋2 дней назад

can one apply from EU?

Фото профиля Balagopal
Balagopal2 дней назад

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

Похожие видео