Kestra 2.0 splits into a control plane and data plane, letting workers connect via gRPC instead of requiring direct database access, which means you can deploy them across regions and networks. The release also adds AI agent integration, a revamped no-code editor, and decouples the queue from the database for simpler configuration.

• Workers now connect to the control plane over a single outbound gRPC stream instead of needing direct database access, enabling deployment in different regions, clouds, or restricted networks without opening inbound ports.
• Queue and repository are now independent, so you pick them separately (Postgres, Kafka, Redis, or AMQP) instead of being locked into paired options; this simplified the codebase to one implementation instead of multiple backends.
• MCP Tool Trigger exposes any existing flow as a callable tool for AI agents like Claude, skipping the need for custom integration layers.
• AI Copilot is now a persistent sidebar with three modes (Edit, Plan, Ask) that refines flows iteratively rather than generating from scratch, and reads your namespace configuration to ground suggestions.

Salesforce integrated Anthropic’s Claude Tag into Slack, creating a persistent AI agent that overlaps with its own Slackbot and Agentforce features. Employees fear this third-party tool could undercut Salesforce’s in-house AI offerings even as the company promotes an open-platform strategy.

• Salesforce built Claude Tag into Slack even though it directly competes with its own Slackbot and Agentforce, leaving customers with three overlapping AI helpers in one workspace.
• The move is financially motivated: Salesforce plans to buy $300 million in Anthropic compute this year and owns roughly 1% of the now-$380 billion startup.
• Employees worry the strategy undercuts in-house products and confuses which tool deserves priority, even as Benioff frames Slack as a model-agnostic "interface to AI."
• Anthropic is reportedly eyeing expansion into Teams, email, and project-management tools, positioning itself to succeed independently of Slack.

The paper examines the shift from quick “vibe coding” to a structured, agent-driven software development lifecycle. It highlights context engineering’s role in ensuring reliability and frames developers as orchestrators of AI-powered software factories. It also outlines steps to integrate AI tools without sacrificing production-grade standards.

• Vibe coding's speed trades off type checks, error handling, and dependency hygiene, making production bugs hard to trace back to their source.
• Context engineering centralizes prompts, schemas, and env vars into one source of truth so model or API swaps only require a single update.
• Developers shift from writing code to orchestrating AI components as factory managers, using tools like Airflow or Prefect to stitch containerized models together.
• The proposed four-step roadmap—catalog tools, formalize interfaces/tests, automate deployment with rollback, monitor with alerting—merges AI-driven agility with traditional SDLC rigor.

This article walks through setting up a future-proof data stack by outsourcing ingestion to turnkey tools, sticking with SQL-based transforms, and carefully integrating AI without ignoring fundamentals. It also covers key areas like data quality, storage and compute choices, and when to move from replicas to a full warehouse or lakehouse.

• Ingestion is a solved problem now—use managed connectors (Estuary, Fivetran, Glue, DLT) instead of building custom pipelines unless there's truly no supported option.
• SQL remains the backbone of transformation work regardless of tool (dbt, stored procedures, Airflow), with AI only starting to help via auto-generated schemas and template joins, not replacing hands-on cleanup.
• Flashy AI chatbots/analytics tools often demand as much setup as traditional dashboards, so lightweight CLI or skills-file integrations with tools like Claude or Codex are a more practical automation win.
• Don't over-architect storage/compute—a read replica and plain SQL can beat a lakehouse or warehouse if your team size and actual workload don't justify the complexity.

Chrome now lets you save reusable Gemini prompts as “Skills” for one-click access instead of retyping or copy-pasting each time. Saved Skills sync across devices when you’re signed in, and you trigger them with “/” or the plus button in Gemini. They still require confirmation for actions like messaging or calendar entries.

• Chrome's Gemini now lets you save reusable prompts as "Skills," triggered via "/" or the "+" button instead of retyping or pasting them each time
• Skills sync across desktop devices when signed into Chrome
• Skills can operate across multiple open tabs at once, useful for tasks like comparing prices or aggregating research
• Actions like sending messages or adding calendar events still require user confirmation, keeping the same security checks as regular Gemini prompts