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

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

На главную

BREAKING: SpaceXAI has released another major new update for Grok Build (v1.0.19) This update improves background task handling, adds transparent terminal themes, worktree support for headless sessions, and better session/dashboard controls. It also fixes UI freezes, crashes, feedback issues, clickable URLs, and makes the first prompt after login faster....

cb_doge's profile picture

DogeDesigner

1,900,726 subscribers

432,752 просмотров • 5 дней назад •via X (Twitter)

Наука и технологииНовости и политика
LIVE

Anya Rossi• Live Now

Private livecam show

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

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

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

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
0:13

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

47,710 просмотров • 14 дней назад

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
0:12

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

485,457 просмотров • 12 дней назад

BREAKING: SpaceXAI has released another major new update for Grok Build (v1.0.15) v1.0.15 makes Grok Bot faster and smoother. Sessions now open and close faster, first replies arrive sooner, typed input is handled better, and new tips make copying or exporting content easier. Features • Tip appears after repeated scrollback drag-copies suggesting /copy and /export commands. Bug Fixes • Session close is now faster because memory consolidation runs at the next launch instead of blocking exit. • Typed input including Enter during pager startup is now preserved and correctly interpreted as submit or newline. • Dock panel input and rollout now respect remote settings and correctly handle keyboard focus when hidden or empty. Performance • First reply latency is reduced by opening the model connection in the background when a session starts. • Signed-in startup is faster because an expired token refresh now begins in the background at agent spawn. • Creating a new session returns faster; MCP tools and other startup work happen in the background. Download Grok Build: Update to the latest Alpha release: grok update --alpha Update to the latest Stable release: grok update
0:13

BREAKING: SpaceXAI has released another major new update for Grok Build (v1.0.15) v1.0.15 makes Grok Bot faster and smoother. Sessions now open and close faster, first replies arrive sooner, typed input is handled better, and new tips make copying or exporting content easier. Features • Tip appears after repeated scrollback drag-copies suggesting /copy and /export commands. Bug Fixes • Session close is now faster because memory consolidation runs at the next launch instead of blocking exit. • Typed input including Enter during pager startup is now preserved and correctly interpreted as submit or newline. • Dock panel input and rollout now respect remote settings and correctly handle keyboard focus when hidden or empty. Performance • First reply latency is reduced by opening the model connection in the background when a session starts. • Signed-in startup is faster because an expired token refresh now begins in the background at agent spawn. • Creating a new session returns faster; MCP tools and other startup work happen in the background. Download Grok Build: Update to the latest Alpha release: grok update --alpha Update to the latest Stable release: grok update

DogeDesigner

50,270 просмотров • 9 дней назад

BREAKING: SpaceXAI has released a new and improved update for Grok Build. v1.0.12 — 2026-08-27 Performance: • Worktree creation is faster by skipping stale reflog copies. Bug Fixes: • Copying wrapped table cells no longer inserts unwanted spaces at line breaks. • MCP server connections that fail transiently now retry instead of staying unavailable. • Waiting on subagents after an interjection no longer blocks on unrelated background work. • Prompt blocks now show friendly hook descriptions instead of internal IDs. • Truncation error message no longer suggests asking for a shorter answer. • Context estimates for conversations with reasoning are now more accurate. • Token usage after rewinding or switching modes now matches the actual server-reported count instead of overestimating. • Context bar now updates immediately when auto-compaction begins instead of waiting until it finishes. • File system monitoring for .NET projects no longer creates excessive watchers on Linux. • Auto recap no longer appears while a background task or monitor wake turn is streaming. Download Grok Build: Update to the latest Alpha release: grok update --alpha Update to the latest Stable release: grok update
0:11

BREAKING: SpaceXAI has released a new and improved update for Grok Build. v1.0.12 — 2026-08-27 Performance: • Worktree creation is faster by skipping stale reflog copies. Bug Fixes: • Copying wrapped table cells no longer inserts unwanted spaces at line breaks. • MCP server connections that fail transiently now retry instead of staying unavailable. • Waiting on subagents after an interjection no longer blocks on unrelated background work. • Prompt blocks now show friendly hook descriptions instead of internal IDs. • Truncation error message no longer suggests asking for a shorter answer. • Context estimates for conversations with reasoning are now more accurate. • Token usage after rewinding or switching modes now matches the actual server-reported count instead of overestimating. • Context bar now updates immediately when auto-compaction begins instead of waiting until it finishes. • File system monitoring for .NET projects no longer creates excessive watchers on Linux. • Auto recap no longer appears while a background task or monitor wake turn is streaming. Download Grok Build: Update to the latest Alpha release: grok update --alpha Update to the latest Stable release: grok update

DogeDesigner

410,896 просмотров • 13 дней назад

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
0:12

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

61,105 просмотров • 2 дней назад

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
0:16

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,307 просмотров • 9 дней назад

BREAKING: SpaceXAI has released another major new update for Grok Build (v1.0.17) This update adds multi-step input support for MCP tools, allowing tool calls that require additional information to resume correctly on retry. It also makes next-prompt ghost suggestions less frequent and more accurate, while improving table selection in /btw panels with proper cell highlighting and TSV copying. Features • MCP tools now support the 2026-07-28 multi-round-trip elicitation flow where a tool call can return an input_required state that is resumed on retry. • Next-prompt ghost suggestions now appear less often and are more accurate by preferring silence when the next line is not obvious. Bug Fixes • Table cell selection inside /btw panels now correctly highlights cells and copies as TSV instead of drawing a linear rectangle. Download Grok Build: Update to the latest Alpha release: grok update --alpha Update to the latest Stable release: grok update
0:12

BREAKING: SpaceXAI has released another major new update for Grok Build (v1.0.17) This update adds multi-step input support for MCP tools, allowing tool calls that require additional information to resume correctly on retry. It also makes next-prompt ghost suggestions less frequent and more accurate, while improving table selection in /btw panels with proper cell highlighting and TSV copying. Features • MCP tools now support the 2026-07-28 multi-round-trip elicitation flow where a tool call can return an input_required state that is resumed on retry. • Next-prompt ghost suggestions now appear less often and are more accurate by preferring silence when the next line is not obvious. Bug Fixes • Table cell selection inside /btw panels now correctly highlights cells and copies as TSV instead of drawing a linear rectangle. Download Grok Build: Update to the latest Alpha release: grok update --alpha Update to the latest Stable release: grok update

DogeDesigner

43,687 просмотров • 8 дней назад

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.
0:24

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 просмотров • 7 месяцев назад

Claude Code Desktop now opens a new window for each session This makes it much easier to visualize multiple Claude Code agents running in parallel My current stack depends on the task: - Ghostty: when starting a project. Bash commands, git, env variables, provider connections. All manual through the terminal with a Claude panel running alongside. - Claude Code Desktop: once everything is configured. GitHub connected, CLAUDE.md, Skills, subagents and Hooks ready. Claude Code runs on its own, no more terminal setup, just panels running and outputs to review. - VSCode: when I need to review code by hand. I use it less and less, but there are moments where I have to confirm Claude got it right. I usually open the Claude extension inside VSCode, but it lacks most of the CLI features so it's limited Solid update. Worth trying once your workflows are already set up 👇
0:16

Claude Code Desktop now opens a new window for each session This makes it much easier to visualize multiple Claude Code agents running in parallel My current stack depends on the task: - Ghostty: when starting a project. Bash commands, git, env variables, provider connections. All manual through the terminal with a Claude panel running alongside. - Claude Code Desktop: once everything is configured. GitHub connected, CLAUDE.md, Skills, subagents and Hooks ready. Claude Code runs on its own, no more terminal setup, just panels running and outputs to review. - VSCode: when I need to review code by hand. I use it less and less, but there are moments where I have to confirm Claude got it right. I usually open the Claude extension inside VSCode, but it lacks most of the CLI features so it's limited Solid update. Worth trying once your workflows are already set up 👇

Daniel San

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

whoever leaked this has bigger balls than sense SpaceXAI shipped five hireable workers for $200 a month, then wrote the catch into its own Grok Bot documentation and left the page up: all five run on one computer, so one sign-in hands the browser session, the files and the command-line credentials to every one of them the NSA, CISA and the cyber agencies of the UK, Canada, Australia and New Zealand had published the opposite instruction 103 days earlier: no broad or unrestricted access, low-risk and non-sensitive work only i ran four of mine on one account for a week, counting what each could reach: eleven signed-in apps, one browser profile, and deleting a bot left all of it standing Grok Bot is worth hiring five times over, and you can draw its blast radius before the second one exists: - sign in for the bot that needs the site, then open the others and see what they reach: that session is theirs the moment it exists - give each bot its own account on the app, since the docs tell you in writing to stop using separate bots as a security boundary - put the stop line in the description, as an approval controls the proposed action and leaves whatever already ran where it landed - cap the spend outside the product, because there is no bot-specific spend cap yet and the audit view of what they did is still coming - keep the money and the customer replies in your own hands, and let the other four start from scratch each morning on work that cannot bite one sign-in is also why this pays: five names finish inside your real tools instead of handing you drafts to paste my take, and it is the uncomfortable one: your real limit on Grok Bot is how many logins you will put on one machine, and the hiring was always the easy half bookmark this, the five descriptions that let bots hand work to each other and the one folder that survives an update are written out in the article ↓
0:15

whoever leaked this has bigger balls than sense SpaceXAI shipped five hireable workers for $200 a month, then wrote the catch into its own Grok Bot documentation and left the page up: all five run on one computer, so one sign-in hands the browser session, the files and the command-line credentials to every one of them the NSA, CISA and the cyber agencies of the UK, Canada, Australia and New Zealand had published the opposite instruction 103 days earlier: no broad or unrestricted access, low-risk and non-sensitive work only i ran four of mine on one account for a week, counting what each could reach: eleven signed-in apps, one browser profile, and deleting a bot left all of it standing Grok Bot is worth hiring five times over, and you can draw its blast radius before the second one exists: - sign in for the bot that needs the site, then open the others and see what they reach: that session is theirs the moment it exists - give each bot its own account on the app, since the docs tell you in writing to stop using separate bots as a security boundary - put the stop line in the description, as an approval controls the proposed action and leaves whatever already ran where it landed - cap the spend outside the product, because there is no bot-specific spend cap yet and the audit view of what they did is still coming - keep the money and the customer replies in your own hands, and let the other four start from scratch each morning on work that cannot bite one sign-in is also why this pays: five names finish inside your real tools instead of handing you drafts to paste my take, and it is the uncomfortable one: your real limit on Grok Bot is how many logins you will put on one machine, and the hiring was always the easy half bookmark this, the five descriptions that let bots hand work to each other and the one folder that survives an update are written out in the article ↓

Argona

694,694 просмотров • 24 дней назад

Sure, but the idea of simplifying the appearance of Fortnite, the locker and the shop are all going in the exact opposite direction of simplicity. Equipping cosmetics takes double, if not triple the clicks. The UI is impractical and janky, not to mention the introduction of buttons and drop-down menus that were far easier to access previously. Selecting a skin to rotate it, preview it or even spin it around now requires clicking on it, which then applies it to your loadout. Previously this needed a confirm button so you could preview and choose skins, backblings etc without loosing your currently equipped on if you want to go back. Wraps are not included as part of a character's preset despite being completely relevant to the skin worn. Changing emotes, lobby tracks, and all cosmetics now means you have to back out and change tabs, something that could have previously been done on 1 page. The sectioned tabs make sense with new types like LEGO Kits, Cars, Instruments but there's no need to separate Character from Wraps, Emotes or Lobby. Archiving or Favoriting items can no longer be done in batches or quickly. Previously all you had to do was click once per cosmetic on the button but now you have to enter a drop down and select it for every individual item. Applying wraps to all slots now requires a drop down menu rather than simply clicking the button at the bottom. Swinging a pickaxe or redeploying a glider is near impossible to do and feels like more of a chore to actually accomplish with the drop-down menu. It overlays onto other items meaning as soon as it's clicked the menu vanishes and switches to another cosmetic before the animation can even begin. Cosmetics in the locker can be searched by seasons using "S1-17" but after S18+ they no longer filter. Entering the drop-down menu or right-clicking anything in the locker accidentally immediately takes you all the way back to your currently equipped item when exiting. The filter menu requires an "apply" button to be pressed rather than simply closing and applying when selecting one of the filters, taking longer and more clicks to simply find your recent items or remove a filter. The filter menu was also better as a side panel so you don't have to move your cursor to the center of the screen and back every single time. As a side panel it also allowed for more options to be displayed, whereas the current one requires a huge scroll bar to simply filter by favorite. The presets menu scroll wheel also zooms the skins in and out as you scroll up and down the list. Because of the randomize preset button, the list compared to when saving a preset is all moved up by 1, becoming disorientating to where the preset was in relation to the rows. The shop no longer displays item descriptions or set names on cosmetics - now requiring a click on each individual item when there is adequate space to do so. The new shop and locker appearance can be accustomed to, however, it NEEDS the basic functionality and user-friendly UI elements that the previous ones had. Simple buttons at the bottom to favorite, swing, redeploy and equip. Less tabs to switch between, less clicks required to complete simple tasks and less feeling like there's a battle against the UI itself just to equip the cosmetics you paid for. We appreciate the moves the renew the locker and shop, but in terms of functionality and user interaction, there is nothing we want more than the old one back or the old one's elements merged into the new appearance. Thank you.
0:18

Sure, but the idea of simplifying the appearance of Fortnite, the locker and the shop are all going in the exact opposite direction of simplicity. Equipping cosmetics takes double, if not triple the clicks. The UI is impractical and janky, not to mention the introduction of buttons and drop-down menus that were far easier to access previously. Selecting a skin to rotate it, preview it or even spin it around now requires clicking on it, which then applies it to your loadout. Previously this needed a confirm button so you could preview and choose skins, backblings etc without loosing your currently equipped on if you want to go back. Wraps are not included as part of a character's preset despite being completely relevant to the skin worn. Changing emotes, lobby tracks, and all cosmetics now means you have to back out and change tabs, something that could have previously been done on 1 page. The sectioned tabs make sense with new types like LEGO Kits, Cars, Instruments but there's no need to separate Character from Wraps, Emotes or Lobby. Archiving or Favoriting items can no longer be done in batches or quickly. Previously all you had to do was click once per cosmetic on the button but now you have to enter a drop down and select it for every individual item. Applying wraps to all slots now requires a drop down menu rather than simply clicking the button at the bottom. Swinging a pickaxe or redeploying a glider is near impossible to do and feels like more of a chore to actually accomplish with the drop-down menu. It overlays onto other items meaning as soon as it's clicked the menu vanishes and switches to another cosmetic before the animation can even begin. Cosmetics in the locker can be searched by seasons using "S1-17" but after S18+ they no longer filter. Entering the drop-down menu or right-clicking anything in the locker accidentally immediately takes you all the way back to your currently equipped item when exiting. The filter menu requires an "apply" button to be pressed rather than simply closing and applying when selecting one of the filters, taking longer and more clicks to simply find your recent items or remove a filter. The filter menu was also better as a side panel so you don't have to move your cursor to the center of the screen and back every single time. As a side panel it also allowed for more options to be displayed, whereas the current one requires a huge scroll bar to simply filter by favorite. The presets menu scroll wheel also zooms the skins in and out as you scroll up and down the list. Because of the randomize preset button, the list compared to when saving a preset is all moved up by 1, becoming disorientating to where the preset was in relation to the rows. The shop no longer displays item descriptions or set names on cosmetics - now requiring a click on each individual item when there is adequate space to do so. The new shop and locker appearance can be accustomed to, however, it NEEDS the basic functionality and user-friendly UI elements that the previous ones had. Simple buttons at the bottom to favorite, swing, redeploy and equip. Less tabs to switch between, less clicks required to complete simple tasks and less feeling like there's a battle against the UI itself just to equip the cosmetics you paid for. We appreciate the moves the renew the locker and shop, but in terms of functionality and user interaction, there is nothing we want more than the old one back or the old one's elements merged into the new appearance. Thank you.

FNAssist

178,895 просмотров • 2 лет назад

Another WTF moment. A developer just open-sourced a coding agent harness that boots 245x faster than Claude Code. It's called jcode. You launch it and the first frame renders in 14 milliseconds. Claude Code takes 3,436. One active session uses 27.8 MB of RAM. Claude Code uses 386.6. Run ten sessions in parallel and jcode holds at 117 MB while OpenCode swells to 3.2 GB. Each agent has a semantic memory graph instead of a scratchpad. Every turn gets embedded as a vector. The graph is queried on every turn for related memories, and a sideagent verifies the hits before injecting them into context. Consolidation runs in the background to check for stale or conflicting facts. No manual /remember calls. No token burn on lookup tools. The provider list is 30+ deep. Claude, ChatGPT, Gemini, GitHub Copilot, Azure, OpenRouter, DeepSeek, Groq, Mistral, Perplexity, Fireworks, Ollama, LM Studio, and any OpenAI-compatible endpoint you point it at. Ran out of tokens on your first ChatGPT Pro sub? /account swaps to the second. Then there's Swarm. Spawn two agents in the same repo and the server manages them. When agent A edits a file agent B has been reading, agent B gets pinged and can check the diff. Agents can DM each other, broadcast to the room, or spawn their own worker teams for parallel tasks. Groups, channels, and completion statuses are handled automatically. The UI has live side panels that render mermaid diagrams inline. To make it fast, the author wrote a Rust mermaid renderer 1800x faster than the JavaScript one, then wrote a custom terminal called Handterm because no existing terminal could do smooth partial-line scrolling. Self-dev mode is where it gets wild. Tell your agent to enter self-dev and it starts editing jcode's own source code, rebuilds the binary, reloads it live, and keeps working across your existing sessions. You can also resume broken sessions from Claude Code, Codex, OpenCode, or pi directly inside jcode. Anthropic's cache goes cold at the 5-minute mark and you're staring down a big cache miss on your next turn? The UI warns you before you spend the tokens. Written in Rust. MIT licensed. Runs on macOS, Windows, Linux, and Termux. Sitting at 11.2k stars with a native iOS app coming.
0:17

Another WTF moment. A developer just open-sourced a coding agent harness that boots 245x faster than Claude Code. It's called jcode. You launch it and the first frame renders in 14 milliseconds. Claude Code takes 3,436. One active session uses 27.8 MB of RAM. Claude Code uses 386.6. Run ten sessions in parallel and jcode holds at 117 MB while OpenCode swells to 3.2 GB. Each agent has a semantic memory graph instead of a scratchpad. Every turn gets embedded as a vector. The graph is queried on every turn for related memories, and a sideagent verifies the hits before injecting them into context. Consolidation runs in the background to check for stale or conflicting facts. No manual /remember calls. No token burn on lookup tools. The provider list is 30+ deep. Claude, ChatGPT, Gemini, GitHub Copilot, Azure, OpenRouter, DeepSeek, Groq, Mistral, Perplexity, Fireworks, Ollama, LM Studio, and any OpenAI-compatible endpoint you point it at. Ran out of tokens on your first ChatGPT Pro sub? /account swaps to the second. Then there's Swarm. Spawn two agents in the same repo and the server manages them. When agent A edits a file agent B has been reading, agent B gets pinged and can check the diff. Agents can DM each other, broadcast to the room, or spawn their own worker teams for parallel tasks. Groups, channels, and completion statuses are handled automatically. The UI has live side panels that render mermaid diagrams inline. To make it fast, the author wrote a Rust mermaid renderer 1800x faster than the JavaScript one, then wrote a custom terminal called Handterm because no existing terminal could do smooth partial-line scrolling. Self-dev mode is where it gets wild. Tell your agent to enter self-dev and it starts editing jcode's own source code, rebuilds the binary, reloads it live, and keeps working across your existing sessions. You can also resume broken sessions from Claude Code, Codex, OpenCode, or pi directly inside jcode. Anthropic's cache goes cold at the 5-minute mark and you're staring down a big cache miss on your next turn? The UI warns you before you spend the tokens. Written in Rust. MIT licensed. Runs on macOS, Windows, Linux, and Termux. Sitting at 11.2k stars with a native iOS app coming.

Brady Long

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

🚨 WARNING: THE NEXT 24 HOURS WILL CHANGE EVERYTHING! Trump just said Iran may no longer exist as a country. Read that again. “The Islamic Republic of Iran will no longer exist.” This is NOT normal diplomatic language. This is a direct warning. And markets will feel it on Monday. The ceasefire is basically dead. The US has now struck Iranian missile storage sites, drone facilities and coastal radar positions for the second time. Iran has also violated the agreement multiple times in just 48 hours. → Ships attacked in the Strait of Hormuz → Drone strikes on Bahrain → New threats against US forces Now connect the dots. Every new attack is getting a bigger response. This is NOT de-escalation. Both sides are climbing the escalation ladder one step at a time. And Trump just told everyone what could be waiting at the top. Now the worst part. Markets are closed. That means all of this risk will be priced at once when futures open. Oil will NOT simply pump. Oil could explode. Around 20% of global oil supply moves through the Strait of Hormuz. And the Strait is now becoming an active military zone between Iran and the US. That one fact changes everything. Higher oil means: → Inflation comes back → Fed rate cuts get priced out → Bond yields pump → Liquidity gets tighter → Stocks and crypto dump The entire market will reprice around oil. Gold should normally protect investors. But gold is already down 28% from its ATH after losing around $12 trillion in value. Crypto should normally act differently. But $MSTR is already down 81%. The institutional crypto trade is already getting destroyed. Now look at Trump’s final warning: “There may come a point when we are no longer able to be reasonable.” That sentence was posted publicly for a reason. The deal is NOT failing anymore. The deal is over. And what comes after a failed US Iran deal in the Strait of Hormuz is NOT another negotiation. It is war. Markets are NOT pricing that word now. But they will on Monday. I will keep you updated on every major development. When I rotate my money, I will post every move here so my followers can protect themselves. Follow and turn notifications on. Many will regret not doing it before Monday.
0:13

🚨 WARNING: THE NEXT 24 HOURS WILL CHANGE EVERYTHING! Trump just said Iran may no longer exist as a country. Read that again. “The Islamic Republic of Iran will no longer exist.” This is NOT normal diplomatic language. This is a direct warning. And markets will feel it on Monday. The ceasefire is basically dead. The US has now struck Iranian missile storage sites, drone facilities and coastal radar positions for the second time. Iran has also violated the agreement multiple times in just 48 hours. → Ships attacked in the Strait of Hormuz → Drone strikes on Bahrain → New threats against US forces Now connect the dots. Every new attack is getting a bigger response. This is NOT de-escalation. Both sides are climbing the escalation ladder one step at a time. And Trump just told everyone what could be waiting at the top. Now the worst part. Markets are closed. That means all of this risk will be priced at once when futures open. Oil will NOT simply pump. Oil could explode. Around 20% of global oil supply moves through the Strait of Hormuz. And the Strait is now becoming an active military zone between Iran and the US. That one fact changes everything. Higher oil means: → Inflation comes back → Fed rate cuts get priced out → Bond yields pump → Liquidity gets tighter → Stocks and crypto dump The entire market will reprice around oil. Gold should normally protect investors. But gold is already down 28% from its ATH after losing around $12 trillion in value. Crypto should normally act differently. But $MSTR is already down 81%. The institutional crypto trade is already getting destroyed. Now look at Trump’s final warning: “There may come a point when we are no longer able to be reasonable.” That sentence was posted publicly for a reason. The deal is NOT failing anymore. The deal is over. And what comes after a failed US Iran deal in the Strait of Hormuz is NOT another negotiation. It is war. Markets are NOT pricing that word now. But they will on Monday. I will keep you updated on every major development. When I rotate my money, I will post every move here so my followers can protect themselves. Follow and turn notifications on. Many will regret not doing it before Monday.

Wimar.X

148,506 просмотров • 2 месяцев назад

Yesterday at Brown University ICERM's workshop on “Agentic Scientific Computing and Scientific Machine Learning” I spoke about “Adaptive Swarms Across Scales”, making the case for scientific AI as systems that can create representations, stress them, fracture them, and enlarge the category in which future representations live. The category here is a composable and breakable working universe of science: data, hypotheses, simulations, measurements, tools, failures, figures, papers, provenance, and the transformations that connect them. Discovery happens when those transformations become executable, inspectable, composable, and capable of changing the world model they operate within. Atomistic modeling gives one category - states, forces, trajectories, observables, boundary conditions, conservation laws. Neural surrogates learn fast morphisms inside or between such categories. But discovery is higher-order: it changes which objects and morphisms are available in the first place: what variables exist, what operations are allowed, what evidence counts, what scale is active, what invariant is being preserved, and what kind of explanation the system is even capable of forming. This is scientific method as adaptive architecture: compression, stress, fracture, recomposition. Fracture matters here because it makes the logic physical: a non-commuting diagram realized in matter. The imposed load, material hierarchy, defect field, and assumed continuum description no longer map cleanly into the observed outcome. The crack is the obstruction and it identifies where the old morphism failed and where a new representation must be introduced. The physical crack and the categorical obstruction are the same event viewed in different substrates. ScienceClaw × Infinite is a machine for constructing and transforming a category of scientific artifacts. Each artifact is typed. Each operation has lineage. Each failed branch remains in the category as reusable structure. The “paper” is no longer the terminal object of science; it is one projection of a larger compositional trace, and it can be generated at any time for consumption by a human or an AI. With that the unit of scientific labor is changing. For most of the twentieth century the unit was the result (a measurement, a theorem, a synthesized molecule). It is now becoming the algorithm that produces results, and after that, the substrate of discovery itself. The static PDF is the wrong terminal object for this regime, and the role of the scientist with it. We now design algorithms that build algorithms, and eventually substrates in which such algorithms compose themselves. At that point, the scientist is no longer outside the discovery system. The scientist becomes one of the representations the system can transform. In that sense, the systems will eventually do science to us, and that is the structural consequence of the principle they are built on.
0:12

Yesterday at Brown University ICERM's workshop on “Agentic Scientific Computing and Scientific Machine Learning” I spoke about “Adaptive Swarms Across Scales”, making the case for scientific AI as systems that can create representations, stress them, fracture them, and enlarge the category in which future representations live. The category here is a composable and breakable working universe of science: data, hypotheses, simulations, measurements, tools, failures, figures, papers, provenance, and the transformations that connect them. Discovery happens when those transformations become executable, inspectable, composable, and capable of changing the world model they operate within. Atomistic modeling gives one category - states, forces, trajectories, observables, boundary conditions, conservation laws. Neural surrogates learn fast morphisms inside or between such categories. But discovery is higher-order: it changes which objects and morphisms are available in the first place: what variables exist, what operations are allowed, what evidence counts, what scale is active, what invariant is being preserved, and what kind of explanation the system is even capable of forming. This is scientific method as adaptive architecture: compression, stress, fracture, recomposition. Fracture matters here because it makes the logic physical: a non-commuting diagram realized in matter. The imposed load, material hierarchy, defect field, and assumed continuum description no longer map cleanly into the observed outcome. The crack is the obstruction and it identifies where the old morphism failed and where a new representation must be introduced. The physical crack and the categorical obstruction are the same event viewed in different substrates. ScienceClaw × Infinite is a machine for constructing and transforming a category of scientific artifacts. Each artifact is typed. Each operation has lineage. Each failed branch remains in the category as reusable structure. The “paper” is no longer the terminal object of science; it is one projection of a larger compositional trace, and it can be generated at any time for consumption by a human or an AI. With that the unit of scientific labor is changing. For most of the twentieth century the unit was the result (a measurement, a theorem, a synthesized molecule). It is now becoming the algorithm that produces results, and after that, the substrate of discovery itself. The static PDF is the wrong terminal object for this regime, and the role of the scientist with it. We now design algorithms that build algorithms, and eventually substrates in which such algorithms compose themselves. At that point, the scientist is no longer outside the discovery system. The scientist becomes one of the representations the system can transform. In that sense, the systems will eventually do science to us, and that is the structural consequence of the principle they are built on.

Markus J. Buehler

10,095 просмотров • 4 месяцев назад

What would you have done? Merge right and let it play out? Hold your ground? Exactly what a Preventable Crash Really Looks Like. You’re driving a semi. Three-lane highway. You're in the center lane. Left lane is ending. Right lane is completely empty. Convex mirror shows no one beside you on the right. Three cars are pacing you in the left lane… and they’re about to run out of road. So Why are you still in the center lane? You’re not boxed in. You’re not blind. And you’ve already seen the sign telling you the left lane ends. You could’ve merged right a half-mile ago and cruised on. Instead, you’re now stuck in the lane of most resistance. That car flying up on your left? It’s doing what 80% of cars do when the lane end, they punch it. They try to get ahead. Not smart. Not courteous. But absolutely predictable. And that’s the point. You’re the professional. They're not. You know how this goes. You should know exactly what to expect. Textbook behavior. So when that car forces a merge in front of your bumper with 20 feet left of asphalt, are they wrong? Yep. But when you don’t lift off the gas, don’t merge right, and don’t anticipate what’s clearly unfolding, that’s no longer just their problem. Now it’s yours. And it’s preventable. What happens next👇 ✅ You plow into the car. ✅ You get to sit roadside for 3 hours explaining it to law enforcement and doing paperwork. ✅ You spend another 3 months Data Q’ing it, defending it in court, or arguing it with claims adjusters. ✅ It’s on your CSA now. ✅ Your insurance premium goes up. ✅ The carrier eats the deductible. ✅ And you get labeled as someone who “could’ve avoided it but didn’t.” Being a truck driver isn’t just turning a wheel. It’s a chess match. It’s anticipating the next three moves. When you choose not to play defense, you’re the one who loses, even when you’re “not at fault.” Some stats to chew on👇 👉Lane change/merge crashes account for nearly 10% of all large truck crashes. 👉FMCSA's Large Truck Crash Causation Study consistently shows "decision error" and "recognition error" as top contributing factors in preventable crashes. 👉The average post-crash litigation process? 3–6 months minimum, and that’s before settlements, audits, or nuclear verdicts.
0:13

What would you have done? Merge right and let it play out? Hold your ground? Exactly what a Preventable Crash Really Looks Like. You’re driving a semi. Three-lane highway. You're in the center lane. Left lane is ending. Right lane is completely empty. Convex mirror shows no one beside you on the right. Three cars are pacing you in the left lane… and they’re about to run out of road. So Why are you still in the center lane? You’re not boxed in. You’re not blind. And you’ve already seen the sign telling you the left lane ends. You could’ve merged right a half-mile ago and cruised on. Instead, you’re now stuck in the lane of most resistance. That car flying up on your left? It’s doing what 80% of cars do when the lane end, they punch it. They try to get ahead. Not smart. Not courteous. But absolutely predictable. And that’s the point. You’re the professional. They're not. You know how this goes. You should know exactly what to expect. Textbook behavior. So when that car forces a merge in front of your bumper with 20 feet left of asphalt, are they wrong? Yep. But when you don’t lift off the gas, don’t merge right, and don’t anticipate what’s clearly unfolding, that’s no longer just their problem. Now it’s yours. And it’s preventable. What happens next👇 ✅ You plow into the car. ✅ You get to sit roadside for 3 hours explaining it to law enforcement and doing paperwork. ✅ You spend another 3 months Data Q’ing it, defending it in court, or arguing it with claims adjusters. ✅ It’s on your CSA now. ✅ Your insurance premium goes up. ✅ The carrier eats the deductible. ✅ And you get labeled as someone who “could’ve avoided it but didn’t.” Being a truck driver isn’t just turning a wheel. It’s a chess match. It’s anticipating the next three moves. When you choose not to play defense, you’re the one who loses, even when you’re “not at fault.” Some stats to chew on👇 👉Lane change/merge crashes account for nearly 10% of all large truck crashes. 👉FMCSA's Large Truck Crash Causation Study consistently shows "decision error" and "recognition error" as top contributing factors in preventable crashes. 👉The average post-crash litigation process? 3–6 months minimum, and that’s before settlements, audits, or nuclear verdicts.

Rob Carpenter

16,777 просмотров • 7 месяцев назад

🚨 WARNING: SOMETHING EXTREMELY BAD IS COMING ON MONDAY... Four things are breaking at the same time. Interest rate hikes by December is almost confirmed now. Not pauses. Not holds. HIKES. Everything priced on the assumption that cheap money returns just got repriced from scratch. Every leveraged position, every rate-sensitive asset, every model built on a pivot that isn't coming. Japan officially entered yen intervention, that sounds technical. Here's what it means in practice. Japan is burning through reserves defending a currency that's been collapsing for months. And to fund that defense they sell what they own. US Treasuries, at scale, Into a bond market that's already under pressure from every other direction. China hasn't stopped, while everyone was watching Iran and the Fed, China has been quietly and consistently dumping US Treasury holdings for weeks. No announcement, no fanfare. Just steady selling that shows up in the data for anyone paying attention. And the AI rally is dying in real time. The momentum that carried Nvidia, Microsoft, Google, and Meta to valuations that made no fundamental sense is reversing. Funds that loaded up on the AI narrative at the top are now the ones selling into every bounce. The multiple that drove three years of outperformance doesn't survive a rate hike cycle and a liquidity crisis simultaneously. Now put all four together. Rates going up, liquidity going out. The world's two largest foreign Treasury holders selling simultaneously. And the primary growth narrative of the last three years losing believers by the session. When liquidity disappears across multiple layers of the financial system at once markets don't correct. They don't dip, they don't give you a clean exit. They crash fast and they crash hard. Stocks. Bonds. Metals. Crypto. There is no rotation trade that works when everything is being sold to cover everything else. There is no safe haven when the people who need cash are selling whatever has a bid. Insiders are already out, funds are already cutting. The rotation happened this week while retail was still debating whether to buy the dip. By the time Monday's open confirms what's coming it's already too late to position. This sounds SCARY, but I will keep you updated on everything here When I rotate money, I will post my moves here so my FOLLOWERS can SAVE their money Many will regret not following me earlier...
0:15

🚨 WARNING: SOMETHING EXTREMELY BAD IS COMING ON MONDAY... Four things are breaking at the same time. Interest rate hikes by December is almost confirmed now. Not pauses. Not holds. HIKES. Everything priced on the assumption that cheap money returns just got repriced from scratch. Every leveraged position, every rate-sensitive asset, every model built on a pivot that isn't coming. Japan officially entered yen intervention, that sounds technical. Here's what it means in practice. Japan is burning through reserves defending a currency that's been collapsing for months. And to fund that defense they sell what they own. US Treasuries, at scale, Into a bond market that's already under pressure from every other direction. China hasn't stopped, while everyone was watching Iran and the Fed, China has been quietly and consistently dumping US Treasury holdings for weeks. No announcement, no fanfare. Just steady selling that shows up in the data for anyone paying attention. And the AI rally is dying in real time. The momentum that carried Nvidia, Microsoft, Google, and Meta to valuations that made no fundamental sense is reversing. Funds that loaded up on the AI narrative at the top are now the ones selling into every bounce. The multiple that drove three years of outperformance doesn't survive a rate hike cycle and a liquidity crisis simultaneously. Now put all four together. Rates going up, liquidity going out. The world's two largest foreign Treasury holders selling simultaneously. And the primary growth narrative of the last three years losing believers by the session. When liquidity disappears across multiple layers of the financial system at once markets don't correct. They don't dip, they don't give you a clean exit. They crash fast and they crash hard. Stocks. Bonds. Metals. Crypto. There is no rotation trade that works when everything is being sold to cover everything else. There is no safe haven when the people who need cash are selling whatever has a bid. Insiders are already out, funds are already cutting. The rotation happened this week while retail was still debating whether to buy the dip. By the time Monday's open confirms what's coming it's already too late to position. This sounds SCARY, but I will keep you updated on everything here When I rotate money, I will post my moves here so my FOLLOWERS can SAVE their money Many will regret not following me earlier...

ᴛʀᴀᴄᴇʀ

169,405 просмотров • 2 месяцев назад

This Chinese developer launched Llama 70B locally on a MacBook on a plane and for a full 11 hours without internet ran client projects. He was sitting by the window on a transatlantic flight with a MacBook Pro M4 with 64 GB of memory. WiFi on board cost $25 for the flight. He declined. No cloud API, no connection to Anthropic or OpenAI servers, no internet at all. Just a local Llama 3.3 70B on bf16 and his own orchestrator script. The model runs through llama.cpp. Generation speed, 71 tokens per second. Context around 60,000 tokens. Memory usage, 48.6 GiB out of 64. Battery at takeoff, 3 hours 21 minutes. And he gave the orchestrator this system prompt before takeoff: "You are an offline orchestrator running on a single MacBook. There is no network. The only resources you have are local files in /Users/dev/work, the Llama 70B inference server at localhost:8080, and a battery budget of 3 hours 21 minutes. Process the queue at /Users/dev/work/queue.jsonl (one client task per line). For each task: draft → run local evals → save artefact to /Users/dev/work/done/. Save context checkpoints every 12 tasks so you can resume after a battery swap. Stop only on empty queue or when battery drops below 5%." So the system knows exactly what resources it is running on. It knows it has no connection to the outside world for the next 11 hours. It knows it has finite memory and a finite battery. It knows the human will not intervene until the plane lands. The system runs in 1 loop. Takes a task from the queue, runs it through inference, saves the artifact, writes a checkpoint. Task after task, just like that. And only when the battery drops below 5% does the orchestrator automatically pause, waits for the laptop to switch to the backup power bank, and continues from the last checkpoint. Here is what the system actually writes in his log during the flight: "saved context checkpoint 8 of 12 (pos_min = 488, pos_max = 50118, size = 62.813 MiB)" "restored context checkpoint (pos_min = 488, pos_max = 50118)" "prompt processing progress: n_tokens = 50 / 60 818" "task 37016 done | tps = 71 s tokens text → /Users/dev/work/done/proposal_westside.md" Outside the window, clouds, blue sky, and no WiFi. On the tray, 1 MacBook, an open terminal on 2 screens, and an inference server on localhost. From what I have observed, this is the cleanest offline AI workflow I have seen in the past year: 11 hours of flight, $0 for WiFi, and the entire client queue closed before landing.
0:10

This Chinese developer launched Llama 70B locally on a MacBook on a plane and for a full 11 hours without internet ran client projects. He was sitting by the window on a transatlantic flight with a MacBook Pro M4 with 64 GB of memory. WiFi on board cost $25 for the flight. He declined. No cloud API, no connection to Anthropic or OpenAI servers, no internet at all. Just a local Llama 3.3 70B on bf16 and his own orchestrator script. The model runs through llama.cpp. Generation speed, 71 tokens per second. Context around 60,000 tokens. Memory usage, 48.6 GiB out of 64. Battery at takeoff, 3 hours 21 minutes. And he gave the orchestrator this system prompt before takeoff: "You are an offline orchestrator running on a single MacBook. There is no network. The only resources you have are local files in /Users/dev/work, the Llama 70B inference server at localhost:8080, and a battery budget of 3 hours 21 minutes. Process the queue at /Users/dev/work/queue.jsonl (one client task per line). For each task: draft → run local evals → save artefact to /Users/dev/work/done/. Save context checkpoints every 12 tasks so you can resume after a battery swap. Stop only on empty queue or when battery drops below 5%." So the system knows exactly what resources it is running on. It knows it has no connection to the outside world for the next 11 hours. It knows it has finite memory and a finite battery. It knows the human will not intervene until the plane lands. The system runs in 1 loop. Takes a task from the queue, runs it through inference, saves the artifact, writes a checkpoint. Task after task, just like that. And only when the battery drops below 5% does the orchestrator automatically pause, waits for the laptop to switch to the backup power bank, and continues from the last checkpoint. Here is what the system actually writes in his log during the flight: "saved context checkpoint 8 of 12 (pos_min = 488, pos_max = 50118, size = 62.813 MiB)" "restored context checkpoint (pos_min = 488, pos_max = 50118)" "prompt processing progress: n_tokens = 50 / 60 818" "task 37016 done | tps = 71 s tokens text → /Users/dev/work/done/proposal_westside.md" Outside the window, clouds, blue sky, and no WiFi. On the tray, 1 MacBook, an open terminal on 2 screens, and an inference server on localhost. From what I have observed, this is the cleanest offline AI workflow I have seen in the past year: 11 hours of flight, $0 for WiFi, and the entire client queue closed before landing.

Blaze

1,842,664 просмотров • 4 месяцев назад

Impeccable 3.7 brings linting to design. Until now it was a skill you asked for help. Now it's a design-system-aware feedback loop that runs while your agent builds, catching slop and design drift before they land. 🪝 Design hooks for Claude, Codex, and Cursor They run after every UI edit and quietly nudge your agent to fix slop and drift. The output isn't another wall of lint: it separates new findings from already-seen ones, flags clean scans, and asks the agent to use judgment. Fix real issues, leave intentional demos alone, save exceptions to config instead of littering your source. 🎨 Slop detection is now project-aware Reads your actual design system from DESIGN.md, your typography, palette, radius scale, and tokens, and flags drift from your system, not just generic AI slop: • this font isn't in your design system • this color is outside your documented palette • this radius doesn't match your rounded scale The same engine powers both the hooks and the CLI, and it's where we're investing next. 🖥️ Live Mode, ready for real projects Svelte/SvelteKit now preview variants as temporary framework components with live params, then accept cleanly back into your source component. Manual text edits got evidence / apply / discard routes, insertions preserve their anchors, and mapped lists and JSX slots clean up far more reliably. ⚡ Leaner core, sharper detector Rule-level evals across 3 providers and 4 niches cut guidance with no measurable lift and dropped examples that taught models bad patterns. The detector now skips hidden and screen-reader-only elements, understands OKLCH alpha and Sass-like inputs, and tightened checks for repeated kickers, oversized H1s, clipped overflow, and cramped padding. 🛠️ CLI caught up impeccable detect loads DESIGN.md by default, motion findings name the exact token or cubic-bezier instead of just "bounce," and impeccable ignores gives real CRUD for exceptions. Hooks and CLI share the same ignores. No split-brain config. Plus a much-improved interactive installer with hooks setup built in. Upgrade: npx impeccable install npm i -g impeccable
0:12

Impeccable 3.7 brings linting to design. Until now it was a skill you asked for help. Now it's a design-system-aware feedback loop that runs while your agent builds, catching slop and design drift before they land. 🪝 Design hooks for Claude, Codex, and Cursor They run after every UI edit and quietly nudge your agent to fix slop and drift. The output isn't another wall of lint: it separates new findings from already-seen ones, flags clean scans, and asks the agent to use judgment. Fix real issues, leave intentional demos alone, save exceptions to config instead of littering your source. 🎨 Slop detection is now project-aware Reads your actual design system from DESIGN.md, your typography, palette, radius scale, and tokens, and flags drift from your system, not just generic AI slop: • this font isn't in your design system • this color is outside your documented palette • this radius doesn't match your rounded scale The same engine powers both the hooks and the CLI, and it's where we're investing next. 🖥️ Live Mode, ready for real projects Svelte/SvelteKit now preview variants as temporary framework components with live params, then accept cleanly back into your source component. Manual text edits got evidence / apply / discard routes, insertions preserve their anchors, and mapped lists and JSX slots clean up far more reliably. ⚡ Leaner core, sharper detector Rule-level evals across 3 providers and 4 niches cut guidance with no measurable lift and dropped examples that taught models bad patterns. The detector now skips hidden and screen-reader-only elements, understands OKLCH alpha and Sass-like inputs, and tightened checks for repeated kickers, oversized H1s, clipped overflow, and cramped padding. 🛠️ CLI caught up impeccable detect loads DESIGN.md by default, motion findings name the exact token or cubic-bezier instead of just "bounce," and impeccable ignores gives real CRUD for exceptions. Hooks and CLI share the same ignores. No split-brain config. Plus a much-improved interactive installer with hooks setup built in. Upgrade: npx impeccable install npm i -g impeccable

Impeccable

233,051 просмотров • 2 месяцев назад

What Trump’s actions show is that globalization is over. Nations must form empires again and secure their strategic space and resources. The world has woken up and is preparing for this new age. If you do not possess a resource at home, or lack direct access to it and the military capability to defend that access and the transport routes then you are dependent on the goodwill of others. The so-called “free and open market” no longer exists. The global Walmart cop has retired. Free, secure, reliable, and cheap global transport may soon be a thing of the past. The world is wide awake and adapting. Europe, meanwhile, reacts with one-sided moral outrage. Geopolitical actions are still interpreted through the outdated ideology of the unipolar moment, judged morally by whether one likes or dislikes the regime being changed. Europe needs to wake up from its liberal, post-political slumber. We are no longer an isolated island between two blocs. We are no longer an economic eunuch living as an adorable pet in the golden cage of a Pax Americana. But the current elites refuse to wake up. They want to become the world police themsevles now - a globocop without a gun. When they speak belligerently about “defending Europe,” they do not mean defending European peoples, national identities, or national interests. They mean defending liberal universalism. They are fanatics of a cargo cult. They are incapable of responding to modern challenges or operating in a de-globalized world. They hate Trump and Putin primarily but because they think they shattered their beautiful dream of globalization out of bad will. They were just reading the signs earlier and rugpulled the unipolar world with imperial politics. Now our elites want to make it the White European man’s burden to rebuild a utopia that never existed in the first place. To get us in line they copy paste a few Vril-Edits, beat their chests and clamor about the "evil" rest of the world. I stand by my words. The real enemy is within. The greatest threat to national survival and European sovereignty is our current rotten, imbecile, unattractiv and stupid elite. Every day they are in power longer, they're losing more European soil, resources, power, lives, and ethnocultural heritage. They must go. Only then can we consolidate, build a Fortress Europe, begin remigration, and return as a sovereign player in the great game. PS: This edits are our culture, not your costume.
0:16

What Trump’s actions show is that globalization is over. Nations must form empires again and secure their strategic space and resources. The world has woken up and is preparing for this new age. If you do not possess a resource at home, or lack direct access to it and the military capability to defend that access and the transport routes then you are dependent on the goodwill of others. The so-called “free and open market” no longer exists. The global Walmart cop has retired. Free, secure, reliable, and cheap global transport may soon be a thing of the past. The world is wide awake and adapting. Europe, meanwhile, reacts with one-sided moral outrage. Geopolitical actions are still interpreted through the outdated ideology of the unipolar moment, judged morally by whether one likes or dislikes the regime being changed. Europe needs to wake up from its liberal, post-political slumber. We are no longer an isolated island between two blocs. We are no longer an economic eunuch living as an adorable pet in the golden cage of a Pax Americana. But the current elites refuse to wake up. They want to become the world police themsevles now - a globocop without a gun. When they speak belligerently about “defending Europe,” they do not mean defending European peoples, national identities, or national interests. They mean defending liberal universalism. They are fanatics of a cargo cult. They are incapable of responding to modern challenges or operating in a de-globalized world. They hate Trump and Putin primarily but because they think they shattered their beautiful dream of globalization out of bad will. They were just reading the signs earlier and rugpulled the unipolar world with imperial politics. Now our elites want to make it the White European man’s burden to rebuild a utopia that never existed in the first place. To get us in line they copy paste a few Vril-Edits, beat their chests and clamor about the "evil" rest of the world. I stand by my words. The real enemy is within. The greatest threat to national survival and European sovereignty is our current rotten, imbecile, unattractiv and stupid elite. Every day they are in power longer, they're losing more European soil, resources, power, lives, and ethnocultural heritage. They must go. Only then can we consolidate, build a Fortress Europe, begin remigration, and return as a sovereign player in the great game. PS: This edits are our culture, not your costume.

Martin Sellner

14,856 просмотров • 7 месяцев назад

🚨 WARNING: TOMORROW WILL BE THE WORST DAY OF 2026!! The U.S.-China trade deal just COLLAPSED. The U.S.-Iran peace deal is officially CANCELLED. And new Trump tariffs are coming. When markets open on Monday, this won't be “just normal volatility.” Stocks will dump. Metals will dump. Bitcoin will dump even harder. Smart money already sees what’s happening. They are not “buying the dip.” They are building cash positions and reducing exposure before the real crash begins. And now add a real trade war on top of that: China is actively rejecting U.S. Nvidia chips. That is not just a tech story. Because once semiconductors become a geopolitical weapon, supply chains stop functioning normally. Capital freezes. Confidence breaks. And global growth expectations reset lower immediately. At the exact same time: → Japanese bond yields are surging → Global bonds are being sold aggressively → The dollar is losing stability → Liquidity is tightening worldwide This is no longer one isolated event. This is pressure building across MULTIPLE fronts simultaneously. And now the geopolitical layer just intensified again. After MONTHS of negotiations, the U.S. and Iran walked away with no agreement. That changes everything. Because when diplomacy fails, markets stop pricing “hope.” They price ESCALATION. And none of this is happening in isolation. Japan’s bond market is already flashing stress. China-U.S. tensions are escalating again through semiconductors. Oil markets are becoming unstable. And liquidity conditions are deteriorating globally at the same time. Now connect the dots. When geopolitical stress collides with a fragile financial system, reactions do not stay contained. They CASCADE. Oil does not pump higher slowly. It goes parabolic. Capital does not rotate calmly. It skyrockets towards safety all at once. And risk assets? They do not “dip.” They COLLAPSE. This is exactly how chain reactions begin. Because once markets start pricing prolonged instability instead of temporary fear, the entire system changes. Watch oil. Watch bonds. Watch semiconductors. Because once this accelerates, there will be no time left to react. I’ve spent years tracking macro and systemic market reactions like this. When the next move becomes clear, I’ll share it here publicly. Follow and turn notifications on. Because by the time it reaches the headlines, it’s already too late.
0:16

🚨 WARNING: TOMORROW WILL BE THE WORST DAY OF 2026!! The U.S.-China trade deal just COLLAPSED. The U.S.-Iran peace deal is officially CANCELLED. And new Trump tariffs are coming. When markets open on Monday, this won't be “just normal volatility.” Stocks will dump. Metals will dump. Bitcoin will dump even harder. Smart money already sees what’s happening. They are not “buying the dip.” They are building cash positions and reducing exposure before the real crash begins. And now add a real trade war on top of that: China is actively rejecting U.S. Nvidia chips. That is not just a tech story. Because once semiconductors become a geopolitical weapon, supply chains stop functioning normally. Capital freezes. Confidence breaks. And global growth expectations reset lower immediately. At the exact same time: → Japanese bond yields are surging → Global bonds are being sold aggressively → The dollar is losing stability → Liquidity is tightening worldwide This is no longer one isolated event. This is pressure building across MULTIPLE fronts simultaneously. And now the geopolitical layer just intensified again. After MONTHS of negotiations, the U.S. and Iran walked away with no agreement. That changes everything. Because when diplomacy fails, markets stop pricing “hope.” They price ESCALATION. And none of this is happening in isolation. Japan’s bond market is already flashing stress. China-U.S. tensions are escalating again through semiconductors. Oil markets are becoming unstable. And liquidity conditions are deteriorating globally at the same time. Now connect the dots. When geopolitical stress collides with a fragile financial system, reactions do not stay contained. They CASCADE. Oil does not pump higher slowly. It goes parabolic. Capital does not rotate calmly. It skyrockets towards safety all at once. And risk assets? They do not “dip.” They COLLAPSE. This is exactly how chain reactions begin. Because once markets start pricing prolonged instability instead of temporary fear, the entire system changes. Watch oil. Watch bonds. Watch semiconductors. Because once this accelerates, there will be no time left to react. I’ve spent years tracking macro and systemic market reactions like this. When the next move becomes clear, I’ll share it here publicly. Follow and turn notifications on. Because by the time it reaches the headlines, it’s already too late.

0xNobler

1,111,884 просмотров • 3 месяцев назад