与「Bugs」相关的搜索结果

xAI has been shipping Grok Build updates non-stop If you have not been keeping track, here is what xAI has rolled out up to v0.2.11: New commands & core features → Integrated 𝕏 search and much faster web search → Added /export, /login, /usage, and /config-agents → Added an interactive read-file viewer with PowerPoint text extraction → Added Always-approve mode to streamline permissions → Auto-installed shell completions for bash, zsh, and fish Expanded platform support → Added Windows ARM64 and macOS x86_64 support → Improved terminal support across Warp, VTE-based terminals, JetBrains, and legacy Windows Console → Fixed copy/paste issues across Linux Wayland, WSL, and Windows Agent & context improvements → Subagents now share the terminal backend, scheduler, and monitor across sessions → Added proactive system reminders and laziness detectors to keep the model on task → Improved context compaction and memory usage for chat history → Auto-backgrounds long-running bash-mode commands triggered via ! UX, media & UI upgrades → Boosted terminal video playback to 30fps → Added multi-image paste, drag-and-drop, and temporary macOS screenshots → Added instant loading indicators when switching models → Improved clickable markdown links and rendered links inside table cells → Smoother plan-mode controls and absolute line numbers in the edit panel Stability & fixes → Increased default retry budget to ~5 minutes → Increased Unix ulimits to prevent crashes → Hardened background tools to handle timeouts and self-kills → Fixed rendering bugs across UTF-8 output, large monitors, Windows contrast, and more xAI is moving insanely fast Grok Build is going from early CLI to a serious agentic coding environment very quickly

Why is the creator of OpenCode pretty skeptical about AI productivity gains, and the hype around AI? A very conversation @thdxr (and lots of truth bombs:) Timestamps: 00:00 Intro 07:03 Dax’s path into tech 09:04 Early startup experience 13:16 Getting involved with open source 16:13 OpenCode 23:17 Anthropic banning OpenCode 30:34 From terminal to GUI 32:34 OpenCode’s business model 36:33 Why inference is profitable 39:11 GPU bottlenecks 40:54 AI hype 45:50 AI spending 48:47 Dax’s memo 55:41 Dax’s skepticism of predictions 58:58 Engineering culture at OpenCode 1:02:38 How building works at OpenCode 1:05:36 Taste and quality 1:11:32 Dax’s work setup 1:12:35 The role of engineers and EMs 1:15:50 Advice for engineers 1:18:12 Book recommendation Brought to you by: • @AntithesisHQ – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages • @WorkOS – everything you need to make your app enterprise ready • @turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable Three interesting thoughts from Dax: 1. No AI-native coding agent company is “winning” by being better with AI. Dax says that none of OpenCode’s competitors are crushing them, and that nobody is using AI so well that others cannot compete. 2. Most software engineers profit from AI as time gained, not increased output — unless you change incentives! Dax says the natural way for software engineers to “cash out” their AI tooling gains is with time savings, by doing the same work as before, but faster. Until compensation and motivation structures change, most teams should expect output to stay flat while engineers go home earlier. There’s nothing wrong with this, but AI vendors sell a different outcome to CFOs: increased output. 3. AI code generation mutes the “guilt” of doing the wrong thing, but this builds up tech debt. Pre-AI, writing a hack felt bad, the second time it felt really bad, and by the third time you’d often just refactor in order to fix up the code. Now, the agent hides the hack, which skews devs’ judgment and results in less tech debt being cleaned up.

Seeing green shoots on day 1 of a highly experimental and completely novel new technology makes me happy. As to be expected with a mainnet beta on day 1 there's some bugs. But the dev running the sole "dealer" means often waiting between hands. Thoughtful scaling with baby steps.

LATEST: ⚡️ XRP Ledger will roll out the fixCleanup3_1_3 upgrade on Wednesday, deleting expired NFT offers automatically and patching bugs in domain settings, vault withdrawals, and loan accounting.

Bug fixes shipping to Grok Build 0.1.219 (release notes will be available in the TUI) - fixing usage limit bugs with prompt caching - fix layout-shifted chars in kitty terminal - replace Shift+Enter w/ Alt-Enter on VTE-based terminals (GNOME Terminal, Ptyxis, kgx, Tilix, etc.) - default expand (search_replace, write_file, run_terminal_command) calls on scrollback - mixed prose + URL paste no longer silently drops prose - set_images byte: length collision losing chips - make multi-line markdown link URLs clickable across word-wrap - clear selection when expanding truncated group - remove read_file duplicate-read check that breaks after compaction

ITZY <Motto (Remixes)> Released Online : 🎧 Melon 🎧 Genie 🎧 Bugs 🎧 FLO 🎧 VIBE #ITZY# #MIDZY# @ITZYofficial #ITZY_Motto#

Bug fixes shipping to Grok Build (release notes will be available in the TUI) 0.1.214 - Rolling out X search and a much faster web-search (we plan to complete this by EOD) - Windows rendering bugs fix on powershell - Fix arrow-up keybinding in modals - Fix non-vim mode keybinding hints - Fix Cmd+Click on wrapped links - Filter out sessions that had no user input from picker - Support hookSpecificOutput.tool_input override - Prevent crash on exit when there are MCP servers with expiring tokens - Auto-refresh Skills when plugins change

Creator of C++, Bjarne Stroustrup: AI-generated code isn't ready — it generates more bugs, more bloat, more security holes, and is nearly impossible to validate "senior developers are already retiring rather than deal with it" The problem is that even a small prompt change can shift the entire codebase in unpredictable ways

‼️🚨 BREAKING: Cloudflare's CISO just published what Anthropic's unreleased Mythos did against more than 50 of their own production repos. According to him, Mythos is too powerful and must "include additional safeguards" before releasing to the public. Turns out the model can chain multiple low-severity bugs into a single severe exploit with a working PoC, where previous frontier models would stop at "interesting bug, unclear if exploitable." At triage time, that means fewer hedged findings and less time spent asking "is this even real?" A finding that arrives with a PoC is a finding you can act on. Cloudflare is also explicit about the safety side. The Mythos Preview build provided for Project Glasswing did not include the safeguards present in generally available models like Opus 4.7 or GPT-5.5. The model's organic refusals are real, but Cloudflare states they are not consistent enough to serve as a complete safety boundary on their own, and that any cyber frontier model made generally available in the future must ship with additional safeguards on top of that baseline. Interesting detail: Cloudflare was not on the original Project Glasswing launch partner list with Apple, AWS, Google, Microsoft, CrowdStrike, and others. Instead they got invited later on.

ITZY <Motto> Released Online : 🎧 Melon 🎧 Genie 🎧 Bugs 🎧 FLO 🎧 VIBE #ITZY# #MIDZY# @ITZYofficial #ITZY_Motto#