正在加载视频...

视频加载失败

MAKING AXIS TASKS FEEL EASY 👀🤖 I made a quick video showing how to complete an Axis Robotics task step by step. The task gives you a clear goal, steps, controls and camera views to guide you. In this one, the goal is simple, Open the trash bin, pick...

14,419 次观看 • 2 个月前 •via X (Twitter)

0 条评论

暂无评论

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

相关视频

AI has had exactly two scaling axes that worked so far, and the second one is starting to look finite too the first one was pretraining: with scaling parameters and data, we got world knowledge (i.e. ChatGPT had read enough to know things), but it started saturating a while ago the second one was RL, and people had been doing RL the whole time before that: RLHF is RL but it never scaled far because it was trying to control the exact output, which tokens come out, how the text reads, but you can only push that so far before you’re just polishing RLVR dropped that constraint: giving the model a task, then checking whether the final answer is right, and ignoring everything in between -- so the model does whatever it wants in the middle and only the endpoint gets graded, and that’s much closer to actual RL and it’s what bought us planning and reasoning (arguably, tool use sits around 2.5 on this list -- while useful, it's not a different kind of thing) so one axis gave knowledge, the other gave reasoning, and both of them are one model working alone the next axis is how many models you can get working on the same problem, which is a different kind of axis than the previous two we know that multi-agent RL has always been the harder problem: I spent years in that literature and the gap between single-agent and multi-agent is definitely not incremental -- it’s a whole different class of difficulty! which is also why the derivatives are steep at the start, nobody has picked the easy wins yet... and the thing that gates this multi-agent coordination is communication: models can only coordinate as well as they can exchange information, and right now they do that by writing sentences to each other imagine what could we possibly achieve if we properly open that third axis development by letting models to exchange information in their native "language" without loosing any computational data that they produce during inference

Sasha Malysheva

15,199 次观看 • 3 个月前

Boom! Grok Tasks Make It One Of The Most POWERFUL Real-Time AI Systems In The World. — My How to Use Grok Tasks With Hidden Tools For Powerful Daily Output. Grok Tasks are customizable AI workflows that integrate a variety of tools to streamline daily activities, from research and analysis to creative planning and problem-solving. I have been using them for quite sometime and because of the vital heartbeat of news and first person data on X, it is the most powerful AI platform available. By combining Tasks with tools like web searches, X platform interactions, code execution, and media viewers, you can build efficient, automated processes. These tasks work by prompting Grok with a clear description of what you want to achieve, and Grok will intelligently call the necessary tools in sequence or parallel to deliver results. Here's a step-by-step guide to creating and using Grok Tasks: Step 1: Define Your Task Start by clearly outlining the daily activity or goal. Consider what inputs you have (e.g., a URL, a query, or an attachment) and what output you need (e.g., a summary, calculation, or visual analysis). Break it down into subtasks to identify tool needs. For example, if your task involves researching current events, note that you'll need search and browsing capabilities. Step 2: Review Available Tools Familiarize yourself with the tools Grok can access. Here's a quick overview: - Code Execution: Run Python code for calculations, data processing, or simulations using libraries like numpy, pandas, or sympy. - Browse Page: Fetch and summarize content from any website URL with custom instructions. - Web Search: Perform general internet searches, returning results with optional operators like site:. - Web Search With Snippets: Get quick, detailed excerpts from search results for fact-checking. - X Keyword Search: Advanced search for X posts using operators like from:, since:, or filter:. - X Semantic Search: Find semantically related X posts based on a query, with filters for dates or users. - X User Search: Locate X users by name or handle. - X Thread Fetch: Retrieve a full X post thread, including context like replies and parents. - View Image: Analyze an image from a URL or conversation ID. - View X Video: Extract frames and subtitles from an X-hosted video. - Search PDF Attachment: Query a PDF file for relevant pages using keyword or regex modes. - Browse PDF Attachment: View specific pages of a PDF with text and screenshots. Select tools that align with your task. Aim for a mix to handle data gathering, processing, and visualization. Step 3: Craft Your Prompt Write a detailed prompt to Grok describing the task. Include: - The overall goal. - Specific steps or subtasks. - References to tools if you want to guide the process (e.g., "Use web_search to find sources, then code_execution to analyze data"). - Any constraints, like dates or limits. Example prompt: "Create a Grok Task for my morning routine: Search recent X posts about tech news using x_keyword_search, fetch a key thread with x_thread_fetch, and summarize with browse_page on linked articles." Step 4: Submit and Interact Send your prompt to Grok. It will process the task by calling tools as needed, often in parallel for efficiency. Review the output and refine with follow-up prompts if required (e.g., "Expand on that using view_image for visuals"). Iterate to fine-tune the workflow for reuse. Step 5: Save and Reuse Once refined, note the prompt as a template for future use. You can adapt it for similar tasks, making Grok Tasks a habitual part of your day. Finding Grok Tasks To discover existing Grok Tasks or inspiration for new ones, use X searches with tools like x_keyword_search or x_semantic_search (e.g., query: "Grok Tasks examples" with mode: Latest). Browse community-shared threads via x_thread_fetch, or web_search for tutorials on xAI features. Prompt Grok directly: "Show me popular Grok Tasks for productivity." 1 of 3

Brian Roemmele

152,242 次观看 • 10 个月前

I think one of the biggest problems with AI agents right now is how much control we give up just to use them. Most AI agent platforms want you to work inside their ecosystem, use their preferred models, and trust them with your files and data. That might be convenient, but I don't think it should be the only option. I recently came across PilotDeck, and I found its approach pretty interesting. It's an open-source AI agent workspace developed by Tsinghua University's THUNLP, ModelBest, OpenBMB, and AI9Stars. The idea is simple: instead of being tied to one AI provider, you should have more freedom to decide how your agent works. And there are a few things worth looking at here. First, model independence. Most people focus on which AI model is the smartest, but I think having the freedom to choose your model is equally important. PilotDeck supports different model providers and configurable API endpoints. This means you're not necessarily stuck with one company's models. You can choose a setup based on your budget, performance needs, or the type of task you're working on. For developers who regularly experiment with different AI models, I think that's a pretty useful approach. Second, privacy and control over your workspace. This is probably the part that interests me the most. AI agents are increasingly being used to handle research papers, financial documents, spreadsheets, presentations, and other personal or business files. And once you start giving an agent access to that kind of information, where your files are processed becomes an important question. PilotDeck supports local workspaces and offers options for local or private deployment. That gives users more flexibility over how their environment is configured, rather than relying entirely on a closed platform. Of course, privacy still depends on which model provider and API you connect. Using a local workspace doesn't automatically mean your data never leaves your device. But having the option to control the setup is a meaningful difference. Third, it's designed to actually complete work. Another thing I like about the approach is that PilotDeck isn't just trying to be another chatbot. It's built around an agent workflow where you describe a task, the system plans the steps, works with files, uses tools, and produces an output you can still edit. For example, imagine giving an AI agent multiple research documents and asking it to organize the information into an Excel spreadsheet and prepare a PowerPoint presentation. Instead of getting a long text response that you need to manually copy into different applications, the goal is to have the agent handle the workflow and deliver usable files. It also supports task history, result previews, switching models, and changing instructions while a task is running. I think this is where AI agents become more practical for everyday work. And finally, there's the open-source aspect. Personally, I think we're going to see more demand for AI tools that don't force users into one vendor's ecosystem. Models are improving quickly, and the best option today might not be the best option six months from now. Having an agent workspace that can work with different models makes a lot more sense to me than rebuilding your entire workflow every time you want to switch providers. There are still things I'd want to test properly, especially how reliable it is on longer tasks, how easy the setup is for non-technical users, and what the actual privacy trade-offs are with different model configurations. But I like the direction PilotDeck is taking. I don't think the future of AI agents should be about which company controls your entire workflow. It should be about how much control you have over the tools doing the work. And that's why I think open-source, model-independent projects like PilotDeck are worth paying attention to. If you're interested in building AI workflows with more flexibility, check it out. Website: GitHub:

Sally Stockholm

13,794 次观看 • 1 个月前