Just Shipped: Flue 1.0 Beta
Flue is the TypeScript framework for building the next generation of agents, designed around an open agent harness with zero LLM lock-in. It’s like Astro, for agents.
Flue 1.0 has been redesigned around three core primitives:
🔁 Workflows — structured automations designed for background work, where your code drives the agent from start to finish.
🧭 Agents (New!) — autonomous, stateful loops where the model drives itself to complete a given task.
📡 Channels (New!) — connect agents to Slack, GitHub, Linear, Discord, Teams, and more. Flue handles the boilerplate for you.
Everything shares the same durable foundation, powered internally by Pi, Vite, and Durable Streams. Deploy anywhere, use any LLM, and recover running agents across restarts and downtime.
We’ve talked to a lot of teams building agents, and keep hearing the same thing: getting to production is hard work. We built Flue to help change that.
Flue 1.0 Beta is available today. Give it a try and let me know what you think!
COMO ASSIM BICHO
O modelo de IA da PREFEITURA DO RIO bateu os modelos da Qwen e da Deepseek nos benchmarks e virou um dos melhores modelos de IA de código aberto ????????
⚠️ Malicious Sicoob NuGet steals Brazilian bank credentials while npm packages target AWS and CI/CD secrets.
The fake "Sicoob.Sdk" versions 2.0.0–2.0.4 exfiltrate client IDs, PFX certificates, and passwords. It was downloaded nearly 500 times.
Multiple npm packages from one actor also steal cloud and pipeline secrets.
Full report: https://t.co/NnLMiVp32X
introducing thermos in cursor
a deep security/correctness audit and a harsh code quality audit, run in parallel on your branch, synthesized into one prioritized list
Pergunta de entrevista backend:
Um dev júnior implementou upload de arquivo assim:
recebe o arquivo -> salva no disco -> grava URL no banco
Funcionou lindo no teste.
Até subir arquivo grande.
Até a API cair no meio.
Até 2 servidores entrarem no ar.
O que você mudaria?
Pergunta de entrevista backend:
Seu app recebe pagamento via webhook.
Às vezes o provedor envia o mesmo evento 2 vezes.
Às vezes envia fora de ordem.
Às vezes sua API cai no meio do processamento.
Como você desenharia esse fluxo pra não cobrar, liberar ou notificar errado?
🚨 BREAKING: 84 TanStack npm packages were compromised in an ongoing Mini Shai-Hulud supply chain attack, adding suspected CI credential-stealing malware.
Socket flagged every malicious version within six minutes of publication. This is a developing story.
Elysia 2.0 codename Kiana
This is an entire rewrite of Elysia with a better foundation structure
This release aims to provide much better performance, memory usage and easier contributions
You can track the progress the progress here
Expect 2 months until stable release
Been enjoying the Paper MCP with codex alot.
I wish there was a tool like Paper that opened in the Codex browser.
A codex native canvas board like this.
Yup, platform activity is surging. There were 1 billion commits in 2025. Now, it's 275 million per week, on pace for 14 billion this year if growth remains linear (spoiler: it won't.)
GitHub Actions has grown from 500M minutes/week in 2023 to 1B minutes/week in 2025, and now 2.1B minutes so far this week.
So we're pushing incredibly hard on more CPUs, scaling services, and strengthening GitHub’s core features.
And as a fine purveyor of hand-crafted shit code for many years, I'm not gonna weigh in on that. 🤣