正在加载视频...

视频加载失败

Just created Grok 3 AI Customer Support Agents 🔥 🤖 Grok 3 reads docs & builds the agent Elon Musk 🔍 DeepSearch for In-depth search ⚡ Flask web app + API setup 🚀 Browser-based deploy - Replit ⠕ Amjad Masad ✨ Zero manual coding needed PraisonAI Step-by-Step Tutorial: 👇

3,620,768 次观看 • 1 年前 •via X (Twitter)

9 条评论

Shubham Saboo 的头像
Shubham Saboo1 年前

@elonmusk @Replit @amasad @PraisonAI Would have appreciated the idea source credits if you are gonna use the exact idea for your post.

Rickyticky Bobbywobbin 的头像
Rickyticky Bobbywobbin1 年前

INTRODUCING: Agentic Security - LLM Security Scanner! 🔍 🔑 Features: Scans for prompt injections, jailbreaking & more. Provides detailed reports & options to customize attack rules. 🔗access the GitHub Link ↓

justswap 的头像
justswap1 年前

@elonmusk @Replit @amasad @PraisonAI Wanna endorse it ?

ZAZO 的头像
ZAZO1 年前

@elonmusk @Replit @amasad @PraisonAI Well that’s crap any model cal give you code even Replit alone will do the same as well don’t know what’s the hype is all about

justswap 的头像
justswap1 年前

@amasad @elonmusk @Replit @PraisonAI A coin was created for you Wanna endorse it ??

ZAZO 的头像
ZAZO1 年前

@elonmusk @Replit @amasad @PraisonAI Real deal is when the API is available for Grok3 and we can test it locally on Cursor

Space Universe 的头像
Space Universe1 年前

Grok 3 AI Customer Support Agents = Next-Level Automation! 🤖🔥 Here’s how you built it with zero manual coding: 1️⃣ Grok 3 reads the docs and generates a fully functional AI agent. 2️⃣ DeepSearch allows for in-depth, accurate responses. 3️⃣ Flask web app + API setup for easy integration. 4️⃣ Deployed in the browser via Replit, quick and accessible. This is customer support on steroids, no need for manual coding, just AI-powered efficiency! 🚀

Steveyam 的头像
Steveyam1 年前

@elonmusk @Replit @amasad @PraisonAI Is it free?

Auny 🧡 的头像
Auny 🧡1 年前

@elonmusk @Replit @amasad @PraisonAI Absolute banger. People can learn a lot from this! Thanks for sharing ❤️

相关视频

🚀 Less managing, more creating. Building app usually means: • Hours lost debugging • Constantly juggling tools • Non-stop AI hand-holding Replit’s new Agent 3 changes that entirely → ⁠ We just tried out Agent 3, and it’s impressive! ⁠ It’s not another ordinary AI coding assistant. It’s a full-on collaborator that: • Runs autonomously for up to 200 minutes, building your app from start to finish. • Tests its own work in a real browser and fixes bugs automatically, saving hours of manual debugging. • Lets you build other agents and automations (think Slack bots, Telegram reminders, email summaries). ⁠ Here's why Agent 3 is different: Unlike traditional AI tools where you constantly babysit and prompt, Agent 3 understands your idea and takes charge, freeing you to focus on creativity, strategy, or simply grabbing coffee while your app builds itself. And to show how easy it is, we built a complete waitlist app in less than an hour, from idea to almost finished product. No babysitting. No endless tweaking. ⁠ Replit ⠕ is calling this “Autonomy for All,” and after seeing Agent 3 in action, it’s easy to see how it can bring millions more creators online. ✅ Faster builds ✅ Less frustration ✅ More polished, reliable apps With Agent 3, app-building really does feel less like wrestling with software and more like collaborating with a teammate. ⁠ Try Replit Agent 3 yourself today…👆 Get $10 credit when you purchase Replit Core using our link above!

There's An AI For That

40,330 次观看 • 10 个月前

🚨BREAKING: The future of building software just changed. Replit ⠕ just launched Agent 3 and it changes everything. Heres is what Agent 3 can do: ☑ Runs autonomously for 200 minutes ☑ Tests and fixes its own code in a real browser ☑ Builds bots & automations across Slack, Telegram, Email ☑ 10x more autonomy, 3x faster, 10x cheaper Try Agent 3 now: The gains compound with capability. Old agents wrote code. Agent 3 writes, tests, and deploys it. Old agents stopped at output. Agent 3 builds entire workflows end-to-end. Old agents needed babysitting. Agent 3 runs like a teammate. You thought AI coding tools would always need your hand-holding. Wrong… Agent 3 rewards clarity like compound interest. Clear goals = stronger autonomous performance. Not just faster execution. Smarter execution. But what use cases win? Automations dominate everything: ☑ Slackbots that query data on demand ☑ Telegram bots that send daily reminders ☑ Email workflows that ship reports overnight Tasks you once hacked together with 3rd-party tools? Now built inside Replit. Your skill level doesn’t matter either. Designer, PM, founder, engineer the pattern holds. Give the Agent your intent, it does the heavy lifting. The reality: Prototype fast → one prompt. Build with data → no plugins needed. Deploy instantly → baked in. Monitor growth → already included. But clarity still matters. Vague prompts won’t save you. ☑ Start with a clear project idea. ☑ Let Agent 3 handle the heavy lifting. ☑ Iterate on results. ☑ Scale from there. Your competition is still stitching tools together. You now know better. Try here: (Get a $10 Core credit to kick off your build) Autonomy for All Repost ♻️ so more people discover this.

Muhammad Ayan

47,180 次观看 • 10 个月前

The new Google Search is rolling out and there seems to be confusion on what it will look like. Google literally told us. Let me clarify for anyone who is still unsure of what is rolling out this week. Last month Google responded to everyone saying Search is dead. Here is what they said: "You will absolutely continue to see blue web links in search results. AI Mode is not the default experience in Search. You will continue to get a range of results on Search." [Want to know where your site stands across Google AI, ChatGPT, Claude, Grok, etc? Check here (it's free): Google has explicitly laid out what Search will look like from this point going forward. The new Search box accepts text, images, files, videos, and open Chrome tabs. It anticipates your intent before you finish asking. It is powered by the most advanced Gemini model Google has ever put into Search, and layered on top of that, information agents will now be able to run 24/7 in the background on behalf of your buyer. Think of it in 5 steps: Step 1: The buyer describes their problem, their category, their needs in full. Step 2: The agent breaks that down into sub-topics and maps out a plan. Step 3: It determines what intel is needed right now versus later. Step 4: It monitors blogs, news sites, and social posts continuously for relevant changes. Step 5: It sends the buyer a synthesized update with links and the ability to take action. Blue links are not going away in the short-term, but the brands getting recommended by information agents 24 hours a day while also ranking in traditional results are going to pull so far ahead of the ones doing only one or the other that it will not be a fair fight. This is exactly what SEO Stuff ( has been building for every customer. Optimized content depth that covers every sub-question a buyer in your category asks, so the agent finds you at every step of its plan. Editorial authority from trusted websites that signals credibility to every retrieval system Google has ever built, across both traditional rankings and AI citations simultaneously. One investment. Blue links and AI citations. Around the clock. SEO Stuff's Complete Done-For-You Plan: SEO Stuff's "Optimized Content" Plan: There is a reason more than 80 percent of SEO Stuff customers reorder. The results continue long after the work is done. Google Search is changing. AI Search is here. Your websites need to prepare accordingly. Want to know where your site stands across Google AI, ChatGPT, Claude, Grok, etc? Check here (it's free):

Alex Groberman

44,078 次观看 • 25 天前

Anthropic's Claude Ai Agents Team just Educated how to build production AI agents in under 30 mins. For Free. From the engineers who built the stack. CANCEL Your Weekend Plans, and Learn to Build AI Agents Today. Bookmark it. Watch it. Build your first production agent this weekend. $5,000/month. $7,000/month. $12,000/month. People are building agents for clients and charging $$$ as Beginners. You're still stuck in the thinking about AI phase. This video fixes that tonight. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward. ↓ Ivan Nardini runs Developer Relations for AI at Google Cloud. He just gave away the entire production agent stack in 30 minutes. This is the talk that separates people deploying AI agents that actually scale from people whose agents break the moment they leave localhost. Here's everything inside. I break down a production AI video like this every week. Follow Himanshu Kumar. ↓ The 4-part agent stack that actually scales. Most devs are duct-taping frameworks together and calling it an "AI agent." Ivan lays out the real stack: Agent Development Kit (ADK): open-source, code-first framework for building, evaluating, and deploying agents. Supports Claude models through Vertex AI directly. Model Context Protocol (MCP): lets your agent talk to any tool or data source with one standard. Vertex AI Agent Engine: managed platform for deploying, monitoring, and scaling agents in production. No DevOps headaches. Agent-to-Agent Protocol: open protocol so agents built on different frameworks can actually work together. This is the stack replacing every hacky agent setup in production right now. Full MCP + Claude breakdowns drop weekly on Himanshu Kumar. ↓ Building your first real agent. Ivan builds a birthday planner agent live. LLM Agent class. Name it. Define instructions. Pick the model. He uses Claude 3.7 Sonnet. You could use Opus 4.7 for better reasoning. Full agent built in minutes. Not weeks. Watch the build once and you'll never structure an agent the wrong way again. I post agent architectures people pay $500 courses to learn. Himanshu Kumar. ↓ Multi-agent systems without the chaos. Single agents are easy. Multi-agent systems are where 99% of builders fail. Ivan extends the birthday planner by: Adding a calendar service through MCP tools Creating an orchestrator agent to route requests between agents Handling state and context across agent handoffs This is production multi-agent architecture. Clean. Scalable. Debuggable. Most tutorials hand-wave this part. This one shows you every step. Multi-agent orchestration content drops weekly on Himanshu Kumar. ↓ Deployment without the DevOps nightmare. This is where most AI projects die. You build a cool agent locally. It works. You try to deploy it. Everything breaks. Vertex AI Agent Engine fixes this: Minimal code deployment Automatic monitoring of latency, CPU, and memory Built-in observability and logging No infrastructure setup needed You provide config and requirements. The platform handles the rest. This is how agents actually get to production. Deployment guides for Claude agents post every week. Himanshu Kumar. ↓ Agent-to-Agent Protocol: the future nobody's talking about. Most people don't know this exists yet. The A2A Protocol lets agents built in different frameworks communicate seamlessly. Your Claude agent. My LangChain agent. Someone else's CrewAI agent. All talking to each other. All solving parts of the same problem. All without custom integration code. This is the infrastructure layer of the coming AI economy. Getting in early on A2A Protocol is like getting in early on HTTP in 1995. A2A deep dive coming soon. Himanshu Kumar. ↓ 30 minutes from the team shipping this in production. You'll learn more from this than from 6 months of YouTube tutorials made by people who've never deployed an agent past localhost. People who watch this understand production AI agents at the architect level. People who skip it keep hacking together frameworks that break every time an API updates. Save the video. Watch it tonight. Build a real agent this weekend. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward.

Himanshu Kumar

226,535 次观看 • 2 个月前

Introducing Sharpe Search: On-Chain Search AI Agent Powered by Hive Intelligence We’re thrilled to announce the launch of Sharpe Search, a crypto search AI agent powered by Hive Intelligence Designed to simplify blockchain data interaction, Sharpe Search represents a significant step toward making crypto more accessible and actionable for users at every level. Sharpe Search leverages Hive Intelligence’s advanced search API to provide real-time, actionable insights across the blockchain ecosystem. Here’s a detailed look at what Sharpe Search is, how it works: What Is Sharpe Search? At its core, Sharpe Search is an AI agent purpose-built for querying and analyzing on-chain data. It takes the complexity out of blockchain exploration by enabling users to ask questions in plain language and receive detailed, accurate responses. Whether you’re looking to monitor wallet activity, track portfolio positions, or analyze transaction history, Sharpe Search ensures that the answers are at your fingertips—accurate, comprehensive, and delivered instantly. How Does Sharpe Search Work? Sharpe Search is powered by Hive Intelligence, a search engine API designed to make blockchain data easily accessible and AI-ready. Here’s a breakdown of how it enables Sharpe Search to function effectively: 1. LLM-Optimized Query Processing Sharpe Search leverages Hive Intelligence's optimized responses for large language models. This ensures that AI agents can process blockchain data in a structured format, delivering precise answers to complex user queries. 2. Natural Language Interaction Forget the need for technical knowledge. Sharpe Search supports natural language queries, making it as simple as typing: - “What tokens are in my wallet? Am I eligible for any airdrop I haven't claimed yet?” - “Check me my last 100 transactions, tell me if I interacted with any protocol with recent hacks” - “Track my wallet activity over the past month, suggest optimised portfolio based on best stable yields available” 3. Real-Time Insights Across Multi-Chains Using Hive Intelligence, Sharpe Search connects to over 20 chains and 5000+ Protocols. This real-time access ensures that the AI agent provides up-to-date and actionable insights, no matter how dynamic the blockchain environment. 4. Unified API Access Sharpe Search consolidates fragmented blockchain data through Hive’s unified API. Instead of dealing with multiple integrations, Sharpe Search uses a single access point to aggregate and query data, reducing complexity for both users and developers. Technical Depth: The AI Agent Advantage Sharpe Search's design philosophy revolves around the principle of creating an intuitive, AI-driven experience. Here’s what makes its technology stand out: Data Indexing and Aggregation: Hive Intelligence employs advanced indexing algorithms to aggregate data from multiple chains. This ensures that Sharpe Search can retrieve information within milliseconds, even when querying vast datasets. Dynamic Updates: Blockchain data is volatile. Sharpe Search processes dynamic updates in real time, enabling users to act on the most recent metrics, transactions, and balances without delays. Contextual Understanding: The AI agent parses natural language queries and contextualizes them to blockchain-specific scenarios. For instance, when querying “Show portfolio details,” Sharpe Search understands the underlying requirements—fetching wallet holdings, token values, and current positions. Hive Intelligence: The Backbone of Sharpe Search While Sharpe Search takes center stage, Hive Intelligence provides the critical infrastructure to make it all possible. Its LLM-ready responses and multi-chain support ensure that Sharpe Search operates at the forefront of blockchain data accessibility. By launching Hive Intelligence through Sharpe Launchpad, Sharpe reinforces its commitment to supporting innovation in the blockchain space. Hive’s infrastructure not only powers Sharpe Search but also lays the groundwork for future AI agents to thrive in the ecosystem. What’s Next for Sharpe Search? Currently in invite-only access, Sharpe Search is preparing for a broader public release. Future updates will include: - Expanded Blockchain Coverage: More chains and protocols will be added. - Enhanced Query Flexibility: Even more advanced natural language capabilities. Stay tuned for the public launch and get ready to explore crypto like never before!

Sharpe AI

263,255 次观看 • 1 年前

This Claude MCP AI Agent replaces your $200K+ Operations Teams. I probably shouldn't be sharing the exact system for free... while I was trying to catch Pikachu at 3am on Pokemon Go, it audited my entire business, found 12 bottlenecks, and built me 5 production-ready n8n agents the efficiency gain is absolutely INSANE most founders burn months hiring ops consultants who charge $500/hour just to tell you what's broken this agentic system does their entire job in minutes here's what happens when you deploy it: → runs complete business intelligence audit in 3 minutes (what takes consultants weeks) → identifies 12+ workflow bottlenecks killing your efficiency → architects custom agentic systems tailored to your business → builds 5+ autonomous AI agents with advanced error handling → creates intelligent orchestration layer syncing everything together → delivers complete operational transformation in under 10 minutes the entire audit that consultants charge $50K for now happens in 10 minutes ZERO technical knowledge needed ZERO expensive consultants required ZERO months of back-and-forth just describe your current setup and watch it build your agentic empire the math is stupid simple: $200K ops team salary vs one-time MCP deployment that's $16,600 saved monthly the system includes: - intelligent business stack analyzer - bottleneck detection AI - custom agentic architect - autonomous agent builder - complete deployment documentation this is the exact system building 7-figure operational infrastructure and you're getting it for free Follow + RT + comment "MCP" & I'll send you the FULL setup guide tonight don't sleep on this every week you wait is 30+ hours of manual work you'll never get back

Aryan Mahajan

146,227 次观看 • 1 年前

Google just announced the biggest upgrade to Search in over 25 years. For brands the opportunity here is pretty enormous. Here is what the new Search actually looks like and how you should take advantage: The search box now accepts text, images, files, videos, and open Chrome tabs. It expands dynamically as you type. It also anticipates your intent before you finish asking. This is the version of Search that SEO Stuff has been helping customers build for. The biggest opportunity here is what happens after the search. Google's new information agents run 24/7 in the background on behalf of your buyer. And that's why it has never been more important to understand how Google, ChatGPT, Claude and every other AI platform sees your brand. (If you want to see where your site stands across Google and AI search, start here: Here is exactly how Google's new information agents work: Step 1: The buyer does a total brain dump of what they want to stay updated on. Essentially a full description of their problem, their category, their needs. Step 2: The agent breaks down that question and maps out a plan across every relevant sub-topic. Step 3: It determines urgency and what kind of intel the buyer needs right now versus later. Step 4: It sets triggers and monitors the web continuously, scanning blogs, news sites, and social posts for relevant information as it changes. Step 5: It sends the buyer an intelligent synthesized update with links and the ability to take action. Here is why this is a massive opportunity: AI Mode already has 1 billion monthly users. Queries are more than doubling every quarter. And multiple studies have shown that users arriving via AI search are more likely to convert. With information agents running continuously for over a billion users, the brands in that cited source pool are being recommended around the clock, automatically, to buyers who are actively monitoring their category. The brands that build content depth and editorial authority now are building a presence that buildings on itself 24 hours a day. This is what SEO Stuff builds for every customer. Content that covers every sub-question a buyer in your category asks, so the agent finds you at every step of its plan. Authority building from trusted websites that signal credibility to every retrieval system Google has ever built. One investment. Continuous recommendations. Around the clock. Check it out: Our most popular done-for-you package: Our done-for-you "content only" package: There is a reason more than 80 percent of SEO Stuff customers reorder. The results continue long after the work is done. #GoogleIO📷📷📷 #Google📷📷📷

Alex Groberman

157,952 次观看 • 1 个月前

How many AI agents work at your company? We now have over 3,258 agents working alongside 1,300 humans. The crazy part is these agents were created by EVERY EMPLOYEE at our company... sales reps, marketers, customer support, product, eng. Literally EVERYONE. BUT I'm most surprised by the adoption and value that MANAGERS are getting from agents. I used to think that every IC would become a manager of agents. Now I think that managers will very likely manage WAY more agents than their ICs combined. And managers' agents will manage their ICs' agents - overseeing them for human-in-the-loop interactions. When creating agents, we use 100% context from all of your activity, files edited, tasks and projects worked on, hierarchy, skills, and role information. We build a user-based context model to make agents as relatable as possible to the specific human that we're building for. This means they truly understand the nuances of the work and what "great" looks like - because great is very much in the eye of the beholder. Great is by definition, subjective. This is also why the human ENGAGEMENT loops are SO vital to agent value. The iteration AFTER the agent is onboarded is where the MAGIC happens. This is just like a manager managing an IC in real life... you're giving feedback. In this case, though, agents learn INSTANTLY, and they retain the knowledge perfectly and indefinitely. Even though I've been pushing AI for years now to everyone in our company, this was the first time we had truly end-to-end AI adoption and retention. This kind of AI adoption is wild. But the value we're realizing is truly INSANE. Super Agents outnumber our humans nearly 3 to 1. What if you could 3X your workforce overnight? Watch this video to see how 👇

Zeb Evans

425,244 次观看 • 5 个月前

Use this prompt in OpenClaw to create your own AI agent command center that syncs up your life like Tony Stark's Jarvis in Iron Man. Adapt the specifics (agent names, data sources, branding) below to your own setup. Prompt: Build me a mission control dashboard for my OpenClaw AI agent system. Stack: Next.js 15 (App Router) + Convex (real-time backend) + Tailwind CSS v4 + Framer Motion + ShadCN UI + Lucide icons. TypeScript throughout. This is the command center where I monitor and control my autonomous AI agent(s) running on OpenClaw. The agent operates 24/7 on a Mac Mini, connected to Telegram/Discord, running cron jobs, spawning sub-agents, and reading/writing to a filesystem-based memory and state system. Dark mode only. Ultra-premium aesthetic, think Iron Man's JARVIS HUD meets a Bloomberg terminal. Subtle glass effects (backdrop-blur-xl, bg-white/[0.03]), no heavy gradients or glow. Rounded corners (16-20px on cards). Framer Motion for page transitions, stagger animations on card grids, spring physics on interactions. Mobile-first responsive. Never cookie-cutter. ## Architecture The dashboard reads live data from TWO sources: 1. **Convex**: real-time database for structured data (tasks, contacts, content drafts, calendar events, activity logs) 2. **Local API routes** (`/api/*`): read files from the agent's workspace filesystem at `~/.openclaw/workspace/` and return JSON. This is how live system state flows into the dashboard. ## Pages & Views (8 nav items, some with tab sub-views) ### 1. HOME (`/`) Dashboard overview. Grid of live status cards: - **System Health**: read from `/api/system-state` (parses `state/servers.json`). Show each service with UP/DOWN indicator, port, last check time. - **Agent Status**: read from `/api/agents` (parses `agents/registry.json` + agent workspace files). Show active agent count, healthy/unhealthy ratio, active sub-agent count from OpenClaw sessions API. - **Cron Health**: read from `/api/cron-health` (parses `state/crons.json`). Table of all scheduled jobs with name, schedule, last status (green/red dot), consecutive errors. - **Revenue Tracker**: read from `/api/revenue` (parses `state/revenue.json`). Current revenue, monthly burn, net. - **Content Pipeline**: read from `/api/content-pipeline` (parses `content/queue.md`). Kanban-style: Draft | Review | Approved | Published counts. - **Quick Stats**: total tasks, pending approvals, active sessions, uptime. All panels auto-refresh every 15 seconds. Live indicator dot + "AUTO 15S" badge in header. ### 2. OPS (`/ops`) with 3 tabs: Operations | Tasks | Calendar **Operations tab:** Full operational view. Server health table, branch status (from `state/branch-check.json`), observations feed (from `state/observations.md`), system priorities (from `shared-context/priorities.md`). **Tasks tab:** Strategic task suggestion system. API route `/api/suggested-tasks` reads/writes `state/suggested-tasks.json`. Cards grouped by category (Revenue, Product, Community, Content, Operations, Clients, Trading, Brand) with emoji headers. Each card shows title, reasoning, next action, priority badge, effort badge, approve/reject buttons. Filter bar by status and category. **Calendar tab:** Weekly calendar view from Convex `calendarEvents` table. Drag-to-create, color-coded by type, time slots. ### 3. AGENTS (`/agents`) with 2 tabs: Agents | Models **Agents tab:** Card grid of all registered agents from `/api/agents`. Each card shows name, role, model, level (L1-L4), status. Cards are CLICKABLE: expanding into a detail panel showing: - Agent personality (reads their SOUL .md) - Capabilities and rules (reads their RULES .md) - Sub-agents they can spawn - Recent outputs (reads from `shared-context/agent-outputs/`) **Models tab:** Model inventory table showing all available models, their routing (which tasks go to which model), costs, and failover chains. ### 4. CHAT (`/chat`): 2 tabs: Chat | Command **Chat tab:** Chat interface to communicate with the agent. Left sidebar shows session list (from `/api/chat-history` reading .jsonl transcript files). Main area shows messages with role-aligned bubbles (user right, assistant left), date separators, channel badges (telegram/discord/webchat). Input bar with send button + voice input (Web Speech API with SpeechRecognition). Messages sent via `/api/chat-send` which queues to a file the agent reads. **Command tab:** Quick command interface for common operations. ### 5. CONTENT (`/content`) Content pipeline management. Read from Convex `contentDrafts` table AND `/api/content-pipeline`. Show drafts in kanban columns. Each card shows title, platform target, draft text preview, status, created date. Edit/approve/reject actions. ### 6. COMMS (`/comms`) with 2 tabs: Comms | CRM **Comms tab:** Communication hub showing recent Discord digest, Telegram messages, notification history. **CRM tab:** Client pipeline kanban (Prospect → Contacted → Meeting → Proposal → Active). API route `/api/clients` reads markdown files from `clients/` directory. Each card shows client name, status, contacts, last interaction, next action. ### 7. KNOWLEDGE (`/knowledge`) with 2 tabs: Knowledge | Ecosystem **Knowledge tab:** Searchable knowledge base. Global search across all workspace files using `/api/knowledge` endpoint. **Ecosystem tab:** Product grid showing all products/apps in the ecosystem. Each card shows product name, status (Active/Development/Concept), health indicator, key metrics. Cards link to `/ecosystem/[slug]` detail pages with tabbed views (Overview, Brand, Community, Content, Legal, Product, Website, Actions). Detail pages read from `/api/ecosystem/[slug]` which parses workspace memory files. ### 8. CODE (`/code`) Code pipeline view. Shows repositories from `/api/repos` (scans ~/Desktop/Projects/ for git repos). Each repo card shows name, branch, last commit, dirty file count, language breakdown. Detail view at `/api/repos/detail` shows recent commits, file tree, open PRs. ## Navigation Top horizontal nav bar, NOT sidebar. All 8 items visible at all viewport widths. Use `flex` layout with `flex-1` items. Text size uses `clamp(0.45rem, 0.75vw, 0.6875rem)` for fluid scaling. Active item gets `text-primary bg-primary/[0.06]` static highlight (no sliding animation). Agent/app name visible at md+ breakpoints (`hidden md:inline`). Tab sub-views use a reusable `TabBar` component with pill/glass styling and Framer Motion `layoutId` transitions. Tab state stored in URL via `?tab=` search params. ## API Routes (all under `src/app/api/`) Each API route reads from the agent's workspace filesystem and returns JSON: - `/api/system-state` → reads `state/servers.json`, `state/branch-check.json` - `/api/agents` → reads `agents/registry.json`, agent SOUL .md files - `/api/agents/[id]` → reads specific agent's SOUL .md, RULES .md, outputs - `/api/cron-health` → reads `state/crons.json` - `/api/revenue` → reads `state/revenue.json` - `/api/content-pipeline` → parses `content/queue.md` (markdown with status markers) - `/api/suggested-tasks` → GET (read) / POST (approve/reject) on `state/suggested-tasks.json` - `/api/observations` → reads `state/observations.md` - `/api/priorities` → reads `shared-context/priorities.md` - `/api/chat-history` → reads .jsonl transcript files with pagination/search/channel filter - `/api/chat-send` → writes to queue file - `/api/clients` → reads markdown files from `clients/` directory - `/api/ecosystem/[slug]` → reads memory files for specific ecosystem - `/api/repos` → scans project directories for git repos - `/api/health` → returns status, uptime, memory usage, Convex connectivity All filesystem paths should be configurable via environment variable (default: `~/.openclaw/workspace/`). ## Convex Schema Define tables for: activities, calendarEvents, tasks, contacts, contentDrafts, ecosystemProducts. Include seed scripts (`convex/seed.ts`) to populate initial data. ## Key Design Rules - Mobile-first, test at 320px minimum - Font sizes 10-14px for body text, everything must fit naturally at small viewports - Cards use consistent border radius (16-20px) - Glass cards: `bg-white/[0.03] backdrop-blur-xl border border-white/[0.06]` - No heavy blur blobs or grain overlays - Stagger animations on card grids (0.05s delay per item) - Skeleton loading states for all async data - Custom scrollbar styling - Empty states with helpful messaging - All text must use Inter or system font stack - Never mix sharp and rounded corners in the same view - Premium = lighter feel, more whitespace, less visual noise ## File Structure ``` src/ app/ page.tsx, layout.tsx, providers.tsx agents/page.tsx calendar/page.tsx chat/page.tsx code/page.tsx comms/page.tsx content/page.tsx ecosystem/page.tsx, ecosystem/[slug]/page.tsx knowledge/page.tsx ops/page.tsx api/[...all routes above] components/ nav.tsx tab-bar.tsx dashboard-overview.tsx ops-view.tsx, suggested-tasks-view.tsx agents-view.tsx, models-view.tsx chat-center-view.tsx, voice-input.tsx content-view.tsx comms-view.tsx, crm-view.tsx knowledge-base.tsx, ecosystem-view.tsx code-pipeline.tsx activity-feed.tsx, calendar-view.tsx ui/ (ShadCN primitives) hooks/ lib/ convex/ schema.ts functions for each table seed.ts ``` Build the complete application. Every component, every API route, every Convex function. Production-quality code and premium design, not stubs. Dark mode only. Make it look incredibly beautiful and premium, no cookie cutter UI / AI slop.

klöss

201,167 次观看 • 5 个月前

"The future of AI is agentic. That includes browsers!" Imagine having an AI agent in your browser that can help you complete complex tasks, answer your questions, and streamline your workflow. Today I'm thrilled to share a sneak peek at Project Mariner, a cutting-edge research collaboration between Chrome and Google DeepMind, exploring the future of agentic AI within the browser! Building on the power of Gemini 2.0, Mariner envisions AI agents seamlessly guiding users through online tasks, streamlining workflows and enriching browsing experiences. Imagine having an intelligent co-pilot in your browser, anticipating your needs and proactively offering assistance. We're in the early stages of experimentation, focusing on core functionalities like understanding user intent, automating actions, and providing personalized recommendations. This prototype leverages Gemini's advanced natural language understanding and reasoning capabilities to interpret user requests, both typed and spoken. Mariner can then interact with web pages, retrieve information, and even perform actions like filling out forms or navigating to specific sites. For example, a user could simply ask "Find me a job near me," and Mariner would understand the request, navigate to a relevant job search site, and tailor the search based on the user's location and preferences. This is just one example of how we're exploring Gemini 2.0's potential to unlock agentic experiences through a series of prototypes, including: 1. Agents with multimodal reasoning: Project Astra, our research prototype exploring the capabilities of a universal AI assistant, is enhanced by Gemini 2.0. 2. Agents that can help you accomplish complex tasks: Project Mariner itself focuses on the future of human-agent interaction within the browser. 3. Agents for developers: Jules is an experimental AI-powered coding agent that integrates directly into a GitHub workflow. 4. Agents applied across domains: We're exploring agents for navigating video games and even applying Gemini 2.0's spatial reasoning to robotics. We believe that integrating AI agents directly into the browser has the potential to revolutionize how we interact with the web. Project Mariner aims to make browsing more intuitive, efficient, and personalized. By understanding user context and proactively offering assistance, Mariner can simplify complex tasks, save users time, and empower them to achieve more online. This aligns perfectly with the vision of Gemini 2.0 to create more helpful and intuitive AI experiences. We’re currently testing Mariner with a small group of trusted users to gather feedback and refine the user experience. We believe that this technology holds immense potential to transform the way we browse and interact with information online.

Addy Osmani

29,501 次观看 • 1 年前

how to use firecrawl to give your AI eyes and actually build startups that outperform 99% of apps: 1. your AI is smart but blind. it can't go to a website, read a page, or grab data on its own. firecrawl fixes that. you put in a URL. you get back clean markdown, structured JSON, screenshots. feed it to any model. 2. three lines of code. that's it. no proxies. no anti-bot detection. no custom scrapers that break when a site changes. one API call. clean data back in seconds. works on 98%+ of sites. 3. firecrawl has six core capabilities: scrape a single page. crawl an entire site. map all URLs on a domain. search google and return full content. an agent endpoint where you describe what you want and it goes and finds it. and a browser sandbox where AI controls a real browser like filling forms, clicking buttons, handles logins. 4. the agent endpoint is wild. you can say "find all of YC's winter 24 dev tool companies and their founders and emails" and get back structured data. or "compare pricing tiers across stripe, square, and paypal" and get a side-by-side table. 5. the browser sandbox lets your AI stay logged in across sessions, navigate pagination, watch live as it browses. this is computer use without building the infrastructure yourself. 6. think of it in layers. every builder needs: an agent harness (claude code, cursor, codex), a search layer (perplexity, exa), a web data layer (firecrawl), an ops brain (obsidian, notion), and an outbound stack. the web data layer is the one most people are sleeping on. 7. this is the AWS moment for web data. in 2006 building a web app meant buying servers and managing racks. AWS said one API call, use our servers. some of the biggest companies of the last decade were built on that. firecrawl is doing the same thing for web data in 2026. 8. the framework i'd use for coming up with startup ideas building with clean data: take a massive horizontal platform. rebuild it for one niche using firecrawl. the vertical version always wins because people want specific, not generic. price for outcome. 9. a year ago firecrawl posted a job listing that said "please only apply if you're an AI agent." content creator agents. customer support agents. junior dev agents. it looked weird. it was a signal for where this is all going. the people who understand how to get clean web data, wrap it around an LLM, and package it as a product are the the ones with a 12-month head start. i use Firecrawl with Idea Browser . once you see what's possible with structured web data, you can't unsee it. episode is live on The Startup Ideas Podcast (SIP) 🧃 (full breakdown there) i tried to explain this as clear as possible for even the non technical. send it to a builder friend. watch

GREG ISENBERG

134,714 次观看 • 3 个月前

10 repos that cut your ai agent token bill by up to 80% 1. microsoft/LLMLingua → cuts prompt size by up to 95% compresses prompts before the api call. 20x compression. published at EMNLP + ACL. near-zero quality loss. 6,100 stars 2. mem0ai/mem0 → replaces full conversation history in context stores what matters. retrieves only what's needed. 10,000 token history → 200 token memory. per agent. 54,800 stars 3. BerriAI/litellm → routes each call to the cheapest model simple task → haiku. complex task → sonnet. tracks cost per agent, per call, per day. 45,700 stars 4. run-llama/llama_index → replaces sending full documents rag: 100-page doc → 3 relevant chunks → same answer. 98% fewer tokens per query. 49,100 stars 5. chroma-core/chroma → replaces keyword search in full context vector store. finds the closest match. feeds only that. 50-200 tokens per query instead of thousands. 27,800 stars 6. letta-ai/letta → replaces infinite context window crashes paged memory for agents. loads only relevant memory. stops your agent from hitting limits and retrying. 22,400 stars 7. guidance-ai/guidance → cuts output token bloat by 30-50% structured generation. constrains model output natively. no more 100-token prompts to get json back. 21,400 stars 8. Aider-AI/aider → replaces pasting entire codebases builds a repo map. sends only files relevant to the task. not your whole project. just what the agent needs. 44,300 stars 9. openai/tiktoken → count tokens before you send know the exact cost before the api call happens. not after the bill arrives. 18,100 stars 10. simonw/ttok → hard cap on what gets sent cli tool: count tokens, truncate to budget limit. pipe any text in. get truncated output back. 389 stars most agents are expensive not because the model is expensive. because nobody checked what was being sent to it.

self.dll

39,370 次观看 • 2 个月前