@MrX

Obsidian Security found three chained LiteLLM CVEs that let a default low-privilege user reach admin access and RCE (CVSS 9.9). We also demonstrate how a compromised gateway can inject arbitrary tool calls to further compromise downstream agents like Claude Code. Full breakdown and the fixes.

Build your creator business on Gigstop — sell downloads, courses, memberships, bookings, commissions, and digital products.

Best free online tool to resize and compress photos and signatures for Indian government exams (UPSC, SSC, IBPS, NEET, GATE) to exact dimensions. 100% private, secure & instant.

I made a chapter in my Advanced Robotics course about swarm robotics, focusing on the main ideas behind multi-robot coordination rather than treating it as just a buzzword. The video covers topics like: what makes a robot group a “swarm” decentralized vs. centralized coordination local rules and emergent global behavior examples inspired by ants, birds, and collective systems why scalability and robustness are important in swarm robotics I’m sharing it as a learning resource for students or beginners who are trying to understand where swarm robotics fits inside robotics and multi-agent systems. Video: https://www.youtube.com/watch?v=EXH3NpsKtUc I also keep the related course materials and source codes here, for anyone who prefers to learn by reading or experimenting with code: https://github.com/mohammadijoo/Control_and_Robotics_Tutorials For people working in robotics/control: what topics do you think should be added to make a swarm robotics lecture more useful — communication models, formation control, task allocation, path planning, or real hardware examples? submitted by /u/abolfazl1363 [link] [Kommentare]

I use Claude Code, Codex CLI, OpenCode, Cline, Cursor, and Amp enough to notice a pattern in how they handle long context. They are all converging on layered progressive compression, but they disagree on what to protect. Most protect recent user messages as a first-class asset. That makes sense. The user said it, which is the source of truth. Most also protect tool outputs that carry state. What surprised me was how differently they treat old assistant messages. Artifacts keeps recent tool calls verbatim but drops older context aggressively. Cursor starts pruning earlier design decisions once the window gets full. Codex CLI lets the model itself decide what to keep in the summary tier. The other axis is transparency. Do you tell the model it was compressed? Some systems silently replace old tool results with a placeholder, which means the model is reasoning under the illusion that it never happened. Others make it explicit: "the previous 40 tool calls are summarized below." I lean explicit because the model needs to know its own context was degraded. Verdents agent loop uses a similar tiered approach: snip first, prune second, summarize last, and a hard red line that protects user messages, stateful tool outputs, and anything the user explicitly flagged. The tradeoff is cost vs accuracy. Aggressive compression saves tokens but degrades the plan. Under-compression hits the window and causes context rot. submitted by /u/Direct_Band896 [link] [Kommentare]

Hyper-vigilant safety classifiers turn Fable into cautionary tale

“One robot now turns into many robots next year, but the number of ballerinas is the same.”

Create cinematic AI video with Seedance 2.0 Mini — text to video and image to video up to 1080p, at a fraction of Seedance 2.0 pricing. Start free.