| The news today of OpenAI acquiring Astral completes a loop first opened by GDM when they bought what became the Antigravity team last July, and then Anthropic’s purchase of Bun last December. Astral joins OpenClaw and (to a lesser extent) gpt-oss and Whisper in OpenAI’s growing list of top tier open source AI projects. This comes against the backdrop of Fidji Simo explicitly dropping “side quests” like Shopping (with key partner Walmart reporting awful conversion about 1/3 of click-outs) and prioritizing Enterprise (Frontier Alliances) and Coding (Astral), and now unifying ChatGPT and Codex apps into one “superapp” — something we have predicted but is now explicitly being prioritized at the highest levels. If we got one thing wrong in Rise of the AI Engineer 3 years ago, it is the importance of the role of code. Back then we framed the “1+2=3” thesis - that LLM-powered software would be capable of much more than either LLMs or software would alone - essentially presaging what would now be called harness engineering. But we almost completely missed the importance of the recursive nature of agentic coding improving agent/LLM training, which has been called out all over from Claude Code to MiniMax 2.7 as a key element of acceleration and importance in the labs. (we did end with a poignant “As human Engineers learn to harness AI, AIs will increasingly do Engineering as well, until a distant future when we look up one day and can no longer tell the difference.” — perhaps a half point there, but negative points on underestimating the importance and immediacy). Thankfully by the time the first AIE Summit came around, I was fully allocating 1/3 of the weight of AI Engineering to agentic coding:  AI News for 3/18/2026-3/19/2026. We checked 12 subreddits, 544 Twitters and no further Discords. AINews’ website lets you search all past issues. As a reminder, AINews is now a section of Latent Space. You can opt in/out of email frequencies!
AI Coding Agents, Developer Tooling, and the Race to Own the IDE Cursor’s Composer 2 looks like the day’s biggest developer-model launch: @cursor_ai released Composer 2, positioning it as a frontier-class coding model with major cost reductions. Cursor says quality gains came from its first continued pretraining run feeding a stronger base into RL (details). Third-party reactions emphasized both price/perf and benchmark competitiveness: @kimmonismus highlighted $0.50/M input and $2.50/M output with reported scores of 61.3 on CursorBench, 61.7 on Terminal-Bench 2.0, and 73.7 on SWE-bench Multilingual; @mntruell framed Cursor as a new kind of company combining API models with domain-specific in-house models. The launch also included an early alpha UI at Glass, with commentary from @theo that the industry will likely converge on this more agent-native UX. Several engineers also noted the training/infra story: @ellev3n11 said the RL run was distributed across 3–4 clusters worldwide, and @amanrsanger said the ~40-person team is focused exclusively on software engineering tasks. OpenAI moves down-stack with Astral; Anthropic expands Claude Code’s surface area: @charliermarsh announced that Astral—the team behind uv, ruff, and ty—is joining OpenAI’s Codex team; @gdb confirmed the deal from OpenAI’s side. The acquisition was broadly read as OpenAI strengthening its developer platform moat through ownership of foundational Python tooling; see @Yuchenj_UW and Simon Willison’s commentary. In parallel, Anthropic expanded Claude Code with channels so developers can interact via messaging apps, starting in research preview (announcement, docs). The product direction is notable: both OpenAI and Anthropic are pushing beyond “model API” toward persistent developer workflows and ambient agent access.
Agents, Multi-Agent Runtimes, and Enterprise Agent Control Planes The center of gravity is shifting from single agents to managed fleets, runtimes, and agent operating systems: @LangChain launched LangSmith Fleet, an enterprise workspace for creating and managing a fleet of agents with memory, tools, permissions, and channel integrations; repeated themes across the launch were agent identity, credential management, sharing controls, Slack exposure, and auditability (overview, additional framing). This lines up with broader discourse that “agent” is no longer a useful abstraction by itself: @YuvalinTheDeep argued the right metaphor is an AI operating system that allocates work, resources, and execution contexts. Complementary launches reinforced this stack-level view: @cognition added teams of Devins, where Devin decomposes work and delegates to parallel Devins in separate VMs; @lvwerra released AgentUI, a multi-agent interface coordinating code, search, and multimodal specialists; and @hrishioa argued long-horizon agentic work now requires a dedicated runtime with checkpointing, rollback, provider-specific harness switching, and execution repair. Security and permissions are becoming first-class design constraints for agent systems: a recurring thread across launches was that production agent deployment is bottlenecked less by “can the model do it?” and more by permissions, blast radius control, and observability. @swyx highlighted identity-based authorization as the emerging consensus for AI security, and @baseten described NemoClaw as NVIDIA’s answer to OpenClaw-style safety concerns with zero permissions by default, sandboxed subagents, and infra-enforced private inference. LangChain’s Fleet launch also heavily emphasized permissioning and audit trails. The throughline: agent stacks are maturing into something much closer to enterprise software infrastructure than chatbot wrappers.
Model Releases, Benchmarks, and Retrieval/Reasoning Results MiniMax M2.7 is being positioned as a practical agent model rather than a pure “frontier giant”: MiniMax teased a deeper technical livestream with OpenClaw around self-evolution and infrastructure for 100,000 running clusters (announcement), while early usage reports stressed improved emotional intelligence, character consistency, and strong agentic workflows (MiniMax note). More technical third-party evaluation from ZhihuFrontier said M2.7 keeps overall performance roughly on par with the previous generation but upgrades instruction following, context hallucination handling, and large-code / multi-round dialogue behavior, albeit with slightly worse hard reasoning and higher token consumption. Integration momentum was immediate: @Teknium added M2.7 to Hermes Agent, and users reported better long-running agent behavior than OpenClaw in some workflows (example). Qwen 3.5 Max Preview and retrieval-centric systems posted notable leaderboard movement: @arena reported Qwen 3.5 Max Preview reaching #3 in Math, Top 10 in Arena Expert, and Top 15 overall, with particularly large gains versus prior Max variants in text, writing, and math (breakdown); @Alibaba_Qwen confirmed more optimization is coming. Meanwhile, one of the most technically interesting result clusters was around late interaction retrieval: @antoine_chaffin claimed BrowseComp-Plus is now near 90% solved using Reason-ModernColBERT, a 150M model that outperformed systems up to 54× larger on deep research-style retrieval. Multiple follow-ups from @lateinteraction and others argued this is not a one-off but another strong signal that multi-vector / late-interaction retrieval is systematically outperforming dense single-vector approaches in reasoning-intensive search.
Multimodal Models, OCR, Document Parsing, and Creative Tools A strong crop of document/OCR tooling shipped, spanning model-based and model-free approaches: @nathanhabib1011 flagged Chandra OCR 2 as a new SOTA OCR release with 85.9% on olmOCR bench, 90+ languages, a 4B parameter model, and support for handwriting, math, forms, tables, and image caption extraction. Separately, @skalskip92 highlighted GLM-OCR 0.9B as a small OCR model reportedly beating Gemini on OCR benchmarks. On the parsing side, LlamaIndex open-sourced LiteParse, a local, layout-aware parser for PDFs, Office docs, and images with zero Python dependencies, built-in OCR options, spatial layout preservation, and explicit targeting at agent pipelines (launch, expanded post). This is a useful split in the stack: high-end OCR/VLMs for difficult pages, plus lightweight local parsers for the common case. Image/video and world-model work keeps accelerating, but the interesting part is latency and deployability: Google rolled out a significantly upgraded AI Studio “vibe coding” experience with a new Antigravity coding agent plus Firebase integrations, enabling multiplayer apps, backend services, auth, and persistent builds (Google AI Studio post, Google summary). On imaging, Microsoft launched MAI-Image-2, which debuted at #5 on the Image Arena and posted large subcategory gains over MAI-Image-1, especially in text rendering and portraits (arena ranking, Microsoft announcement). For vision/video understanding, @skalskip92 showed MolmoPoint doing point-based multi-object tracking directly from a VLM, distinct from segmentation-first approaches like SAM. And @kimmonismus made a useful systems point: sub-100ms prompt-to-output loops in generative media may matter more than raw model quality for real production workflows.
Training, Architectures, Inference, and Systems Research Continued pretraining and RL environment quality are re-emerging as core competitive levers: Composer 2’s team explicitly attributed gains to continued pretraining before RL (Cursor), and several researchers argued this pattern will become more common for specialized models (@code_star, @cwolferesearch). Relatedly, @pratyushmaini introduced the “Finetuner’s Fallacy”: early training data leaves a durable imprint on model representations that later finetuning struggles to undo. On the systems side, @skypilot_org scaled Karpathy-style autoresearch over a K8s GPU cluster, running ~910 experiments in 8 hours instead of ~96 sequentially, an example of infrastructure directly changing the shape of automated research loops. Architecture exploration remains lively beyond standard transformers: @MayankMish98 released M²RNN, revisiting non-linear recurrence with matrix-valued states for scalable language modeling; @tri_dao noted nonlinear RNN layers appear to add something distinct from attention and linear SSMs. NVIDIA’s Nemotron 3 stack also drew attention for mixing Transformer + Mamba 2, MoE/LatentMoE, multi-token prediction, and NVFP4 precision in service of lower inference costs and long-context agent workloads (summary). At the infra layer, @rachpradhan reported TurboAPI reaching 150k req/s, claiming 22× FastAPI throughput after a day of optimization, while @baseten launched the Baseten Delivery Network to reduce large-model cold starts by 2–3×.
Top tweets (by engagement) OpenAI acquires Astral: @charliermarsh announced Astral joining OpenAI’s Codex team, one of the clearest signals that AI labs now see ownership of core developer tooling as strategic. Cursor Composer 2 launch: @cursor_ai had the highest-engagement technical product launch in the set, reflecting how central coding-model price/performance has become. Google AI Studio’s upgraded vibe coding stack: @GoogleAIStudio and @OfficialLoganK drove major engagement around full-stack app generation with persistent builds, multiplayer, and backend integrations. LlamaIndex LiteParse: @jerryjliu0 resonated strongly, suggesting continued demand for practical, local-first parsing infrastructure for agent pipelines. Late interaction retrieval on BrowseComp-Plus: @antoine_chaffin posted one of the more important benchmark results of the day: a 150M late-interaction retriever pushing a hard deep-research benchmark toward 90%.
MiniMax-M2.7 Announced! (Activity: 1078): The image presents a comparative analysis of the newly announced MiniMax-M2.7 model against other models like M2.5, Gemini 31 Pro, Sonnet 4.6, Opus 4.6, and GPT 5.4 across various benchmarks such as SWE Bench Pro, VIBE-Pro, and MM-ClawBench. MiniMax-M2.7 is highlighted in red and demonstrates superior performance in several categories. The model’s development emphasizes autonomous iteration, where it optimizes its performance through iterative cycles of analysis, planning, modification, and evaluation, achieving a 30% performance improvement on internal evaluation sets. This process includes optimizing sampling parameters and enhancing workflow guidelines, indicating a shift towards fully automated AI self-evolution. One commenter highlights the importance of real-world usability over benchmark performance, expressing skepticism about models that excel in evaluations but may not perform well in practical applications. Another comment humorously notes the rapid pace of new model releases, expressing excitement and anticipation for future developments. Recoil42 highlights the autonomous iteration capabilities of the MiniMax-M2.7 model, which can optimize its own performance through iterative cycles. The model autonomously analyzes failure paths, plans changes, modifies code, and evaluates results, achieving a 30% performance improvement on internal evaluation sets. This process includes optimizing sampling parameters and enhancing workflow guidelines, indicating a move towards fully automated AI self-evolution. Specialist_Sun_7819 raises a critical point about the discrepancy between benchmark performance and real-world usability. They emphasize that many models excel in evaluations but struggle with tasks that deviate from the training distribution. This comment underscores the importance of user testing to validate the practical effectiveness of models like MiniMax-M2.7. Lowkey_LokiSN expresses concern about the model’s quantization resistance, referencing issues with the previous M2.5 model’s UD-Q4_K_XL variant. Quantization can affect model performance, and improvements in this area would be crucial for maintaining the integrity of MiniMax-M2.7’s capabilities when deployed in resource-constrained environments.
Omnicoder-Claude-4.6-Opus-Uncensored-GGUF (Activity: 397): The post introduces the OmniClaw model, crafted from real Claude Code / Codex sessions using the DataClaw dataset, and available on Hugging Face. The Omnicoder model, distilled by Claude Opus, and the OmniRP model for creative writing, are also presented. All models are uncensored and use Q8_0 quantization due to quality issues with other quants. The models were merged using a Python script available on Pastebin, maintaining GGUF header and metadata for compatibility. The Omnicoder model was created by merging several models, including Jackrong’s and HauhauCS’s Qwen 3.5 9B models, Tesslate’s Omnicoder, and Bartowski’s Qwen 3.5-9B as a base. The OmniClaw and OmniRP models were further merged with models from empero-ai and nbeerbower, respectively. The post claims these models represent the best in Uncensored General Intelligence (UGI) for small 9B models based on the Qwen 3.5 9B architecture. A comment highlights a benchmark test on the Omnicoder 9B model, noting a 5.3% pass@1 and 29.3% pass@2 success rate on the Aider benchmark, with a runtime of 402 seconds per problem, suggesting skepticism about the effectiveness of Claude distillation in improving Omnicoder’s performance. grumd provides a detailed benchmark comparison between Qwen3.5 35B-A3B and Omnicoder 9B using the Aider benchmark, which consists of 225 hard coding problems. Qwen3.5 35B-A3B achieved a 26.7% pass@1 and 54.7% pass@2, taking 95 seconds per problem on average. In contrast, Omnicoder 9B, after completing 75 problems, has a 5.3% pass@1 and 29.3% pass@2, with a significantly longer average time of 402 seconds per problem. This highlights a substantial performance gap between the models, particularly in efficiency and accuracy. grumd expresses skepticism about the potential for Claude distillation to resolve Omnicoder’s performance issues, suggesting that the current results are not promising. The comparison with Qwen3.5 9B is anticipated to provide further insights into whether the performance issues are inherent to Omnicoder or if they can be mitigated through model adjustments or distillation techniques. jack-in-the-sack raises a question about model interchangeability, specifically whether Claude Code can be replaced with Omnicoder. This reflects a common concern in the community about the compatibility and performance trade-offs when switching between different AI models, especially in specialized tasks like coding.
My company just handed me a 2x H200 (282GB VRAM) rig. Help me pick the “Intelligence” ceiling. (Activity: 854): The user has access to a server with dual Nvidia H200 GPUs, each with 141GB HBM3e, totaling 282GB VRAM. They are tasked with testing large language models (LLMs) for local coding tasks, including code completion, generation, and reviews. A suggested model is Qwen 3.5 397B using vLLM for efficient context handling at Q4 quantization. It’s recommended to avoid models like ollama or llama.cpp due to their poor handling of batched inference, which is crucial for concurrent coding tasks. Instead, vLLM or sglang are suggested for better stability and performance in multi-user environments. One commenter emphasizes the importance of defining clear goals and outcomes before experimenting to ensure continued access to the hardware. Another shares a negative experience with ollama, citing instability and poor performance, and recommends vLLM for its stability and suitability for multi-user environments. Zyj suggests using vLLM with the Qwen 3.5 397B model, which should allow for a significant context window at Q4 precision. This recommendation is based on the available VRAM and the need to balance model size with context capabilities. TUBlender advises against using ollama or llama.cpp for setups requiring batched inference due to their poor handling of concurrent requests. They share personal experience with ollama serving qwen2.5 72b, which resulted in instability and crashes, recommending vllm or sglang as more stable alternatives for multi-user environments. Mikolai007 warns against using models that max out the GPU’s VRAM, emphasizing the importance of maintaining a healthy context window. They recommend Minimax M2.5 and Qwen 3.5 as optimal choices, noting that GLM 5 is too large at 800b despite its capabilities.
Two weeks ago, I posted here to see if people would be interested in an open-source local AI 3D model generator (Activity: 366): The post introduces a beta version of an open-source desktop application designed to generate 3D meshes from images, currently supporting the Hunyuan3D 2 Mini model. The app is modular, built around an extension system, and the developer is seeking feedback on features, file export extensions, and additional model support. The GitHub repository is available here. Commenters suggest features such as multi-image input, text-based editing, checkpoint saving, and support for formats like glTF. They also recommend supporting Trellis 2 for state-of-the-art open 3D model generation and propose a ggml backend for non-CUDA GPUs. Additional features like custom mesh import, texture generation, and basic editing tools are also discussed. New_Comfortable7240 outlines a comprehensive feature set for a local AI 3D model generator, emphasizing the need for a user-friendly interface that allows for the addition of images and text to create initial meshes. They suggest implementing a chat interface for iterative editing, saving checkpoints, and ensuring compatibility with the glTF format through a healing function. The comment also highlights the importance of node renaming in glTF to avoid confusion and proposes optional features like texture generation, animations, and Level of Detail (LOD) management. Nota_ReAlperson mentions Trellis 2 as the state-of-the-art for free open 3D model generation and suggests supporting it. They also propose the challenging task of developing a ggml backend for non-CUDA GPUs, which would broaden accessibility for users without high-end hardware. This highlights the importance of considering diverse hardware capabilities in the development of the model generator. ArtifartX emphasizes the necessity of importing custom meshes and generating textures for them, suggesting enhancements like blending and basic brush tools. They reference a past project using SDXL and ControlNet with custom shaders for projection, indicating the potential for advanced texture manipulation features. The comment also advises focusing on commonly used file formats such as OBJ, FBX, GLTF, and USD for export options.
/r/Singularity, /r/Oobabooga, /r/MachineLearning, /r/OpenAI, /r/ClaudeAI, /r/StableDiffusion, /r/ChatGPT, /r/ChatGPTCoding, /r/aivideo, /r/aivideo
Harmonic unleashes Aristotle, the world’s first formal mathematician agent for free (Activity: 446): The image announces the release of the “Aristotle Agent” by Harmonic, touted as the world’s first autonomous mathematician agent, available for free. This agent is notable for its ability to solve and formalize complex mathematical problems, distinguishing itself from other AI math tools by providing formal verification of proofs, which ensures correctness without human intervention. This is in contrast to other AI systems like DeepMind’s AlphaProof, which remains proprietary. The tool has been linked to recent attempts to solve the Erdős problem, highlighting its potential in tackling significant mathematical challenges. Commenters highlight the significance of the formal verification feature, which ensures that proofs are correct by construction, eliminating the need for human verification. There is curiosity about its capability to handle complex open problems beyond textbook-level challenges. ikkiho highlights the significance of formal verification in Harmonic’s Aristotle, contrasting it with other AI math tools. Unlike LLMs that generate proofs in natural language, which may be incorrect, Aristotle’s use of Lean proofs ensures correctness by construction, eliminating the need for human verification. This approach is particularly notable as it is offered for free, unlike DeepMind’s proprietary AlphaProof. ikkiho also raises a question about the current capabilities of Aristotle, wondering if it has been tested on challenging open problems or if it is primarily solving textbook-level mathematics. This inquiry points to the potential of Aristotle to tackle more complex mathematical challenges in the future. omegahustle expresses hope that Aristotle remains free and is used responsibly, emphasizing the importance of its availability for those who can utilize it effectively. This comment underscores the potential impact of free access to advanced mathematical tools on the research community.
A new version of the Gemini app was just released. (Activity: 425): The image announces an update to the Google Gemini app, version 1.2026.1062300, which introduces a ‘Personal Intelligence’ feature for free users in the US. This feature aims to enhance connectivity across Google apps, providing personalized responses. The update also includes UI improvements and bug fixes, with a download size of 196.2 MB. This suggests a significant enhancement in user experience and integration capabilities within the Google ecosystem. Commenters express concerns about privacy, particularly regarding the potential for government access to personal data through the ‘Personal Intelligence’ feature. There is also skepticism about the necessity of the Gemini app, with some users viewing it as redundant to existing Google app functionalities. Technical_Train_9821 raises concerns about data privacy with the Gemini app, highlighting the potential risks of allowing the app to access and connect personal data. They suggest that if the government were to gain access, it could make an individual’s entire online presence searchable, posing significant privacy issues. brandeded shares practical use cases for the Gemini app, emphasizing its ability to integrate with other services and perform complex tasks. They describe scenarios where the app can create calendar appointments based on email content, search for specific financial transactions, and retrieve information from Google Drive, showcasing its utility in managing personal data efficiently.
Basically Official: Qwen Image 2.0 Not Open-Sourcing (Activity: 495): The image in the Reddit post is an announcement for the launch of Qwen-Image-2.0, a next-generation image generation model by Alibaba. Initially tagged as “Open-Source” on the Qwen research page, it has now been reclassified as “Release,” indicating it will not be open-sourced. This change aligns with recent internal shifts at Alibaba, including the departure of key engineers and a strategic pivot away from open-source models due to revenue concerns. The model features professional typography rendering, support for 1k-token instructions, and native 2K resolution, aimed at creating detailed infographics and comics. Commenters express confusion and disappointment over Alibaba’s decision not to open-source Qwen-Image-2.0, arguing that its value diminishes when closed-source, especially given the competitive landscape with models like Midjourney. Additionally, it’s noted that Alibaba’s CEO has shown dissatisfaction with the lack of revenue from open-source models, influencing this strategic shift. Skystunt highlights a critical issue with Qwen Image 2.0’s closed-source approach, emphasizing that its competitive edge is diminished when compared to other models like Midjourney or Nano Banana, which offer more mature UIs and open-source benefits. The model’s closed nature, combined with data privacy concerns, makes it less appealing despite its technical capabilities as a 7B parameter model. BreakingGood provides context on Alibaba’s strategic shift away from open-sourcing, citing the CEO’s dissatisfaction with the lack of revenue from open models. This has led to significant internal changes, including the departure of key engineers, suggesting a future where Alibaba may not release open-source models, impacting the community’s access to cutting-edge technology. LeKhang98 comments on the perception of model release frequency, noting that while some feel overwhelmed by new models, the actual release rate is relatively low, with only 2-3 significant models per year. This perspective suggests that the community should appreciate the current pace and availability of new models, despite potential slowdowns in releases.
An Australian ML researcher, used ChatGPT+AlphaFold to shrink 75% of his life-threatened dog’s MCT cancerous tumor, developing a personalized mRNA vaccine in just two months - after sequencing his dog’s DNA for $2,000 (Activity: 498): An Australian machine learning researcher, Paul Conyngham, utilized ChatGPT and AlphaFold to develop a personalized mRNA vaccine for his dog, Rosie, who had a life-threatening mast cell tumor. By sequencing the tumor’s DNA for approximately $2,000, Conyngham identified neoantigens using ChatGPT and predicted protein structures with AlphaFold. Collaborating with Martin Smith from UNSW for genome sequencing and Pall Thordarson for mRNA synthesis, he successfully shrank the tumor by 75% within two months, despite having no formal background in biology or medicine. This case highlights the potential of AI in personalized medicine and rapid vaccine development (source). Commenters are debating the implications of this case, questioning whether it represents a significant shift in healthcare democratization or if it’s overhyped. Some suggest that regulatory barriers are hindering medical progress, as demonstrated by the rapid development achieved in this instance. DepartmentDapper9823 argues that this case illustrates how regulatory bodies may impede medical progress. They suggest that when these barriers are bypassed, advancements can occur more rapidly, as evidenced by the quick development of a personalized mRNA vaccine for the dog using ChatGPT and AlphaFold. AngleAccomplished865 calls for expert opinions to assess the broader implications of this case, questioning whether it represents a significant shift in democratized healthcare or if it’s merely hype. They highlight the need for professional insights to determine the true impact of using AI tools like ChatGPT and AlphaFold in medical research. 682463435465 raises a concern that individuals with cancer might attempt to replicate this approach on themselves, indicating a potential risk of self-experimentation without proper medical guidance. This underscores the need for careful consideration of the ethical and safety implications of using AI in personalized medicine.
Built an open source tool that can find precise coordinates of any picture (Activity: 837): Netryx is an open-source tool developed by a college student, designed to determine precise geographic coordinates from street-level photos using visual clues and a custom machine learning pipeline. The tool is available on GitHub and aims to connect with developers and companies interested in geolocation technologies. The tool’s capabilities are demonstrated through a custom web version that geolocates events like the Qatar strikes, although the core pipeline remains consistent across versions. Commenters express mixed feelings about the tool’s potential uses, noting it could be both beneficial and harmful. There is also curiosity about its reliance on existing data sources like Google Street View for functionality. I built a Claude skill that writes accurate prompts for any AI tool. To stop burning credits on bad prompts. We just hit 600 stars on GitHub‼️ (Activity: 728): The prompt-master is a Claude skill designed to optimize prompt generation for various AI tools, achieving over 600 stars on GitHub. It intelligently detects the target AI tool and applies specific strategies, such as extracting 9 dimensions from user input and identifying 35 common prompt issues, to enhance prompt accuracy and efficiency. The tool supports a wide range of platforms including Claude, ChatGPT, Midjourney, and Eleven Labs, and is open-source, allowing for community-driven improvements. The latest version, v1.4, incorporates user feedback and plans for v1.5 are underway, focusing on agent-based enhancements. GitHub Repository. Commenters highlight the tool’s ability to tailor prompts to specific AI models, such as Midjourney and Claude Code, as a key differentiator from generic prompt tools. There is interest in its compatibility with open-source models, suggesting potential for broader application. The tool’s ability to perform tool-specific routing is highlighted as a key feature, making it more effective than generic prompt enhancers. This is crucial because different AI tools like Midjourney and Claude Code require distinct prompt structures, which most general tools fail to address. A user inquires about the compatibility of the tool with open-source models, specifically mentioning running it locally with ComfyUI on a 5090 GPU. This suggests interest in leveraging the tool’s capabilities beyond proprietary models, potentially expanding its utility in diverse AI environments. Another user notes that while similar tools have been attempted, they often require manual tweaking of prompts. However, if this tool effectively manages tool-specific nuances, such as differences between Cursor and Claude Code, it could significantly enhance usability and efficiency.
I got tired of manually prompting every single clip for my AI music videos, so I built a 100% local open-source (LTX Video desktop + Gradio) app to automate it, meet - Synesthesia (Activity: 306): Synesthesia is an open-source application designed to automate the creation of AI-generated music videos by integrating with local LLMs like Qwen3.5-9b. It processes three input files: an isolated vocal stem, a full band performance, and text lyrics, to generate a shot list that alternates between vocal and story segments. The app interfaces with LTX-Desktop for video generation, achieving a first-pass render of a 3-minute video in under an hour on a 5090 GPU at 540p resolution. Users can adjust the shot list manually or let it run automatically, and select multiple takes per shot for final editing. The project is hosted on GitHub. One commenter suggests adding LoRA support for consistent character representation, while another criticizes the automation, arguing that it cannot replace the creative process of manual prompting. Loose_Object_8311 suggests that the app could benefit from LoRA support to maintain consistent character appearances across clips. LoRA (Low-Rank Adaptation) is a technique used to fine-tune models efficiently, which could enhance the app’s ability to generate consistent visual elements in AI-generated music videos. InternationalBid831 inquires about compatibility with Wan2GP running LTX2 instead of LTX Desktop, particularly for users with a 5070ti GPU. This suggests a need for the app to support different hardware configurations and possibly different versions of the LTX software to accommodate a wider range of users. Diadra_Underwood proposes adding a styles drop-down menu to the app, highlighting the potential for users to easily switch between different visual styles such as claymation, puppets, or CGI. This feature could enhance user experience by allowing for quick experimentation with various artistic styles in AI-generated content.
The dictionaries are suing OpenAI for “massive” copyright infringement, and say ChatGPT is starving publishers of revenue (Activity: 718): Britannica and Merriam-Webster have filed a lawsuit against OpenAI in the Southern District of New York, alleging that OpenAI’s ChatGPT has infringed on their copyrights by using their researched content without permission. The lawsuit claims that ChatGPT’s ability to provide direct answers from absorbed content is depriving publishers of web traffic and ad revenue, which are crucial for their survival. This case adds to ongoing legal debates about AI’s use of online content and the boundaries of public knowledge versus proprietary information. Read more. Commenters are questioning the implications of allowing companies to own definitions and the broader impact on information accessibility. There’s a satirical tone regarding the monetization of word usage, reflecting skepticism about the lawsuit’s premise. CEO Asks ChatGPT How to Void $250 Million Contract, Ignores His Lawyers, Loses Terribly in Court (Activity: 465): In a recent legal debacle, Krafton CEO Changhan Kim attempted to void a $250 million contract with Unknown Worlds Entertainment by consulting ChatGPT instead of his legal team. The court decisively ruled against him, emphasizing the dangers of using AI for intricate legal strategies without professional oversight. The case underscores that while AI can assist in legal preparation by stress-testing arguments and summarizing precedents, it lacks the liability and contextual understanding necessary for direct legal action. For more details, see the 404 Media report. Commenters highlight the misuse of AI as a replacement for professional judgment, noting that AI should be used to enhance legal strategies rather than replace them. They emphasize the importance of human oversight, especially in complex legal matters, and suggest using AI to identify potential challenges rather than as a direct source of legal advice. RobinWood_AI highlights the misuse of AI in legal contexts, emphasizing that AI should be used to enhance legal strategies rather than replace professional judgment. AI can assist in stress-testing arguments and drafting frameworks but lacks the liability and context of a human lawyer. The CEO’s mistake was using AI to directly void a contract without legal oversight, illustrating the gap between AI as a tool and a liability. chiqu3n discusses the limitations of AI in understanding specific legal contexts, noting that general AI models like ChatGPT may not account for special legislation that could affect contract terms. They compare this with a specialized legal LLM, ‘justicio’, which provided a more nuanced and legally accurate response, highlighting the importance of human expert review in critical legal matters. Dailan_Grace points out the issue of AI’s authoritative tone, which can mislead users into trusting incorrect information. AI models often present information confidently without hedging, which can be problematic if the user lacks the expertise to identify errors. This overconfidence in AI outputs may have contributed to the CEO’s poor decision-making.
Jeremy O. Harris drunkenly called OpenAI’s Sam Altman a Nazi at the Vanity Fair Oscar party (Activity: 650): At the Vanity Fair Oscar party, playwright Jeremy O. Harris confronted Sam Altman, CEO of OpenAI, accusing him of being akin to a Nazi figure due to OpenAI’s new deal with the Department of War. Harris later clarified his statement, comparing Altman to Friedrich Flick, a German industrialist convicted of war crimes, rather than Joseph Goebbels. This incident highlights ongoing ethical debates surrounding AI and its military applications. The comments reflect skepticism about the appropriateness of the Nazi comparison, noting Altman’s Jewish background, and include some off-topic humor.
Unfortunately, Discord shut down our access today. We will not bring it back in this form but we will be shipping the new AINews soon. Thanks for reading to here, it was a good run. You're currently a free subscriber to Latent.Space. For the full experience, upgrade your subscription. Upgrade to paid | |
No comments:
Post a Comment