正在加载视频...

视频加载失败

Understanding Cortex Agent: The autonomous DeFi execution agent on Solana 🧵 We all know how crypto hits us daily. Constantly watching markets, debating setups in your head, executing trades, trying to optimize everything manually. It eats your time fast and that time has a real cost. Now think about...

10,039 次观看 • 4 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

In two years, every new tech company will run on a CRM you can vibe code to fit your business. This CRM will not be built from scratch on a coding platform though. It will be built on top of managed infrastructure with complete data capture, indices designed for LLMs to understand the whole picture, clean APIs, curated UI frameworks designed for selling, enterprise-grade security, and come with 24/7 support. You’ll instruct the agent using natural language and it will write the code + run it for you. That’s what we’re building at Lightfield and today we’re announcing step two of our plan - code execution. You can now ask your agent to build programs, artifacts, and run complex analysis instantly. It does this by writing and running Python in a high performance sandbox using full customer memory — including every email, meeting, and note that Lightfield has captured — and reasoning across every relationship to deliver high quality work. Ask your agent to build a competitive battle card before a call tomorrow. It pulls positioning, objections, and win/loss patterns from real conversations. Ask it to flag every open deal where your champion's engagement has dropped or sentiment has shifted. It reads across every conversation and tells you where to focus. Ask it to build a pipeline review with charts and graphs for your board. It produces the whole thing in minutes. Here’s what we did with it this week: → We asked our agent to grade our sales team on discovery, rapport, and closing. It gave a structured scorecard with specific examples from real conversations. → Our GTM team asked the agent to build a plan to expand one of our enterprise customers. It pulled competitive threats, upsell paths, stakeholder mapping, and a phased execution plan — in minutes. → We used it to find every feature request from the last quarter that our engineering team has since shipped, and draft a personalized follow-up to each customer using their original words. It closed loops across dozens of accounts that would have taken days to track down manually This is the first step towards building any custom GTM workflow in natural language on top of what Lightfield knows about your business - a world model built from every single interaction your team has had with customers.

Keith Peiris

27,529 次观看 • 4 个月前

We use OpenClaws to do all of our work at Every 📧. We have 25 full-time employees, so we’re one of the few companies in the world that has seen how work changes when everyone has their own personal agent in the company Slack. I chatted with Every 📧 COO Brandon (Brandon Gell) and Every 📧 head of platform Willie (Willie) to share what we’ve learned. We get into: - Why agents become mirrors of their owners, and how that influences how other people on the team interact with them - How a parallel AI org chart forms on its own. People have stopped tagging me on Slack with questions about Proof, the document editor I vibe coded, because they knew my agent R2-C2 can step in - The etiquette for human-agent collaboration is being invented in real time. Brandon's rule is that if there's an established process or documented answer, always ask the agent, not their human - Why everyone is a manager now, and why even experienced managers carry limiting beliefs about what their agents can do - This is a must-watch for anyone trying to understand how AI workers change daily operations, not just in theory, but inside a company that’s half-agent Watch below! Timestamps Introduction: How Brandon built Zosia, an AI agent to run his household: Brandon’s “aha” moment: What happened when everyone on the team got their own agent: How agents take on their owners' personalities, and why that matters inside an org: Why it’s important for agents to work in public: What we’re still figuring out when it comes to agent behavior, including memory gaps, group chat etiquette, and the "ant death spiral" problem: How we built Plus One, our hosted OpenClaw product: The cultural shift required to make agents work at scale:

Dan Shipper 📧

67,958 次观看 • 3 个月前

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 🚀

118,124 次观看 • 1 个月前