Loading video...

Video Failed to Load

Go Home

BREAKING: SpaceXAI just released a new update for Grok Build, v1.0.46 This update brings faster startup, fewer delays on network drives and clearer progress updates. It also fixes MCP reporting, tool-search summaries, rule handling, token counts and video playback. Performance • list_dir on network or virtual filesystems now skips...

41,206 views • 12 days ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

BREAKING: SpaceXAI has released a major new update for Grok Build (v1.0.13). The update improves reliability with automatic retries and recovery from truncated responses, inference failures, oversized images and session-saving issues. It also adds smarter hooks, better Windows support, faster MCP and session startup, improved scheduled tasks and quicker compressed CLI downloads. Features • Length-truncated responses now continue automatically instead of failing the turn. • Hooks can now ask the user to confirm a tool call instead of always allowing or denying. • Hooks can now request deferral or add context shown to the model after a tool runs. • Session close now records detailed timing data for performance analysis. • Credit limit upsell now offers a Try Again button to retry the last prompt. • Pasted images now show a live pixel preview in the prompt box on iTerm2. Bug Fixes • Transient inference failures (stalls, drops, 5xx) now retry automatically instead of ending the turn. • Windows users can now correctly open ~/.grok and worktree sessions. • Session data is now more reliably saved after prompts and on power loss. • Compaction failures now show the actual error instead of a generic message. • Truncation error messages now show the right guidance instead of suggesting an unhelpful retry. • Truncated tool calls are now executed instead of failing the turn when arguments are complete. • Images larger than 2000px no longer brick sessions on many-image requests. • Wrapped hyperlinks in the pager now remain fully clickable on Windows Terminal instead of only the first line. • Recurring scheduled tasks now include a reminder to stop the monitor when work finishes. • Scheduled task IDs are now full UUID strings, preventing collisions when tasks are created in the same millisecond. Performance • Subagent spawning is faster when connections drop during bursts. • Session startup with MCP servers is now much faster when auth is already configured. • MCP server startup no longer stalls behind a fixed batch size. • CLI downloads are now compressed, making fresh installs and updates substantially faster. Download Grok Build: Update to the latest Alpha release: grok update --alpha Update to the latest Stable release: grok update

DogeDesigner

490,415 views • 1 month ago

BREAKING: SpaceXAI has released a major new update for Grok Build (v1.0.14) Grok v1.0.14 is a reliability and workflow update for the Grok CLI. It makes OIDC token refresh proactive, lets PostToolUse hooks send feedback back to the model after tools run, adds per-turn token and cost tracking via grok usage, and cuts Windows downloads by about 70%, with a large set of fixes that tighten sandboxing, subagent handling, hooks, and startup. Features: • OIDC token refresh is now proactive by default for better reliability. • PostToolUse hooks can now provide feedback and context to the model after tool execution. • SDK-registered PostToolUse hooks now provide model-facing feedback. • grok usage now shows persisted per-turn token and cost data. • Retry status in composer and title now shows a short reason for the retry. • Models can now declare a different identifier for each reasoning-effort level instead of always sending the same id. • Prompt suggestions now respect remote configuration and default to the current session model. • Windows CLI downloads are now ~70% smaller using the same compressed sidecars as macOS and Linux. Bug Fixes: • grok inspect now correctly shows Claude bypass locks as advisory rather than enforced. • Subagent sessions no longer leak threads or file descriptors when the parent is busy. • Cold startup no longer performs duplicate remote settings fetches. • Compaction failures due to context size now degrade input instead of retrying identically. • --sandbox strict now restricts writes to ~/.grok/sessions only. • Subagent spawning now waits longer on a busy coordinator and shows clearer retry guidance instead of "unreachable". • Failed task and todo tool calls now appear in the transcript instead of disappearing without a trace. • Composer status row no longer collapses or flashes when using double-Enter to send now. • Session close is no longer delayed by a single slow hook; each SessionEnd hook now has its own timeout. • Hook removal in the extensions modal no longer offers actions that the handler will refuse. • Interjections during a turn are now delivered atomically or not at all. • Subagent tasks no longer get incorrectly cancelled when the parent session is waiting for completion. • Workflow detail view now closes the overlay on X or outside click instead of returning to the run list. • Resuming subagents now succeeds for larger transcripts that still fit the model context with headroom. Performance: • Startup now fetches remote settings only once per boot instead of potentially twice. • First message on large repositories no longer waits on repository status scan. • Large session memory no longer blocks the agent during turn completion or subagent spawning. • Signed-in CLI starts faster by serving remote settings from a local cache on warm boots. Download Grok Build: Update to the latest Alpha release: grok update --alpha Update to the latest Stable release: grok update

DogeDesigner

52,568 views • 1 month ago

BREAKING: SpaceXAI has released another major new update for Grok Build (v1.0.22) This update is focused on smoother workflows, better safety and improved reliability. It adds stronger desktop and MCP integration, clearer file-edit previews, a redesigned dashboard and better subagent support. It also fixes problems with sessions, skills, authentication and background commands while making sessions faster to open and resume. Features Built-in agent tools now take precedence over user MCP servers when tool names collide. Desktop app tools are now available through a dedicated first-party MCP server. Remote control pickers can now group servers by device using announced device identity. edit_file diffs now show real file line numbers instead of starting at line 1. Permission prompts for file edits now auto-expand the diff row so you can see the change before approving. Sending a message to a finished subagent now continues that same subagent instead of failing. Background subagent completion messages now show the actual output instead of just a pointer to run the tool. Dashboard now shows a unified header with a location picker and an actions row for creating agents or resuming previous sessions. New grok-workspaced daemon mode lets a long-lived process expose folders to the Computer Hub, separate from the Desktop-supervised sidecar. Bug Fixes MCP connectors now correctly show when they need re-authentication, even if no tools are listed. Extensions modal shortcuts now work when the tab bar is focused, and invalid actions on headers show helpful messages. The Send now button and shortcuts now work correctly when an automatic background turn is running. Resumed sessions now show the exact text you typed for mid-turn follow-ups instead of the wrapped system message. The /skills command now updates the model with newly installed skills, even when written from another NFS client. Auto mode no longer instantly runs destructive git checkout -- commands; they now go through the model for safety. Fixed a crash that could occur when restoring pasted content after certain skill injections or rewinds. Subagents and workflows now respect the same bash timeout and auto-background settings configured for the parent session. Fixed model backend selection so an explicit chat_completions setting in config.toml is no longer overwritten by same-slug siblings. Slash command advertisements no longer spam repeatedly when your current directory is your home folder. Foreground shell commands no longer produce spurious background-task reminders or incorrect kill results. Queued follow-up buttons now appear in the order [Send now][edit][Cancel]. /compact instructions in the pager are now passed to the compaction backend. Bare /compact is unchanged. /goal, and resume after pressing Esc, now correctly starts the goal planner instead of failing with “Planning failed.” run_terminal_cmd now correctly tells the model that foreground commands are backgrounded after approximately 15 seconds instead of the 120-second timeout value. Skill announcements no longer repeat the same list of available skills multiple times in a session. Monitor events in multi-session processes now correctly wake idle sessions instead of being buffered until the next prompt. Performance Opening or resuming sessions no longer pauses the interface while reading MCP configuration files. Download Grok Build: Update to the latest Alpha release: grok update --alpha Update to the latest Stable release: grok update

DogeDesigner

62,365 views • 1 month ago

SpaceXAI just released a new update for Grok Build. Update to v1.0.11 Features: • Headless sessions are now browsable in the resume picker without mixing into default history. • Default permission mode for new interactive sessions is now configurable. • Turn duration now appears in session history after resume. • Turn footers (Worked for, cancelled, failed) now appear after /resume. • mkdir and touch no longer prompt in auto mode or safe-command lists. • Subagent messages are now allowed automatically in permission Auto mode. • Headless sessions can now auto-allow permission prompts via a startup hint. Bug Fixes: • Permission prompts for common command chains and subcommands are now more reliable. • Blocked prompts no longer appear in conversation history or scrollback after restart. • Background monitors no longer have a 10-hour default timeout. • Mouse input at the right margin no longer types characters into the prompt on certain terminals. • Pasting text ending in a newline no longer accidentally submits the prompt on some terminals. • Auto mode now shows a permission card when the classifier blocks an action on interactive sessions. • Image previews no longer leave ghost artifacts when using the Kitty protocol on Warp. • Expanded Execute tool output no longer snaps closed during live progress. • /voice now falls back to parec/arecord on older PipeWire installs. Performance: • Background command waits now finish as soon as the process exits. Download Grok Build: Update to the latest Alpha release: grok update --alpha Update to the latest Stable release: grok update

DogeDesigner

49,666 views • 1 month ago

BREAKING: SpaceXAI just released a major Grok Build update, with Grok 4.7 now available in Grok Build. The update improves crash recovery, prompt handling, navigation, configuration reliability and overall subagent performance. It also adds new subagent controls, configurable request limits and long-reasoning reminders. Release Notes Version 1.0.41 — September 22, 2026 Features • Added a new sports_search tool that can look up live NFL scores, standings, schedules, player stats and team records directly from X data. • Added a subagent model inheritance setting to /settings. It persists in config.toml and respects managed and overlay layers. • Per-model request size limits can now be configured to match provider HTTP body caps and control inline image eviction. • A long-reasoning reminder can now be enabled through config to nudge the model after lengthy hidden-reasoning steps. Bug Fixes • Fixed the subagent fullscreen view so it no longer shows a stray [Dashboard] button in the header. • Fixed agent frontmatter mcpServers so headers and URLs from the active agent’s agent.md correctly override config.toml and survive config reloads or agent switches. • Ctrl+P now opens the command palette immediately from the welcome screen. • The Dashboard now focuses the “+ New Agent” row instead of leaving the previous session selected. • Sessions interrupted by a crash now show a clear marker instead of silently dropping the turn. • Pressing Ctrl+Z immediately after stashing a prompt now restores it. • The collapsed edit blocks setting now correctly collapses edits even when expanded_by_default is pinned to true. • Interjections now receive a visible reply before the agent resumes its previous tasks. • Cancelling a turn blocked on spawn_subagent now tells the model that the child moved to the background instead of claiming it was never executed. • Saving a queued-prompt edit now returns focus to the composer so the next keystrokes type the next message. • Subagent activation is now consistent between the TUI and Grok Agent Studio. Tables that only set limits or models no longer disable subagents. • Effort-level selection now accepts menu labels in addition to IDs.

DogeDesigner

427,277 views • 20 days ago

Build AI agents on a time-aware knowledge graph! Utopia is an open-source knowledge system that turns documents, databases, and connected sources into a temporal graph your agents can reason over. Most RAG systems are optimized for one question: what is relevant right now? That works until the underlying knowledge changes. A customer contract gets updated. A project owner changes. A policy is revised. A previous fact may no longer be true, but simply overwriting it means the system loses the history behind that change. Utopia handles this with a bitemporal knowledge graph. Each fact can track both when it was true in the real world and when the system learned about it. When something changes, the old fact is preserved instead of silently disappearing. That means an agent can reason about questions like: • What is true now? • What was true three months ago? • When did this information change? • What evidence was the conclusion based on? The graph is also ontology-aware, so documents are represented as entities, facts, and relationships instead of only chunks and embeddings. That gives the system more structure for reasoning across relationships, resolving entities, detecting conflicting facts, and deriving new information through explicit rules. Key capabilities: • Bitemporal knowledge graph for tracking how facts change over time • Provenance on facts so agents can trace where information came from • Conflict detection instead of silently overwriting contradictory information • Ontology-based reasoning across entities, relationships, and derived facts • Hybrid retrieval across full-text search, vector search, and graph traversal • MCP and agentic RAG support for exposing the knowledge layer directly to agents The interesting part is that this turns the knowledge base into more than a retrieval system. Instead of only finding relevant information, an agent can reason over what changed, what is still valid, how facts are connected, and where each conclusion came from. 100% open source. I've shared the GitHub repo in the comments!

Sumanth

16,653 views • 1 month ago

Dune analytics MCP.. Claude becomes your on chain SQL analyst.. No dashboard has every query you'll ever need. dune does but writing SQL is a skill, and most of you would skip it.. i know this MCP fixes that. Claude writes the query, runs it on dune, and explains what the data actually means. with this MCP wired in, you don't need to know SQL. you describe what you want in plain english and Claude does the rest. like "Claude, which wallets bought $RAVE in last few weeks and still hold?" "Claude, show me the top 50 ETH wallets by stablecoin inflows last 7 days." "Claude, what's the median gas paid by ARB users in the last 24h?" Questions no dashboard can answer. one prompt away.. Setup (3 minutes) ▫️Step 1: grab a free dune API key → ▫️Step 2: add this to ~/.claude/settings.json or .mcp.json: { "mcpServers": { "dune": { "command": "npx", "args": ["-y", "dune-analytics-mcp"], "env": { "DUNE_API_KEY": "your-key-here" } } } } ▫️Step 3: restart claude. you'll see the dune tool load in your tool menu. that's it. you now have onchain SQL on tap. How to actually use it: 3 prompts i use: 1) Smart money watchlist: "claude, pull the top 20 wallets by realized pnl on $TOKEN in the last 30 days. show me which ones are still holding." gives you a clean leaderboard of who's actually winning on that token. add them to your etherscan watchlist. 2) accumulation vs distribution "claude, compare net inflows vs outflows for $TOKEN across all CEX wallets in the last 14 days." if whales are moving off exchanges → accumulation. onto exchanges → distribution. you see the rotation before the candle. 3) narrative heat check "claude, which 10 tokens saw the biggest % increase in unique new holders this week?" finds where fresh money is flowing. before this MCP i'd either, pay for a pro dune account + write queries manually, or look at someone else's dashboard and hope it answers my question… now claude writes it for me, in seconds, custom to my thesis. no dashboard in existence beats that. free tier covers most of what you need. upgrade if you're querying heavy. ( built a quick $RAVE post mortem dashboard using a prompt as shown in the video ) MORE SUCH USEFUL MCP for traders below.. 👇

Axel Bitblaze 🪓

32,016 views • 5 months ago

The Visual Studio Code insiders version that just shipped and will ship in the next few days will come with an insane amount of new capabilities. A few highlights: - You can now run sub-agents in parallel. Yes, really. I even attached a video. - Major UX improvements for sub agents, especially visible in the chat window - A new search tool wrapped as a sub-agent that iteratively runs multiple search tools: semantic_search, file_search, grep_search Which connects nicely to the point above: multiple searches running in parallel, efficiently and fast - Anthropic’s Message API is now enabled by default - You can choose the model for the cloud agent (three available, all premium) - Extended thinking support when using the Claude cloud agent This is part of the broader multi-vendor cloud support under AgentsHQ I wrote about a few weeks ago - Tasks sent to the background agent (basically the CLI tool) now always run in isolation, each with its own git worktree - In a multi-repo workspace, assigning a task to a cloud agent prompts you to choose the target repo Same behavior when opening an empty workspace with no repo - Support for building an external index for files not supported by GitHub’s default indexing - UI/UX improvements for starting new sessions and switching between local / background / cloud agents - Skills are now first-class citizens, just like prompt files, with better UX indicating when a skill is loaded - Improved API for dynamic contribution of prompt files New V2 includes skills as part of the model. Curious to see the extensions that will leverage this - Finally, initial support for showing context usage percentage per session - Skills are enabled by default - Resizable chat window and session view. Small thing, but it was driving me crazy 😁 - A new integrated browser meant to replace the old simple browser Maybe the beginning of real browser use? - Better UI/UX for token streaming in chat - Ability to index external files not supported by GitHub There’s a lot more. Some of it hasn’t fully landed yet, but everything that has is already in Insiders. The next stable release should drop in early February. As usual, I’m just shocked by the volume of features this team ships every month. After the holiday slowdown, this one is shaping up to be a wild release.

Oren Melamed

29,555 views • 9 months ago

After a few more hours, I think I've figured out Opus 5. Opus 5 is trained to be more agentic than anything I've used. All Claude 5 models are like that. So what changes? The way to interact with Opus 5 or contextualize it won't work the same way as with other models. It loves exploring, so it doesn't need much guidance for it. Unique preferences, artifacts, and references compliment it well and enable cleaner and more effective exploration and execution. Now that it can explore more effectively on its own and understand intent better, the best thing to do is to get out of its way (e.g., it doesn't need examples of your preferences; a clear high-level description of it works best). It's truly agentic in that sense. A good first step to provide better context for Opus 5 is to distinguish between what's situational and what needs persistence. Regardless, persistent system prompts and CLAUDE.MD needs to stay lightweight. Remove memories and tool descriptions from these. CLAUDE.MD is also a great place to tap into progressive disclosure by linking command/skills to it. On the situational side, agent skills and auto-memory can leverage progressive disclosure and the improved ability of the model to use its external context/knowledge. Conflicting and unnecessary instructions, which are common at this layer (mainly to ensure reliability), are going to throw off this model easily. That's the biggest change I had to make. Simple, clean, and clear prompts and skills work best. I had to clean a lot of my skills and system prompts. The way I prompt remains the same (usually clear and well-scoped). MCP tool descriptions are also more descriptive and have been deduped from the system prompt. Anthropic released a guide on the new rules for context engineering, which was helpful here. I started to test the recommendations and created a little artifact with the things that worked along the way. This might feel like a lot of work. Believe me, it has been frustrating. But I think we can expect future frontier models to become more agentic and smarter at figuring out the right context/gaps. The best thing to do is to prepare for that now. Boris Cherny mentioned that Opus 5 is their least prompt-injectable model yet. I am not sure if that was something they intentionally trained for or if it emerged based on how it was trained, which is to be extremely agentic in nature and more direct in execution.

elvis

37,824 views • 2 months ago

There’s a reason the LimeWire name still hits people instantly. If you were around in the early internet days, LimeWire was everywhere. Music discovery, file sharing, chaos, excitement. It shaped how a whole generation interacted with the web. That kind of brand memory doesn’t fade and LimeWire is proving it can be reused in a serious way. What’s different now is the foundation. LimeWire Network is the decentralized storage layer of LimeWire, built on BNB Chain. It is not a nostalgia project. It is infrastructure. Storage, transfers, and usage are happening on chain, designed to scale for real applications rather than demos. The growth backs that up. Looking at recent data on lmwrscan, LimeWire Network has already moved into tens of terabytes of stored data, with tens of thousands of uploads and consistent daily activity. Network usage keeps climbing, not spiking once and disappearing. That kind of curve usually shows real users, not incentive farming. And the economics are clear. The $LMWR token sits at the center of the system. Users pay in LMWR to use storage. Node operators earn LMWR for providing resources. Rewards and payments stay inside the ecosystem instead of leaking out to third parties. That loop matters. Most decentralized storage networks struggle because nobody knows they exist. LimeWire doesn’t have that problem. The brand alone opens doors, pulls attention, and lowers the friction for new users to try the product. When you combine that with live usage data and a functioning token economy, the upside starts to look asymmetric. Built on BNB Chain, LimeWire Network also gets the scalability needed if adoption keeps accelerating. That choice signals intent to grow, not just experiment. This feels like a rare case where nostalgia is not the product, it is the distribution layer. Curious how you see it. Are you watching LimeWire because of the brand comeback, the LimeWire Network growth, or the role of the LMWR token in the long run?

ryu 龙

25,416 views • 8 months ago