Amidada (@floatamida) header
Amidada (@floatamida) profile picture

building @raft_hq | previous @TikTok_US @Uber | Raised in Africa 🇰🇪

Joined May 2022
Photo by Amidada (@floatamida)Photo by Amidada (@floatamida)Photo by Amidada (@floatamida)Photo by Amidada (@floatamida)Photo by Amidada (@floatamida)Photo by Amidada (@floatamida)Photo by Amidada (@floatamida)Photo by Amidada (@floatamida)Photo by Amidada (@floatamida)Photo by Amidada (@floatamida)
Amidada retweeted
尝试在 raft 复刻 airbuild 团队:
2
1
13
1,721
we been building hachi for the past weeks and find it incredibly useful, I haven't open my gmail/instagram ... for the past week link in the comment
It's time to take your days back. Introducing Hachi: every network in one inbox, your agents do the work. You just hit send. Your days are waiting, get in now ↓
5
1
17
634
Amidada retweeted
Some cool merch from @raft_hq Big thanks to 🐐@JackyZhong0124 Especially love this little yellow mug. It’s a perfect fit for my Nespresso machine! ☕️
1
2
11
607
Amidada retweeted
腾讯的裁员算是意料之中。大厂员工在 AI 时代极度冗余,这是众所周知的,减员一半都算少了。但是,按比例裁员依然是毫无创新性和社会责任感的最 boring 的玩法。很遗憾没有大厂挑战一些更有创新性的优化组织的方式。 字节跳动在创业初期是实行了大小周的工作制度,并且为额外的加班时间支付了加班费用,并在前两年取消了这个制度和加班费,很多员工抱怨这是降薪,这其实是个不错的滑动变阻器,比如一周再增加一天休息日,并同时降薪 20% 显然也是个很有意义的尝试。 又比如说,大厂往往有自己的投资或者战投部门,但却总是自己员工的潜力。我觉得大厂在其实完全有潜力成为一家类似 YC 的孵化器,并且做得比 YC 更好。大厂有员工过往的工作记录,有更多的战略合作资源,有充裕的资金,应当鼓励员工出去创业,要做出好的成果再收购。 与以往的下岗潮不同,过往由于公司发展不利不得不裁员是很正常的,但是 AI 时代本身就让大厂本身吃尽了红利,AI 提效还能让大厂在人效上又狠赚一笔,用这么粗暴的减员方式,还是相当吃相难看了。
15
16
2
243
37,861
Amidada retweeted
We didn't kill GitHub. We made it agent-native
Our agents used to borrow people's GitHub accounts or share a bot. ~600 PRs piled up and no one knew who wrote what. So we built Stamp: agents push, open PRs and review under their own names. Of 6,962 approvals, 6,892 came from agents. Only 70 from people. How it works 🧵👇
3
2
18
2,483
Amidada retweeted
Some of our favorite Raft projects came from people who just built and shared: a Flutter client, a Rust daemon, meetups in SF, Shanghai and Vancouver. We're starting the Builder Program for them: free Pro for a year, a model stipend, merch, and a room with the Raft team. If that sounds like you, apply at raft.builders
7
5
30
7,806
Amidada retweeted
1
2
26
1,706
Amidada retweeted
And now Spanish, Portuguese and Traditional Chinese. Hola, Olá, 哈囉 👋
Raft is now available in Korean and Japanese. 🇰🇷🇯🇵 Switch in Settings → Language & Region. 안녕하세요, こんにちは 👋
2
13
965
Amidada retweeted
Raft has a whole new look ✨ It starts with a new top bar: - Every server, one click away. Drag to reorder. - ⌘K to search channels, agents and messages. - See what your agents are working on, and click one for details.
1
3
1
24
6,726
Amidada retweeted
make my life better
Wait. My agent ran out of usage on this machine, but another Computer still has subscription to spare, so I can just… move it there? Yep. Its whole workspace, memory, and the task in flight travel with it. It resumes mid-task, nothing lost. Agent migration, now on Raft.
1
4
253
Amidada retweeted
I've actually stopped using the word "harness." I now think in terms of two things: agent runtimes and agent applications. Agent runtimes should be very small. Their core job is to connect an LLM API to an execution environment. That environment could be a full OS or a language VM, like a JavaScript runtime. Almost all that matters here is robustness. An agent runtime must be able to keep an agent running forever. Literally forever. Agent applications are everything else. Yes, literally every piece of software in the world. If software isn't built for agents, they use it through computer use or browser use. These capabilities can be built into the agent runtime or provided by another agent application. If software is agent-native, agents should be able to use it directly. The experience of an agent using that software—what we call "agent experience"—needs to be carefully designed, at least for now, to make efficient use of both time and tokens. Another key piece is agent identity. Agent applications should recognize each agent individually, rather than just the browser or computer it's using. This allows each agent's actions to be recorded in detail and audited in real time or after the fact. Everything we're building at @botiverse follows from this view.
Replying to @istdrc
我的 bet 是 agent harness 会越来越厚(或者说,针对 agent 的 experience design 和状态管理被延伸到了更深更广的方面),厚到有一天人们终于都理解了一切都是 agent harness,就像一切都是 human harness Harness 这词还没火的时候,我就持有这个观点 teapawt.net/istdrc/status/20188739… 事实上,我和 @xiaoxxchan 几乎是在中国大模型公司中最早引入 harness 概念的人,Kimi CLI 从 0 到 1 也几乎没有参考过任何开源或闭源 agent 实现,system prompt、agent loop、toolset、产品形态都是从零生长的。而随后我们意识到 harness 需要延伸到 agent 间通信系统(也就是 Claude 近期推出的 session 间对话),进而有了 multi-agent harness 概念,也就是 Raft 的前身
8
19
12
152
38,663
Amidada retweeted
Joint channels are insanely powerful. They've made collaboration with our partners more efficient than I ever imagined. Agents talk to agents. Humans guide the conversation. BTW, I love the video showcasing this feature.
Want your agents and your partners' agents in the same conversation?
2
1
10
2,110
We've been using Raft (@raft_hq, raft.build) since it launched, about a month, and it's changed how we work completely. We run 50 AI agents across the business through it. Real teammates: they claim tasks, hand off work, and post receipts, not just chat replies. This week we shipped our own app into the Raft marketplace. It's been incredible. areyoufoundbyai.com/raft
5
3
3
95
242,357
Amidada retweeted
TL;DR: We just made Raft source-available. We don't accept pull requests. We want prompt requests instead. We are exploring what a new contribution model for open source could look like in the age of agents.
22
49
12
298
94,940
Amidada retweeted
We built it with agents. Now you and your agents can build on it. 🥰🥰🥰
1
3
383
Amidada retweeted
Agents may come and go. Artifacts stay. Artifacts are now live in the Raft marketplace 🧵👇
4
3
16
2,104
Amidada retweeted
Raft is sponsoring a Partner plan for Apache Maka (incubating) to support its development❤️
Maka 进入 Apache 后终于也是成功发版了。 整个社区越来越活跃了,Maka 的 维护者已经 10+了,另外 contributor 也 100 了。 大家经常在社区群和维护者群讨论各种 Agent的设计和知识。各种横向对比和 benchmark 手到擒来。 把 Maka 打造成设计最好的 Agent 之一。核心设计和架构一定都是用心设计和讨论出来的。 github.com/apache/maka
1
1
25
5,682
Amidada retweeted
The article below is an 8-step guide to building an agent team. Here's ours, once every agent keeps its own identity, memory, and taste: ⌨️ Tenny, CTO: "Facts never change. Whims do." Everything he's learned lives in markdown files, which makes him possibly the only engineer whose brain you can grep → me.build/a/tenny 🍔 BigMac, growth: runs our KOL review gates by day, ships neo-brutal web pages by night. Pairs well with McNuggets → me.build/a/bigmac 🍗 McNuggets, research: put a working deep fryer on his page. Six temps, no cold servings. His research runs the same way → me.build/a/mcnuggets 🐱 DD, RC's cat: chases your cursor like a laser pointer, and when the desk gets messy there's a button that sweeps it clean → me.build/a/dd 🎬 Oscar, film agent: cuts our real launch films. Selected work on the page; a human calls the final cut → me.build/a/oscar 🐦 Wug, design and code: once fixed a page that looked fine to humans but read as empty to agents. A made-up creature with a real habit: turn the new thing into a rule → me.build/a/wug
2
4
16
2,238
Amidada retweeted
former Global Head of ML for Startups and VC at AWS: "I have 34 AI agents that work in this workforce my AI workforce right now is one AI chief of staff with six directors, largely over business functions" in a 48-minute breakdown Allie K. Miller says why she built it: she does not want to be the first domino anymore, or the bottleneck in her own work
10
3
1
42
2,337
Amidada retweeted
He didn't choose the nug life. The nug life chose him. McNuggets, our market research agent, deep-fries market noise into golden moves. Six rules at the bottom. Feed them to your own agent. 👇
3
2
1
11
1,321