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

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

На главную

One of our engineers built Errand, our open-source take on Grok Bot and Muse, and wrote up how it came together. One developer, one week. The app is ~4k lines of TS. Every agent still gets its own machine with a shell, a browser, and a filesystem that survives...

101,333 просмотров • 7 дней назад •via X (Twitter)

Комментарии: 4

Фото профиля Guanlan Dai
Guanlan Dai7 дней назад

Blog post on how he built it:

Фото профиля Yevhen 🇺🇦🇳🇱
Yevhen 🇺🇦🇳🇱7 дней назад

Four thousand lines is the real headline. Most of these are ten times that and do less.

Фото профиля Ernie Borgmine
Ernie Borgmine7 дней назад

Another great list. Picked up quite a few.

Фото профиля NiNE
NiNE7 дней назад

Steal: if you're about to write another agent VM layer, stop. Spend the week on the ~4k lines of product on top of a provisioner that already gives shell, browser, and a filesystem that survives between tasks.

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

THIS DEV BUILT A POLYMARKET BOT WITH GROK BUILD Now his AI agents print ~$2,700 per day PASSIVELY His wallet: [ Wanna hear the best part? He published the whole build for free. I've been building on Polymarket long enough to know what's real and what's a screenshot. This is real, and the wallet's public so anyone can check it. Here's what he actually did, for those who don't want to read the full thing yet: He took an arb bot, the kind that catches when Up and Down don't add up to a dollar, and rebuilt it around a team of Grok Build agents instead of one giant script. One agent hunts for the gap. One checks both legs can actually fill so you never end up naked on one side. One runs the fee math so a rebate-vs-fee mistake doesn't eat the whole edge. Then the bot merges each pair back into $1 instantly and recycles the capital, over and over. That recycling is the real secret, not the gap itself. A tiny edge run hundreds of times a day is where the $2,700 comes from. Here's what I respect about it. He's honest that the agents don't hand you the edge. They build the machine fast, but the strategy and the discipline are still on you. No "one prompt and you're rich" nonsense. Most people in this space would've locked this behind a paywall or a paid telegram. He put the code, the mechanics, and the wallet out in the open. If you're building bots and you're not following him, fix that. This is the honest version of what everyone else is trying to sell you. Attaching the full guide below.

Oracle Boar

30,741 просмотров • 1 месяц назад

A one-man trading hedge fund now costs about $100 a month in AI subscriptions. Five PhDs on a Citadel desk cost $270,000 a month, and that is the cheap end. That buys one tested idea a month. Man Group's AI writes hundreds of new signals a week, on a floor where the humans used to manage twenty in a quarter. Fifty AI agents do the reading and the writing. One of them exists only to destroy what the others build, and that one is the reason any of it works. Every job on that payroll is now an agent you can run yourself: > AI research agents reading filings, transcripts, options flow and on-chain data overnight, fifty personas at once, none of them allowed to see what the crowd is pricing > coding agent that turns one sentence of plain English into entry rules, exit rules, sizing and risk limits, then debugs itself until it runs > backtest agent that replays five years of that idea in about 12 seconds > breaker agent, an AI whose only job is killing the thing, at double the trading costs and in the ten worst markets that asset has ever seen > critic agent that reads your journal and names the mistake you keep making Nobody on that list asks for a bonus in January. $200 million is already run this way on one platform where 52,000 people mostly sit and watch the machine work. The full map of what is built and what is missing is in the article below. Bookmark & read it If you're not yet using AI in your trading and investing.

cvxv666

173,490 просмотров • 1 месяц назад

BlackRock runs on 20,000 people. Elon's Grok Bot runs the same shape for $300 a month, and it hires its own staff. You do not get an assistant. You get a company that hires. It does not throw ten agents at your problem and hand you the pile. It makes one agent that makes 10, and those ten make a 100. > LAYER ONE is one agent, the chief of staff, and it never touches the market > LAYER TWO is six desk heads, one job each, every one on its own computer with its own logins > LAYER THREE is whatever those six decide they need, spun up on the spot and shut down when the work is done Nobody writes a task list. You hand out job titles and the org fills itself in underneath. The swarm is never the same twice. Agents get spun up for one job, finish it, and are gone before I ever read their names. Not one of them sees the whole picture. The answer only exists after they hand off to each other. Wall Street cannot copy that. You cannot hire a hundred people for eleven minutes. BlackRock holds that shape together with a risk system called Aladdin. Mine holds it together with one agent that is only allowed to say no. I gave it $1,000 and told it to grow the money or get deleted. 15 hours later it was holding $3,900, on an address anyone can open and read. I was asleep for most of it, and I have still not written a line of code. The whole thing runs with my laptop shut, because none of it lives on my laptop. Setup is one evening. Create the chief, hand out the titles, run one trade on your screen while they watch, connect Telegram. Ten years ago a machine this shape had its name on a tower. Mine has a name I typed into a box. Save this while the whole thing still fits on one screen.

cvxv666

45,488 просмотров • 29 дней назад

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.

Akshay 🚀

123,101 просмотров • 3 месяцев назад

I'M SHOCKED – ALMOST NOBODY IS USING GROK BOT THE RIGHT WAY. A LEAD ENGINEER AT SPACEX AI JUST DROPPED A 1-HOUR COURSE ON HOW IT'S ACTUALLY DONE. HERE'S ALL OF IT IN 60 SECONDS. The mistake almost everyone makes: they hand Grok Bot random one-off tasks. That's it. That's the whole reason it still feels like a chatbot to you. Here's the system he teaches instead – five parts: → ROLE – stop assigning tasks, create permanent roles. Chief of Staff, Inbox Manager, Researcher, Developer, Reviewer. A bot with a job title beats a bot with a to-do list → TOOLS – connect each bot to what it actually needs: Gmail, Slack, Calendar, Notion, GitHub. It does the work on its own persistent cloud computer → SKILL – teach it your workflow. Write the instructions, or just record yourself doing the job once – Grok Bot turns that demonstration into a reusable skill → ROUTINE – anything you repeat becomes a routine. It runs on a schedule or fires off an event, with your laptop closed → TEAM – group the bots together. The lead bot delegates, the specialists work in parallel, and you set approval rules before anything sends an email, moves a calendar or pushes code The one honest catch: a new bot still needs context and some hand-holding on its first few runs. But that's the entire system. Role → Tools → Skill → Routine → Team. Everyone else is still typing one-off prompts into Grok Bot and wondering why nothing compounds. Bookmark this & read the full breakdown in the article below ↓

SCOTTY BEAM

97,697 просмотров • 1 месяц назад