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

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

На главную

Grok Build CLI just got an update with v0.2.100! 🚀 Changelog v0.2.100 Features: • Session picker now discovers and resumes recent Claude Code, Codex, and Cursor sessions. • Welcome screen now offers a one-click resume nudge for recent Claude, Codex, or Cursor sessions. Bug Fixes: • Web fetch tool...

GrokInsider's profile picture

Grok News

3,053 subscribers

44,121 просмотров • 2 месяцев назад •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

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

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

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

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

Grok Build CLI just got an update with v1.0.5! 🚀 Changelog v1.0.5 Features: • GROK_CONFIG and GROK_CONFIG_PATH environment variables now let launchers override selected config settings without editing config.toml. • Worktrees under ~/.grok/worktrees are now automatically reclaimed when safe, with strong safeguards that never delete a user's last copy. • Hook policy blocks now correctly report "Turn blocked by a hook" instead of "Turn cancelled by user." • Image and video generation now limits how many calls the model can request in one step to avoid overload. • Arabic and Persian text can now be reordered correctly in the terminal UI. Turn on in /settings. • Reasoning effort can now be supplied when an ACP client opens or resumes a session. • Session titles now refresh early in the conversation and stay stable; /resume shows a recap and last-turn summary when available. • GROK_FORCE_LOGIN_TEAM_ID environment variable now lets launchers restrict interactive login to one or more teams. • Preparing spinner now shows readable labels such as "Writing file…" and "Writing edit…" for common tools. Bug Fixes: • Tool calls (shell, grep, list_dir) no longer fail for the rest of a session if /dev/null is removed. • Agent skill discovery now resolves the user's home directory correctly on Windows. • MCP tool calls now show clearer spinner text instead of the raw wire name while arguments are still arriving. • grok inspect no longer crashes when its output is piped into a command that closes the pipe early. • Minimal mode no longer truncates a still-streaming assistant reply when thinking blocks are interleaved.
0:59

Grok Build CLI just got an update with v1.0.5! 🚀 Changelog v1.0.5 Features: • GROK_CONFIG and GROK_CONFIG_PATH environment variables now let launchers override selected config settings without editing config.toml. • Worktrees under ~/.grok/worktrees are now automatically reclaimed when safe, with strong safeguards that never delete a user's last copy. • Hook policy blocks now correctly report "Turn blocked by a hook" instead of "Turn cancelled by user." • Image and video generation now limits how many calls the model can request in one step to avoid overload. • Arabic and Persian text can now be reordered correctly in the terminal UI. Turn on in /settings. • Reasoning effort can now be supplied when an ACP client opens or resumes a session. • Session titles now refresh early in the conversation and stay stable; /resume shows a recap and last-turn summary when available. • GROK_FORCE_LOGIN_TEAM_ID environment variable now lets launchers restrict interactive login to one or more teams. • Preparing spinner now shows readable labels such as "Writing file…" and "Writing edit…" for common tools. Bug Fixes: • Tool calls (shell, grep, list_dir) no longer fail for the rest of a session if /dev/null is removed. • Agent skill discovery now resolves the user's home directory correctly on Windows. • MCP tool calls now show clearer spinner text instead of the raw wire name while arguments are still arriving. • grok inspect no longer crashes when its output is piped into a command that closes the pipe early. • Minimal mode no longer truncates a still-streaming assistant reply when thinking blocks are interleaved.

Puck

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

Grok Build CLI just got an update with v0.2.106! 🚀 Changelog v0.2.106 Features: • Added GROK_CLIPBOARD_NO_OSC52 env var to stop clipboard sequences from appearing as garbage in unsupported terminals. • Scheduled tasks can now be updated in place; one-time tasks are retired in favor of background commands. Bug Fixes: • Copies now always write a backup file so text remains recoverable when the terminal clipboard fails. • Syntax highlighting in --minimal mode is now visible on light terminals.
0:48

Grok Build CLI just got an update with v0.2.106! 🚀 Changelog v0.2.106 Features: • Added GROK_CLIPBOARD_NO_OSC52 env var to stop clipboard sequences from appearing as garbage in unsupported terminals. • Scheduled tasks can now be updated in place; one-time tasks are retired in favor of background commands. Bug Fixes: • Copies now always write a backup file so text remains recoverable when the terminal clipboard fails. • Syntax highlighting in --minimal mode is now visible on light terminals.

Puck

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

Grok Build CLI just got an update with v0.2.113! 🚀 Changelog v0.2.113 Features: • MCP servers can now be enabled or disabled directly from the CLI with `grok mcp enable ` and `grok mcp disable `. • Full plan markdown can now be copied to the clipboard with `y` during plan approval or preview. • Added support for the new SuperGrok Plus subscription tier in authentication and feature gating. • Enabled automatic recovery from repetitive loops in model output by default. Performance: • Cold start shows the UI instantly while models and settings load in the background. • Large session forks and resumes now use far less memory and avoid spikes. • Prevented thread exhaustion on high-core shared machines by limiting the workspace daemon's worker threads. Bug Fixes: • Terminal command output is no longer lost or duplicated when the gateway is unreachable. • Invalid MCP server entries in config.toml no longer prevent Grok from starting; problems are shown in `grok inspect`. • SessionEnd hooks now run on exit in non-leader TUI and headless sessions. • Paste chips now display with the correct background in inline prompts and question inputs. • Pasted content chips now behave consistently when editing answers in the question view. • Background task status now shows only elapsed duration instead of absolute timestamps. • Session lists no longer drop real sessions when the remote registry reports an outdated turn count of zero. • /loop now stores prompts that include stop conditions so recurring tasks can terminate themselves when done. • Reduced spurious warning messages for common auth and config scenarios. • Fixed conda activation (and other sourced scripts that read $@) when using persistent or login-capture shells. • Fixed stuck background-task tray rows after long foreground shell commands complete. • Agent subprocesses and idle inhibitors are now cleaned up when the parent CLI process dies unexpectedly. • Fixed truncated plans in minimal mode and improved visual separation between reasoning and output (including NO_COLOR). • Fixed credential loss across multiple grok processes sharing the same auth file. • Fixed doubled Enter and other keys on older Alacritty terminals. • Fixed false paywall messages for free-tier and unmatched users.
0:49

Grok Build CLI just got an update with v0.2.113! 🚀 Changelog v0.2.113 Features: • MCP servers can now be enabled or disabled directly from the CLI with `grok mcp enable ` and `grok mcp disable `. • Full plan markdown can now be copied to the clipboard with `y` during plan approval or preview. • Added support for the new SuperGrok Plus subscription tier in authentication and feature gating. • Enabled automatic recovery from repetitive loops in model output by default. Performance: • Cold start shows the UI instantly while models and settings load in the background. • Large session forks and resumes now use far less memory and avoid spikes. • Prevented thread exhaustion on high-core shared machines by limiting the workspace daemon's worker threads. Bug Fixes: • Terminal command output is no longer lost or duplicated when the gateway is unreachable. • Invalid MCP server entries in config.toml no longer prevent Grok from starting; problems are shown in `grok inspect`. • SessionEnd hooks now run on exit in non-leader TUI and headless sessions. • Paste chips now display with the correct background in inline prompts and question inputs. • Pasted content chips now behave consistently when editing answers in the question view. • Background task status now shows only elapsed duration instead of absolute timestamps. • Session lists no longer drop real sessions when the remote registry reports an outdated turn count of zero. • /loop now stores prompts that include stop conditions so recurring tasks can terminate themselves when done. • Reduced spurious warning messages for common auth and config scenarios. • Fixed conda activation (and other sourced scripts that read $@) when using persistent or login-capture shells. • Fixed stuck background-task tray rows after long foreground shell commands complete. • Agent subprocesses and idle inhibitors are now cleaned up when the parent CLI process dies unexpectedly. • Fixed truncated plans in minimal mode and improved visual separation between reasoning and output (including NO_COLOR). • Fixed credential loss across multiple grok processes sharing the same auth file. • Fixed doubled Enter and other keys on older Alacritty terminals. • Fixed false paywall messages for free-tier and unmatched users.

Puck

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

OH F*CK, I RAN AN ENTIRE OPERATION OFF ONE $40 SEAT! grok bot, xai's agents each with own always-on computer in the cloud, a browser and a terminal, signed into my real tools i gave six of them job titles instead of prompts research > drafting > outreach > ops > finance > support, one narrow charter each nothing overlapping i showed one of them a task once while it watched it's own screen it saved the whole flow as a named skill and now fires it the moment a matching email lands / no plugin for a tool? the bot drives it's own browser until it hits a login wall, hands me the screen, then resumes in that session, so it holds a session and never a password / xai, aug 21: grok bot now ships with all supergrok plus, cursor pro + and cursor teams plans / cursor's own pricing page lists team at $40 / user / mo, with "access to grok bot" on both team tiers / cursor pro at $20 still doen't get it pro+ is where the individual floor moved to
0:29

OH F*CK, I RAN AN ENTIRE OPERATION OFF ONE $40 SEAT! grok bot, xai's agents each with own always-on computer in the cloud, a browser and a terminal, signed into my real tools i gave six of them job titles instead of prompts research > drafting > outreach > ops > finance > support, one narrow charter each nothing overlapping i showed one of them a task once while it watched it's own screen it saved the whole flow as a named skill and now fires it the moment a matching email lands / no plugin for a tool? the bot drives it's own browser until it hits a login wall, hands me the screen, then resumes in that session, so it holds a session and never a password / xai, aug 21: grok bot now ships with all supergrok plus, cursor pro + and cursor teams plans / cursor's own pricing page lists team at $40 / user / mo, with "access to grok bot" on both team tiers / cursor pro at $20 still doen't get it pro+ is where the individual floor moved to

dunik

11,496 просмотров • 21 дней назад

THIS GUY TURNED A DESK LAMP INTO A LIVE CLAUDE CODE STATUS INDICATOR the lamp changes color based on what claude code is doing in real time when claude is thinking it's one color. when it's writing code it shifts. when it's done it changes again. when it errors out you know instantly without even looking at your screen the lamp is a moonside halo and i'm already tryna to buy one I might even buy multiple for the multiple claude sessions running in the background and turn my room into a disco if the color reflected the operational status of claude it would just be red 24/7 it could also track your usage limit. green at the start of the session, slowly fading to red as your tokens drain people are already hooking this up to their philips hue and govee setups at home
0:44

THIS GUY TURNED A DESK LAMP INTO A LIVE CLAUDE CODE STATUS INDICATOR the lamp changes color based on what claude code is doing in real time when claude is thinking it's one color. when it's writing code it shifts. when it's done it changes again. when it errors out you know instantly without even looking at your screen the lamp is a moonside halo and i'm already tryna to buy one I might even buy multiple for the multiple claude sessions running in the background and turn my room into a disco if the color reflected the operational status of claude it would just be red 24/7 it could also track your usage limit. green at the start of the session, slowly fading to red as your tokens drain people are already hooking this up to their philips hue and govee setups at home

Om Patel

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

long time no posting, here's some of the stuff we released in helium recently: - customizable keyboard shortcuts on all platforms - automatic updates on windows - frameless mode (previously zen mode), with floating sidebar, is now out of beta and included in settings by default - improved fingerprint noising: fixed the canvas noising algorithm and added protections against analysis attacks (thank you Cynthia 🐈 for your report, research, and assistance) - tab URL copying, one or multiple, formatted as a list with line breaks - manual tab hibernation, with an option to hibernate all tabs except for selected/active ones - an option to close tabs to the left (or above, in vertical layout) - redesigned toast notifications, now anchored to the active web page, and no longer blinding in dark mode - toast notification about newly opened background tabs in frameless mode (can be disabled in settings) - redesigned the infobar, it no longer looks out of place - improved QR code generation, now it's actually useful - downloads bubble is now shown instead of the full page whenever applicable - kagi search now supports reverse image search from image context menu - frameless mode animations are now smoother - better color contrast in light and dark modes - a lot of bug fixes and other minor improvements all of these changes are present in the latest version of helium. if you're using helium on windows, please update to the latest version, so your browser can be updated automatically from now on!
0:45

long time no posting, here's some of the stuff we released in helium recently: - customizable keyboard shortcuts on all platforms - automatic updates on windows - frameless mode (previously zen mode), with floating sidebar, is now out of beta and included in settings by default - improved fingerprint noising: fixed the canvas noising algorithm and added protections against analysis attacks (thank you Cynthia 🐈 for your report, research, and assistance) - tab URL copying, one or multiple, formatted as a list with line breaks - manual tab hibernation, with an option to hibernate all tabs except for selected/active ones - an option to close tabs to the left (or above, in vertical layout) - redesigned toast notifications, now anchored to the active web page, and no longer blinding in dark mode - toast notification about newly opened background tabs in frameless mode (can be disabled in settings) - redesigned the infobar, it no longer looks out of place - improved QR code generation, now it's actually useful - downloads bubble is now shown instead of the full page whenever applicable - kagi search now supports reverse image search from image context menu - frameless mode animations are now smoother - better color contrast in light and dark modes - a lot of bug fixes and other minor improvements all of these changes are present in the latest version of helium. if you're using helium on windows, please update to the latest version, so your browser can be updated automatically from now on!

Helium

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

Elon Musk just made one if the biggest moves in taking over the programming industry “SpaceX just bought Cursor for $60 billion. Do you realize how big this is? SpaceX went public — the biggest IPO in history. $75 billion raised, almost a $2 trillion valuation and the first thing to do with that money? Buy the most popular AI coding tool on the planet. Here's why that changes everything. Elon now owns 3 layers: the compute, Colossus data centers, the models, Grok through xAI, and now the tool that developers actually use every day. It's the full stack. And here's what makes Cursor different from Claude Code or Codex. Cursor is model agnostic. You can run Claude in it, GPT, Gemini, whatever model you want. It's not locked to any one company, and now it has SpaceX's resources behind it. Cursor said they were bottlenecked by compute. Well, that bottleneck has just been removed. $4 billion in annual revenue, over half the Fortune 500 already uses it, and now it's backed by a $2 trillion company. OpenAI has Codex, Anthropic has Claude Code, and now Elon has Cursor.” Let me break this down in simple terms Elon Musk now controls more of the full AI picture: - Massive computers, power (data centers like Colossus) - Smart AI models (Grok from xAI) - The actual tool millions of developers use every day (Cursor) For every day users this means Faster and smarter apps and websites in the future. More developers using powerful AI tools means new apps, games, websites, and features get built quicker and cheaper. This means better video games, smoother streaming, smarter phone apps and better programs For Developers they can describe what they want in plain English (“make a feature that does X”) and the AI handles more of the heavy lifting
2:13

Elon Musk just made one if the biggest moves in taking over the programming industry “SpaceX just bought Cursor for $60 billion. Do you realize how big this is? SpaceX went public — the biggest IPO in history. $75 billion raised, almost a $2 trillion valuation and the first thing to do with that money? Buy the most popular AI coding tool on the planet. Here's why that changes everything. Elon now owns 3 layers: the compute, Colossus data centers, the models, Grok through xAI, and now the tool that developers actually use every day. It's the full stack. And here's what makes Cursor different from Claude Code or Codex. Cursor is model agnostic. You can run Claude in it, GPT, Gemini, whatever model you want. It's not locked to any one company, and now it has SpaceX's resources behind it. Cursor said they were bottlenecked by compute. Well, that bottleneck has just been removed. $4 billion in annual revenue, over half the Fortune 500 already uses it, and now it's backed by a $2 trillion company. OpenAI has Codex, Anthropic has Claude Code, and now Elon has Cursor.” Let me break this down in simple terms Elon Musk now controls more of the full AI picture: - Massive computers, power (data centers like Colossus) - Smart AI models (Grok from xAI) - The actual tool millions of developers use every day (Cursor) For every day users this means Faster and smarter apps and websites in the future. More developers using powerful AI tools means new apps, games, websites, and features get built quicker and cheaper. This means better video games, smoother streaming, smarter phone apps and better programs For Developers they can describe what they want in plain English (“make a feature that does X”) and the AI handles more of the heavy lifting

Wall Street Apes

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

Quick demo of how I use session to session messaging in Claude Code + Ghostty (Save this and try it in your own workflows) 1- I always start with a regular session and a panel running claude agents 2- The first session becomes the orchestrator. It creates the initial context, then distributes the work across other sessions using forks 3- Each fork starts with that context + a prompt telling it what to work on 4- I rename each session with ctrl + r to keep things organized and make it easy to message them from the main session 5- Using @ I send messages to the sessions that are running and ask them to report their task status back, so the main session always knows what everyone is working on This way, I only need 2 or 3 panels open and can switch between tasks as needed The days of opening endless terminal panels and running Claude Code 100 times just to look productive are over! What we need now is ORCHESTATION one main session coordinating everything through session messaging + Agent View And the key is context, build it in the main session first, then fork from there That’s what makes the entire workflow click
0:28

Quick demo of how I use session to session messaging in Claude Code + Ghostty (Save this and try it in your own workflows) 1- I always start with a regular session and a panel running claude agents 2- The first session becomes the orchestrator. It creates the initial context, then distributes the work across other sessions using forks 3- Each fork starts with that context + a prompt telling it what to work on 4- I rename each session with ctrl + r to keep things organized and make it easy to message them from the main session 5- Using @ I send messages to the sessions that are running and ask them to report their task status back, so the main session always knows what everyone is working on This way, I only need 2 or 3 panels open and can switch between tasks as needed The days of opening endless terminal panels and running Claude Code 100 times just to look productive are over! What we need now is ORCHESTATION one main session coordinating everything through session messaging + Agent View And the key is context, build it in the main session first, then fork from there That’s what makes the entire workflow click

Daniel San

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

Look ma new Codex Updates! 0.119.0 and 0.120.0 are here. And with it, a HUGE number of quality of life updates and bug fixes! > Hooks now render in a dedicated live area above the composer. They only persist when they have output, so your terminal stays clean. If you're running PreToolUse or PostToolUse hooks, this is a huge readability win. > Hooks are now available again on Windows > CTRL+O copies the last agent output. Small but clutch when you're pulling a code block into another file or chat. > New statusline option: context usage as a graphical bar instead of a percentage. Easier to glance at mid-session when you're trying to gauge how much runway you have left. > Zellij support is here with no scrollback bugs. If you've been stuck on tmux just because Codex was broken in Zellij, you're free now (shout out Felipe Coury 🦀) > Memory extensions just landed. The consolidation agent can now discover plugin folders under memories_extensions/ and read their instructions.md to learn how to interpret new memory sources. Drop a folder in, give it guidance, and the agent picks it up automatically during summarization. No core code changes needed. This is the first real extension point for Codex's memory system, and it opens the door for third-party memory plugins. > Did you know, you can /rename a thread? But what's really cool about that is, after you rename it, you can resume it with the same name, no more UUIDs. codex resume mynewapp or directly from the TUI: /resume mynewapp > Multi agents v2 got an update to tool descriptions More reliable multi agent environments and inter agent communication > You can now enable TUI notifications whether Codex is in focus or not. Modify this in your config: [tui] notification_condition = "always" > MAJOR overhaul to Codex MCP functionality: 1. Codex Tool Search now works with custom MCP servers, so tools can be searched and deferred instead of all being exposed up front. 2. Custom MCP servers can now trigger elicitations, meaning they can stop and ask for user approval or input mid-flow. 3. MCP tool results now preserve richer metadata, which improves app/UI handoff behavior. 4. Codex can now read MCP resources directly, letting apps return resource URIs that the client can actually open. 5. File params for Codex Apps are smoother: local file paths can be uploaded and remapped automatically. 6. Plugin cache refresh and fallback sync behavior are more reliable, especially for custom and curated plugins. > Composer and chat behavior smoother overall, resize bugs remain though. > Realtime v2 got several significant improvements as well. > You're still reading? What a legend. 🫶 npm i -g @openai/codex to update
0:36

Look ma new Codex Updates! 0.119.0 and 0.120.0 are here. And with it, a HUGE number of quality of life updates and bug fixes! > Hooks now render in a dedicated live area above the composer. They only persist when they have output, so your terminal stays clean. If you're running PreToolUse or PostToolUse hooks, this is a huge readability win. > Hooks are now available again on Windows > CTRL+O copies the last agent output. Small but clutch when you're pulling a code block into another file or chat. > New statusline option: context usage as a graphical bar instead of a percentage. Easier to glance at mid-session when you're trying to gauge how much runway you have left. > Zellij support is here with no scrollback bugs. If you've been stuck on tmux just because Codex was broken in Zellij, you're free now (shout out Felipe Coury 🦀) > Memory extensions just landed. The consolidation agent can now discover plugin folders under memories_extensions/ and read their instructions.md to learn how to interpret new memory sources. Drop a folder in, give it guidance, and the agent picks it up automatically during summarization. No core code changes needed. This is the first real extension point for Codex's memory system, and it opens the door for third-party memory plugins. > Did you know, you can /rename a thread? But what's really cool about that is, after you rename it, you can resume it with the same name, no more UUIDs. codex resume mynewapp or directly from the TUI: /resume mynewapp > Multi agents v2 got an update to tool descriptions More reliable multi agent environments and inter agent communication > You can now enable TUI notifications whether Codex is in focus or not. Modify this in your config: [tui] notification_condition = "always" > MAJOR overhaul to Codex MCP functionality: 1. Codex Tool Search now works with custom MCP servers, so tools can be searched and deferred instead of all being exposed up front. 2. Custom MCP servers can now trigger elicitations, meaning they can stop and ask for user approval or input mid-flow. 3. MCP tool results now preserve richer metadata, which improves app/UI handoff behavior. 4. Codex can now read MCP resources directly, letting apps return resource URIs that the client can actually open. 5. File params for Codex Apps are smoother: local file paths can be uploaded and remapped automatically. 6. Plugin cache refresh and fallback sync behavior are more reliable, especially for custom and curated plugins. > Composer and chat behavior smoother overall, resize bugs remain though. > Realtime v2 got several significant improvements as well. > You're still reading? What a legend. 🫶 npm i -g @openai/codex to update

am.will

742,455 просмотров • 5 месяцев назад

Introducing 🌸 Kanna – a web ui for Claude Code + Codex running right in your browser (and my first open source project!) It's sort of like if Claude Code & Codex had a baby with a much better ui/ux 💅 Here's what makes Kanna special: 🔀 One-click switch between Claude Code / Codex 🌐 Runs in your browser on localhost - no app switching 🧩 Embedded split terminals, persisted between chats with a beautiful horizontal scrolling UX 📁 Full project file browser built in, embedded editor coming soon too. Coming soon: 🔒 End-to-end encryption + remote access via reverse proxy 🌿 Git integration, diffs, PRs 🧱 Plugins I wanted to replace switching between cursor, the github app, browser & (most recently) the codex app. The browser is hardest to recreate yet also the most flexible so it makes sense to build in the browser itself. Install in 5 seconds: bun install -g kanna-code then just type: kanna Kanna is purely a ui/ux layer. It uses your existing CLIs, is 100% compliant & no data ever leaves your machine. If running claude or codex in your terminal works, kanna works too. Kanna natively supports every tool call, model, reasoning effort, fast mode, plan mode, compaction, user questions, web searching, skills, agents, mcps, everything. There are a few libraries that do this but none that I found as comprehensive. All feedback welcome!
1:38

Introducing 🌸 Kanna – a web ui for Claude Code + Codex running right in your browser (and my first open source project!) It's sort of like if Claude Code & Codex had a baby with a much better ui/ux 💅 Here's what makes Kanna special: 🔀 One-click switch between Claude Code / Codex 🌐 Runs in your browser on localhost - no app switching 🧩 Embedded split terminals, persisted between chats with a beautiful horizontal scrolling UX 📁 Full project file browser built in, embedded editor coming soon too. Coming soon: 🔒 End-to-end encryption + remote access via reverse proxy 🌿 Git integration, diffs, PRs 🧱 Plugins I wanted to replace switching between cursor, the github app, browser & (most recently) the codex app. The browser is hardest to recreate yet also the most flexible so it makes sense to build in the browser itself. Install in 5 seconds: bun install -g kanna-code then just type: kanna Kanna is purely a ui/ux layer. It uses your existing CLIs, is 100% compliant & no data ever leaves your machine. If running claude or codex in your terminal works, kanna works too. Kanna natively supports every tool call, model, reasoning effort, fast mode, plan mode, compaction, user questions, web searching, skills, agents, mcps, everything. There are a few libraries that do this but none that I found as comprehensive. All feedback welcome!

Jake Mor

43,379 просмотров • 5 месяцев назад

Anthropic just released a talk on building headless automation with Claude Code. Presented by Sid Bidasaria, Member of Technical Staff at Anthropic live at Code with Claude on May 22, 2025 in San Francisco. Here is what the talk covers. Headless mode lets you run Claude Code without a person actively typing prompts from inside an automated script. Instead of a live session, a script calls Claude with a pre-written instruction using the -p flag. This opens the door for Claude Code to become a piece of a much larger, automated process. In plain terms: Claude Code stops being a tool you use and starts being a service that runs on its own. What this unlocks: Scheduled tasks: Run Claude Code on a cron schedule without anyone at a keyboard. Fix linting errors across an entire codebase. Automatically. Overnight. CI/CD integration: Trigger Claude Code as a step in your build process. Open a PR. Claude reviews it, flags issues, and pushes fixes before a human ever looks at it. GitHub automation: A project manager comments "Claude fix this" on a GitHub issue. Claude reads the request, finds the code, writes the fix, and opens the PR. Multi-machine workflows: One orchestrator dispatches tasks to multiple Claude Code instances running in parallel across different repos simultaneously. When you combine headless mode, hooks, and GitHub Actions, development teams can automate tasks that usually eat up significant time freeing senior engineers to focus on architectural problems while Claude handles the repetitive ones. If you use Claude Code for anything beyond single sessions this talk is worth 20 minutes of your time.
20:58

Anthropic just released a talk on building headless automation with Claude Code. Presented by Sid Bidasaria, Member of Technical Staff at Anthropic live at Code with Claude on May 22, 2025 in San Francisco. Here is what the talk covers. Headless mode lets you run Claude Code without a person actively typing prompts from inside an automated script. Instead of a live session, a script calls Claude with a pre-written instruction using the -p flag. This opens the door for Claude Code to become a piece of a much larger, automated process. In plain terms: Claude Code stops being a tool you use and starts being a service that runs on its own. What this unlocks: Scheduled tasks: Run Claude Code on a cron schedule without anyone at a keyboard. Fix linting errors across an entire codebase. Automatically. Overnight. CI/CD integration: Trigger Claude Code as a step in your build process. Open a PR. Claude reviews it, flags issues, and pushes fixes before a human ever looks at it. GitHub automation: A project manager comments "Claude fix this" on a GitHub issue. Claude reads the request, finds the code, writes the fix, and opens the PR. Multi-machine workflows: One orchestrator dispatches tasks to multiple Claude Code instances running in parallel across different repos simultaneously. When you combine headless mode, hooks, and GitHub Actions, development teams can automate tasks that usually eat up significant time freeing senior engineers to focus on architectural problems while Claude handles the repetitive ones. If you use Claude Code for anything beyond single sessions this talk is worth 20 minutes of your time.

Elias

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

pov: you're running 15 loops across in glm 5.2 in opencode, codex, claude, amp or pi and have no idea which one needs you, bring em all to opensessions cmux, superset - cool ideas, but i got tired of blank screens, glitchy terminals, and macos-only apps i just wanted to know when my agents finish, fail, or need me so i built a tmux sidebar. now re-written in rust with worktree support runs inside your actual terminal. on any OS. - agents status' across all your projects at a glance - forwarded ports per project - live threads across amp, claude code, codex, opencode no electron. no blank panes. no new app. extremely fast and light. open source.
1:16

pov: you're running 15 loops across in glm 5.2 in opencode, codex, claude, amp or pi and have no idea which one needs you, bring em all to opensessions cmux, superset - cool ideas, but i got tired of blank screens, glitchy terminals, and macos-only apps i just wanted to know when my agents finish, fail, or need me so i built a tmux sidebar. now re-written in rust with worktree support runs inside your actual terminal. on any OS. - agents status' across all your projects at a glance - forwarded ports per project - live threads across amp, claude code, codex, opencode no electron. no blank panes. no new app. extremely fast and light. open source.

Palani — oss/acc

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

I'm open-sourcing tws, the tool I've been using for the last few months to organize my engineering work. I've always been a terminal-first engineer; tmux + nvim has been my default. Then AI coding agents arrived and shifted what I needed from that setup. Running several Claude Code and Codex sessions in parallel, the flat tmux session list stopped being enough. So I built tws to fit how I actually work now. It's built on top of tmux, no reinvented wheel. You keep all of tmux's power and flexibility underneath. On top of that, it gives you: - Threads: an abstract organizational layer above tmux sessions, so related work groups together instead of sitting in a flat list - Notes: quick markdown notes attached to each thread or session, kept right next to your work - Fast switching: fuzzy finding, recent-session jumps, and keyboard-driven navigation between everything - Agents view: every Claude Code / Codex session running across your projects in one place, with the ability to pin the ones you keep coming back to Fully configurable — themes, palette, keybindings — via a TOML file. If tmux + terminal isn't your setup, this probably isn't for you. But if you like working from terminal, you might like it. It's been the core piece of how I work for a while now. Github:
0:20

I'm open-sourcing tws, the tool I've been using for the last few months to organize my engineering work. I've always been a terminal-first engineer; tmux + nvim has been my default. Then AI coding agents arrived and shifted what I needed from that setup. Running several Claude Code and Codex sessions in parallel, the flat tmux session list stopped being enough. So I built tws to fit how I actually work now. It's built on top of tmux, no reinvented wheel. You keep all of tmux's power and flexibility underneath. On top of that, it gives you: - Threads: an abstract organizational layer above tmux sessions, so related work groups together instead of sitting in a flat list - Notes: quick markdown notes attached to each thread or session, kept right next to your work - Fast switching: fuzzy finding, recent-session jumps, and keyboard-driven navigation between everything - Agents view: every Claude Code / Codex session running across your projects in one place, with the ability to pin the ones you keep coming back to Fully configurable — themes, palette, keybindings — via a TOML file. If tmux + terminal isn't your setup, this probably isn't for you. But if you like working from terminal, you might like it. It's been the core piece of how I work for a while now. Github:

Yusuf

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

CLAUDE + CURSOR + REPLIT = MAGIC (FULL VIDEO TUTORIAL) You can now write create complex web apps with just english (No copy - paste) using the BEST AI Code generation tool on the market - Cursor. The only problem with cursor for a coding beginner like me, is that its not that easy to deploy web apps. Well, Replit ⠕ makes deploying web apps and creating templates incredibly easy. In this video goes over how to sync Cursor and Replit. And then using our new template we made an AI version of Trello by Atlassian in like 6 or 7 cursor composer prompts. --------------------- In this video: 00:00 - Intro 04:08 - Syncing Cursor and Replit 07:40 - setting up Firebase 10:27 - Using Cursor and Replit to Create Trello Front End 19:41 - Setting up Backend API endpoint (we will make dedicated video on this soon w/template) 21:09 - Adding AI features to Trello!
27:19

CLAUDE + CURSOR + REPLIT = MAGIC (FULL VIDEO TUTORIAL) You can now write create complex web apps with just english (No copy - paste) using the BEST AI Code generation tool on the market - Cursor. The only problem with cursor for a coding beginner like me, is that its not that easy to deploy web apps. Well, Replit ⠕ makes deploying web apps and creating templates incredibly easy. In this video goes over how to sync Cursor and Replit. And then using our new template we made an AI version of Trello by Atlassian in like 6 or 7 cursor composer prompts. --------------------- In this video: 00:00 - Intro 04:08 - Syncing Cursor and Replit 07:40 - setting up Firebase 10:27 - Using Cursor and Replit to Create Trello Front End 19:41 - Setting up Backend API endpoint (we will make dedicated video on this soon w/template) 21:09 - Adding AI features to Trello!

Riley Brown

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

Cursor vs Claude Code (day 3 of 30) today I re-tested Conductor and I don't want to overhype this but... what the actual fook 😮 this thing is amazing! closest things to the "perfect workflow" I have seen in a long time, and it's something I could see myself use full-time it's so minimal and the polar opposite of Cursor but it has all the essentials → Claude Code + Codex subscriptions (= unlimited usage) → great integration with Claude Code's plan mode → multiple tabs with multiple agents at the same time → can use multiple models, not just one → great file tree and diff viewer → best git worktree support I've ever seen there's honestly so much more, like a dedicated "review" button (which you can pair to your favorite review model, e.g. gpt-5.2-extra-high), buttons to create and merge pull requests, to launch your dev server, ... this solves literally EVERY fault I can think of when using Claude Code and/or Codex, combining both into one easy UX that not only does everything the tools can do, but actually adds useful stuff on top just 6 months ago I couldn't have dreamt about any this and the wildest part is that IT IS FREE (I'd literally pay for this UX lol) first time I'm genuinely enjoying myself since starting this challenge not saying it's a full Cursor replacement yet, it obviously isn't for a lot of people (no browser, no debug mode, no code indexing, etc) ... but this is the closest thing I've seen yet 👀 follow for day 4!
5:56

Cursor vs Claude Code (day 3 of 30) today I re-tested Conductor and I don't want to overhype this but... what the actual fook 😮 this thing is amazing! closest things to the "perfect workflow" I have seen in a long time, and it's something I could see myself use full-time it's so minimal and the polar opposite of Cursor but it has all the essentials → Claude Code + Codex subscriptions (= unlimited usage) → great integration with Claude Code's plan mode → multiple tabs with multiple agents at the same time → can use multiple models, not just one → great file tree and diff viewer → best git worktree support I've ever seen there's honestly so much more, like a dedicated "review" button (which you can pair to your favorite review model, e.g. gpt-5.2-extra-high), buttons to create and merge pull requests, to launch your dev server, ... this solves literally EVERY fault I can think of when using Claude Code and/or Codex, combining both into one easy UX that not only does everything the tools can do, but actually adds useful stuff on top just 6 months ago I couldn't have dreamt about any this and the wildest part is that IT IS FREE (I'd literally pay for this UX lol) first time I'm genuinely enjoying myself since starting this challenge not saying it's a full Cursor replacement yet, it obviously isn't for a lot of people (no browser, no debug mode, no code indexing, etc) ... but this is the closest thing I've seen yet 👀 follow for day 4!

Robin Ebers

40,764 просмотров • 8 месяцев назад

I just compared Claude Code vs Codex vs Cursor CLI The task was to build a Next.js app with Tailwind 4 and shadcn components to collect customer feedback and showcase it with a widget. I gave all three the same prompt and let them go for 30 minutes to see what they came up with. Claude Code with Opus 4.1 Even though I told it to set up the app in the existing project folder, it tried to create a directory for it. After I interrupted and told it not to do that, it built a demo form and landing page with no errors. I had to ask it to make the demo interactive so users could submit a testimonial and preview it. The landing page looked like AI and was pretty basic, but it worked and it was done in a fraction of the time of the others. Total tokens used: 33k Codex with GPT-5 At the end of the 30 minutes I just could not get Codex to produce a working app. It got stuck in a loop of not being able to set up Tailwind 4 and despite many, MANY, attempts, I ended up with a "failed to compile" error. Total tokens used: 102k Cursor Agent with GPT-5 This was the slowest agent by far and a couple of times I actually thought it got stuck in a loop and was close to Ctrl+C'ing to cancel it. The TUI is really nice though, especially how it shows diffs and it did eventually build a working app (after one or two slight errors that needed fixing) The demo was interactive and it had a very minimal design that looked bare but also a lot less like an "AI generated" app than the Opus 4.1 design. It also wasn't too chatty and just did what it needed to do! Code quality was on a par with Opus 4.1, but it did use 5.5x as many tokens to get there. Still cheaper than Opus on a direct comparison but not when you factor in a Claude Code Max subscription. Total tokens: 188k I'll be able to do a proper comparison and record some videos when I'm back from holiday but for now, Opus is still the more capable model out of the box and Claude Code is the more complete CLI product. It will be interesting to see how Cursor evolve their CLI though with commands and subagents because I think with GPT-5 they have a real shot at providing competition for Claude Code if they can optimise output to get similar quality with less tokens. Jump to 0:40 in the video to see the two apps. Which do you think is which? ;)
1:18

I just compared Claude Code vs Codex vs Cursor CLI The task was to build a Next.js app with Tailwind 4 and shadcn components to collect customer feedback and showcase it with a widget. I gave all three the same prompt and let them go for 30 minutes to see what they came up with. Claude Code with Opus 4.1 Even though I told it to set up the app in the existing project folder, it tried to create a directory for it. After I interrupted and told it not to do that, it built a demo form and landing page with no errors. I had to ask it to make the demo interactive so users could submit a testimonial and preview it. The landing page looked like AI and was pretty basic, but it worked and it was done in a fraction of the time of the others. Total tokens used: 33k Codex with GPT-5 At the end of the 30 minutes I just could not get Codex to produce a working app. It got stuck in a loop of not being able to set up Tailwind 4 and despite many, MANY, attempts, I ended up with a "failed to compile" error. Total tokens used: 102k Cursor Agent with GPT-5 This was the slowest agent by far and a couple of times I actually thought it got stuck in a loop and was close to Ctrl+C'ing to cancel it. The TUI is really nice though, especially how it shows diffs and it did eventually build a working app (after one or two slight errors that needed fixing) The demo was interactive and it had a very minimal design that looked bare but also a lot less like an "AI generated" app than the Opus 4.1 design. It also wasn't too chatty and just did what it needed to do! Code quality was on a par with Opus 4.1, but it did use 5.5x as many tokens to get there. Still cheaper than Opus on a direct comparison but not when you factor in a Claude Code Max subscription. Total tokens: 188k I'll be able to do a proper comparison and record some videos when I'm back from holiday but for now, Opus is still the more capable model out of the box and Claude Code is the more complete CLI product. It will be interesting to see how Cursor evolve their CLI though with commands and subagents because I think with GPT-5 they have a real shot at providing competition for Claude Code if they can optimise output to get similar quality with less tokens. Jump to 0:40 in the video to see the two apps. Which do you think is which? ;)

Ian Nuttall

195,173 просмотров • 1 год назад

Claude Code is the OpenClaw alternative you already had. I've been telling people this in person for three months. Now it's a piece on Every 📧. When OpenClaw was at peak hype a few months ago, everyone was going crazy over it — for good reasons. But almost nobody made the obvious comparison: Claude Code already does the thing you love about OpenClaw. In a lot of cases, better. Here's why people missed it. You have to understand the difference between a model and a harness. OpenClaw, at the end of the day, is just a harness on top of AI models. And Claude Code is too — it just got marketed as a coding tool, an alternative to Cursor. Until Cowork launched, almost nobody looked at it as a tool for non-programmers. Dan Shipper 📧 was one of the earliest to make that claim, and he was damn right. Let Claude Code run from the home folder of your computer with free access, and you get exactly what made OpenClaw exciting. Instead of just arguing it, here's a video walkthrough of a couple of my AI employees i built on the Claude Code harness. And here's the full article:
8:31

Claude Code is the OpenClaw alternative you already had. I've been telling people this in person for three months. Now it's a piece on Every 📧. When OpenClaw was at peak hype a few months ago, everyone was going crazy over it — for good reasons. But almost nobody made the obvious comparison: Claude Code already does the thing you love about OpenClaw. In a lot of cases, better. Here's why people missed it. You have to understand the difference between a model and a harness. OpenClaw, at the end of the day, is just a harness on top of AI models. And Claude Code is too — it just got marketed as a coding tool, an alternative to Cursor. Until Cowork launched, almost nobody looked at it as a tool for non-programmers. Dan Shipper 📧 was one of the earliest to make that claim, and he was damn right. Let Claude Code run from the home folder of your computer with free access, and you get exactly what made OpenClaw exciting. Instead of just arguing it, here's a video walkthrough of a couple of my AI employees i built on the Claude Code harness. And here's the full article:

Nityesh

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

How I have Claude automate anything I do on my computer just by showing it: I use the free Clips app and hit record to start recording. Then I just do the action - like navigating to Rippling and approving any unapproved time off - and I’ll often just talk out loud as I do it explaining any add’l details like I would when showing a human. The Clips app captures everything on your screen and everything you say, and transforms it into a format Claude can “see and hear”. You'll then get a link that you can easily share with Claude (or humans too). I’ll paste it to Claude and say something like, "automate this for me every day at 8:00 AM." The link has special metadata that agents like Claude can discover. It exposes APIs to see the full transcript with timestamps and grab screenshots of what was on your screen at any of those timestamps. Once it's created the routine, you can go to the Routines tab in Claude Code desktop app. This also works with the CLI, Claude Cowork, Codex etc. You’ll see your new routine there, and you can just hit Run Now to have it start running it. Video attached shows this step by step. The Clips apps is free and open source - I’ll link to it and the source code in the thread.
1:54

How I have Claude automate anything I do on my computer just by showing it: I use the free Clips app and hit record to start recording. Then I just do the action - like navigating to Rippling and approving any unapproved time off - and I’ll often just talk out loud as I do it explaining any add’l details like I would when showing a human. The Clips app captures everything on your screen and everything you say, and transforms it into a format Claude can “see and hear”. You'll then get a link that you can easily share with Claude (or humans too). I’ll paste it to Claude and say something like, "automate this for me every day at 8:00 AM." The link has special metadata that agents like Claude can discover. It exposes APIs to see the full transcript with timestamps and grab screenshots of what was on your screen at any of those timestamps. Once it's created the routine, you can go to the Routines tab in Claude Code desktop app. This also works with the CLI, Claude Cowork, Codex etc. You’ll see your new routine there, and you can just hit Run Now to have it start running it. Video attached shows this step by step. The Clips apps is free and open source - I’ll link to it and the source code in the thread.

Steve (Builder.io)

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

My whole company runs on skills I bundled into a GitHub repo. Here's how to build the same thing for your team: - Put your skills in a GitHub repo - Get Claude to write the couple of JSON files that make it readable as a plugin - In Claude Code, type /plugin, go to marketplaces, add marketplace, paste your repo URL - Split the plugins by department, so your copywriter isn't installing the finance skills It works in Codex too. I've got the same team skills installed there and I use them the same way. Now when I build something like my Notion formatting skill, I add it to the repo and it lands on everyone's Claude and Codex. If someone wrecks a skill, we roll it back to an older version. The key is enabling auto-update, so when someone improves a skill everyone benefits. I don't have a clue how the JSON works. I got Claude to set the whole thing up for me. Start with one skill and before you know it your whole team will be AI pilled.
5:18

My whole company runs on skills I bundled into a GitHub repo. Here's how to build the same thing for your team: - Put your skills in a GitHub repo - Get Claude to write the couple of JSON files that make it readable as a plugin - In Claude Code, type /plugin, go to marketplaces, add marketplace, paste your repo URL - Split the plugins by department, so your copywriter isn't installing the finance skills It works in Codex too. I've got the same team skills installed there and I use them the same way. Now when I build something like my Notion formatting skill, I add it to the repo and it lands on everyone's Claude and Codex. If someone wrecks a skill, we roll it back to an older version. The key is enabling auto-update, so when someone improves a skill everyone benefits. I don't have a clue how the JSON works. I got Claude to set the whole thing up for me. Start with one skill and before you know it your whole team will be AI pilled.

The Startup Ideas Podcast (SIP) 🧃

19,532 просмотров • 26 дней назад

Introducing my newest app, TethrX, made with Grok 4.5 to access Grok Build on your phone. TethrX connects to Grok Build running on your own computer, so you can start a task from anywhere, follow Grok's reasoning as it works, approve every command before it runs, and review the code it writes. Your code never leaves your machine. The public TestFlight is now open, and a demonstration is below. You pair your phone by scanning a QR code, either on your local network or from anywhere through Tailscale. From there TethrX streams Grok's reasoning, tool calls, command output and file changes as they happen, and asks your approval before anything runs. Plan mode lets you read the plan before the work begins. When a task finishes you can review exactly what changed. TethrX lists the modified files in your project, shows a diff for each one, and lets you commit or discard the work without leaving your phone. The app supports slash commands, including /compact and any skills you have installed, along with voice dictation, queued messages and reusable prompts. Sessions can be searched and organised into folders, and you can pair several computers and switch between them. Siri can start a task or tell you what Grok is doing without opening the app, a home screen widget shows whether Grok is working, and a Live Activity tracks progress on your lock screen and Dynamic Island. Every session reports its context window, token usage and cost, the app can be locked behind Face ID, and your computer is kept awake for as long as a task is running. TethrX requires Grok Build installed and signed in on your computer, together with Node.js 20 or newer. A single command starts the bridge: npx tethrx-bridge TethrX is open source under the Apache License 2.0. Both the iOS client and the local bridge are available here: Grok 4.5 helped a lot, thanks to SpaceXAI for making Grok 4.5 exceptional.
0:27

Introducing my newest app, TethrX, made with Grok 4.5 to access Grok Build on your phone. TethrX connects to Grok Build running on your own computer, so you can start a task from anywhere, follow Grok's reasoning as it works, approve every command before it runs, and review the code it writes. Your code never leaves your machine. The public TestFlight is now open, and a demonstration is below. You pair your phone by scanning a QR code, either on your local network or from anywhere through Tailscale. From there TethrX streams Grok's reasoning, tool calls, command output and file changes as they happen, and asks your approval before anything runs. Plan mode lets you read the plan before the work begins. When a task finishes you can review exactly what changed. TethrX lists the modified files in your project, shows a diff for each one, and lets you commit or discard the work without leaving your phone. The app supports slash commands, including /compact and any skills you have installed, along with voice dictation, queued messages and reusable prompts. Sessions can be searched and organised into folders, and you can pair several computers and switch between them. Siri can start a task or tell you what Grok is doing without opening the app, a home screen widget shows whether Grok is working, and a Live Activity tracks progress on your lock screen and Dynamic Island. Every session reports its context window, token usage and cost, the app can be locked behind Face ID, and your computer is kept awake for as long as a task is running. TethrX requires Grok Build installed and signed in on your computer, together with Node.js 20 or newer. A single command starts the bridge: npx tethrx-bridge TethrX is open source under the Apache License 2.0. Both the iOS client and the local bridge are available here: Grok 4.5 helped a lot, thanks to SpaceXAI for making Grok 4.5 exceptional.

Myrhe𝕩

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