# Connectors Published articles for Connectors. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Anthropic merges Claude Chat and Cowork into one interface DevFeed: [Anthropic merges Claude Chat and Cowork into one interface]() Original publisher: [Read original article]() Author: Amanda Caswell Published: 2026-09-16T16:46:36Z Content type: news Language: en Sources: [The New Stack]() Topics: [anthropic](), [Claude]() Tags: [ai-agents](), [ai-infrastructure](), [anthropic](), [chat](), [claude](), [connectors](), [context](), [developer-tools](), [tools](), [workflow]() ### AI overview Anthropic is merging Claude Chat and Cowork into a single interface, allowing conversations to handle simple questions, multi-step projects, connected tools, and background execution. Claude Docs and Claude Slides are launching in beta on paid plans, while Claude Design is moving into conversations. ### Source excerpt Using Claude for anything beyond a quick question has always started with a routing decision to use Chat or Cowork? The post Anthropic bet users were choosing wrong. So it removed the choice. appeared first on The New Stack. ## Unify your marketing data with Lakeflow Connect DevFeed: [Unify your marketing data with Lakeflow Connect]() Original publisher: [Read original article]() Author: Sonia Bendre; Giselle Goicochea Published: 2026-09-11T18:00:00Z Content type: article Language: en Sources: [Databricks]() Topics: [databricks](), [Software as a service](), [Databases](), [API](), [Automation](), [dashboards](), [hubspot](), [CI/CD]() Tags: [analytics](), [api](), [automation](), [churn](), [ci-cd](), [connectors](), [crm](), [customer](), [customers](), [dashboards](), [data](), [databases](), [databricks](), [engineering](), [marketing](), [product](), [retention](), [saas](), [salesforce](), [series]() ### AI overview This first post in a series presents Lakeflow Connect as a fully managed data-ingestion service for unifying fragmented marketing and Customer 360 data. It describes native connectors for SaaS applications, databases, and files, configured through a point-and-click UI or API, with governed tables in Unity Catalog and integrations such as HubSpot and Salesforce. The article highlights reduced maintenance compared with custom pipelines and support for downstream reporting, analytics, retention, and churn analysis. ### Source excerpt This is the first post in a new series exploring how Lakeflow Connect brings fully... ## Control who can manage connectors in Vercel Connect DevFeed: [Control who can manage connectors in Vercel Connect]() Original publisher: [Read original article]() Author: Allen Zhou Published: 2026-09-11T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Authorization]() Tags: [agents](), [connectors](), [documentation](), [enterprise](), [vercel]() ### AI overview Vercel Connect now lets Pro and Enterprise teams restrict connector management to Owners and users with the Connector Manager extended permission. Connectors provide applications and agents with access to external services through team-managed credentials. ### Source excerpt Pro and Enterprise teams can now control who can create and manage Vercel Connect connectors. Connectors let applications and agents access external services using credentials managed by your team. Owners can enable this restriction under Connector Permissions in Team Settings. Once enabled, only people with the Owner role or Connector Manager extended permission can create or manage connectors. Browse all connectors, or learn more in the Vercel Connect documentation. Read more ## Arduino UNO Media Carrier adds MIPI CSI/DSI and audio connectors to UNO Q and VENTUNO Q boards DevFeed: [Arduino UNO Media Carrier adds MIPI CSI/DSI and audio connectors to UNO Q and VENTUNO Q boards]() Original publisher: [Read original article]() Author: Jean-Luc Aufranc (CNXSoft) Published: 2026-09-10T00:00:32Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [UNO Q](), [Arduino](), [Raspberry Pi](), [Hardware](), [Open Source]() Tags: [arduino](), [audio](), [camera](), [connectors](), [display](), [embedded-systems](), [hardware](), [linux](), [mipi](), [mipi-csi](), [news](), [open-source](), [single-board-computer](), [specifications](), [touchscreen](), [uno-q](), [ventuno-q](), [waveshare]() ### AI overview The Arduino UNO Media Carrier adds accessible 22-pin MIPI DSI and CSI connectors, three 3.5 mm audio jacks, and RGB LEDs to Arduino UNO Q and VENTUNO Q boards. It is listed at $19.25 or EUR 19.89 including VAT. ### Source excerpt Arduino UNO Media Carrier board adds three audio jacks, a MIPI DSI display connector, two MIPI CSI camera connectors, and a few RGB LEDs to the Arduino UNO Q and Arduino VENTUNO Q SBCs. Both Arduino "Q" boards already expose MIPI CSI/DSI and audio interfaces, but only through the JMEDIA and JMISC 60-pin headers, which aren't very convenient. The Arduino UNO Media Carrier board fixes that with 22-pin MIPI connectors and 3.5 audio jacks. Arduino UNO Media Carrier (ASX00083) specifications: Compatible SBCs - Arduino UNO Q and Arduino VENTUNO Q Display I/F - 22-pin MIPI DSI connector compatible with standard MIPI-DSI display modules (5-inch, 8-inch, 10.1-inch Waveshare touch display compatible) Camera I/F - 2x 22-pin MIPI-CSI connectors compatible with IMX219 camera modules like the Raspberry Pi Camera Module 2 Audio 3.5 mm (MIC-IN/Headphones Out) audio jack 3.5mm Line Out audio jack 3.5mm Ear Out audio jack Host interfaces 60-pin female [...] The post Arduino UNO Media Carrier adds MIPI CSI/DSI and audio connectors to UNO Q and VENTUNO Q boards appeared first on CNX Software - Embedded Systems News. ## The end of credential sprawl for agents DevFeed: [The end of credential sprawl for agents]() Original publisher: [Read original article]() Author: Dima Voytenko Published: 2026-08-25T04:00:00Z Content type: article Language: en Sources: [Vercel News]() Topics: [Vercel](), [Security](), [OAuth](), [OpenID connect (OIDC)](), [Authorization](), [SDKs](), [API](), [pull-requests]() Tags: [agents](), [connectors](), [github](), [oidc](), [pull-requests](), [sdk](), [security](), [shopify]() ### AI overview Vercel Connect is generally available as a way for applications and agents to obtain short-lived, task-scoped credentials at runtime. It supports connectors for services such as Slack, GitHub, Snowflake, Shopify, and OAuth providers, uses deployment OIDC identity for authentication, refreshes tokens automatically, and avoids storing provider secrets in applications. ### Source excerpt Every useful agent reaches beyond your codebase. It posts to Slack, opens pull requests, queries Snowflake, or calls an internal API. That reach is what makes it valuable, and it's also where the risk lives, because for years, granting it meant provisioning a long-lived token and hoping it never leaked. Vercel Connect replaces long-lived tokens with ones your code requests at runtime, scoped to the task and expiring on their own. During the public beta, we've grown the ecosystem past 100 connectors, unified how they work, and added the governance capabilities teams need in production. Today, Vercel Connect is generally available. Vaults don't fix long-lived tokens Managing credentials has become its own workload. Teams write rotation scripts, copy secrets across environments, and share tokens between users. Putting a token in a vault made it harder to steal, but no less dangerous once stolen. It never expires, and no vault limits what a leaked credential can do. Agents compounded the problem by touching more systems with greater autonomy, more often. Yet the tools to contain a secret haven't changed. With Vercel Connect, your app never stores credentials. It requests one: You register a connector once for a provider like Slack, GitHub, Snowflake, Shopify, or your own OAuth service You attach it to the projects and environments that need it Your code requests a token at runtime, and it refreshes automatically Your app has no provider secret to commit by accident Requesting a token doesn't require another secret. Every deployment on Vercel carries an OIDC identity, and the SDK uses it to prove who's asking. What changes when access becomes a request The difference shows up in the properties of the credential: Property Stored token Vercel Connect Lifetime Never expires Short-lived, refreshed automatically Reach Everything the agent could need Scoped to the task in the request Identity One shared bot for every user App or a specific named user Rotation Mint, update copi ## Connect v0 apps to Slack, Google, and 100+ other services DevFeed: [Connect v0 apps to Slack, Google, and 100+ other services]() Original publisher: [Read original article]() Author: Vishal Yathish Published: 2026-08-24T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Slack](), [Google](), [GitHub](), [Notion](), [dashboards](), [Playwright]() Tags: [agent](), [apps](), [browser](), [connectors](), [github](), [google](), [secrets](), [slack](), [tokens](), [vercel](), [voice]() ### AI overview Vercel Connect lets apps and agents built in v0 securely connect to more than 100 services, including Slack, Google, Notion, GitHub, and Salesforce. It provides guided connector setup, reusable team configuration, managed app registration for some services, and short-lived runtime tokens. Examples include a voice-controlled browser agent that generates Playwright code and a dashboard combining Slack, Gmail, and Linear information. ### Source excerpt Apps and agents built in v0 can now securely connect to more than 100 services, including Slack, Google, Notion, GitHub, and Salesforce, through Vercel Connect. Ask v0 to connect your app to a service. It opens the connector setup and guides you through it. You set up each connector once for your team, then reuse it across apps. For managed connectors like Slack and GitHub, Vercel handles app registration, so you don't need to create or configure an app with the provider. For other services, you can provide your own credentials. In both cases, Vercel Connect issues short-lived tokens at runtime, so your application doesn't need to store or rotate long-lived secrets. Using v0 and Vercel Connect, Danny from KERNEL built a voice-controlled browser agent that generates Playwright code to operate a real browser. We built a personal dashboard that brings Slack messages, Gmail, and Linear issues into one view and summarizes what needs attention. Read the documentation or try it yourself in v0: Read more ## Multi-Core Fiber: Several Optical Cores Inside One Strand DevFeed: [Multi-Core Fiber: Several Optical Cores Inside One Strand]() Original publisher: [Read original article]() Author: j2sw Published: 2026-08-18T13:39:00Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [Hardware](), [Networks](), [interface]() Tags: [400g](), [cabling](), [channel](), [connectors](), [data-center](), [fiber](), [fiber-optics](), [internet-architecture](), [multi-core-fiber](), [network-engineering-resources](), [networks](), [optical-networking](), [optics](), [space-division-multiplexing](), [transmission]() ### AI overview This article explains how multi-core fiber places several optical cores inside one standard 125-micron cladding. It distinguishes MCF from high-fiber-count cable, describes aggregate capacity using separate channels and space-division multiplexing, and explains the need for specialized optical interfaces, connectors, splicing, and testing. ### Source excerpt Multi-core fiber places several independent optical cores inside one standard 125-micron cladding. It increases channel density, but it also requires different connectors, splicing methods, and testing procedures. The post Multi-Core Fiber: Several Optical Cores Inside One Strand appeared first on Justin Wilson (j2sw). ## What it's like to join WorkOS as a product designer DevFeed: [What it's like to join WorkOS as a product designer]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-17T19:47:49Z Content type: opinion Language: en Sources: [WorkOS Blog]() Topics: [Artificial Intelligence](), [Model Context Protocol](), [Tooling](), [Figma](), [Slack](), [Notion]() Tags: [ai](), [connectors](), [context](), [data](), [design](), [designer](), [figma](), [mcp](), [slack](), [tooling]() ### AI overview A product designer describes joining WorkOS and using shared company context, MCP-connected data, Slack, Notion, and AI-assisted design tooling to answer product questions and onboard more quickly. ### Source excerpt What it's actually like to join WorkOS as a product designer: transparent context by default, and AI as everyday design tooling. ## Multi-Core Fiber and How It Is Used in Data Centers DevFeed: [Multi-Core Fiber and How It Is Used in Data Centers]() Original publisher: [Read original article]() Author: j2sw Published: 2026-08-12T14:27:20Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [data centers](), [datacenter]() Tags: [400g](), [cabling](), [connectors](), [data-center](), [data-centers](), [fiber](), [fiber-optics](), [it-operations](), [mpo](), [mtp](), [multi-core-fiber](), [network-engineering-resources](), [optics](), [panel](), [parallel](), [single-mode](), [structured-cabling]() ### AI overview This article explains how "multi-core fiber" is used in data center discussions, distinguishing multi-fiber or high-fiber-count cables from true multicore fiber. It covers cable construction, fiber counts, single-mode and multimode options, and MPO and MTP connectors. ### Source excerpt If you work around data centers and high-density builds, you have probably heard the term "Multi-Core Fiber" thrown around. People use it in a few different ways. Sometimes, it means a new fiber trunk that comes into a cabinet as a single cable and breaks out into dozens or even hundreds of fibers. That setup ... Read more The post Multi-Core Fiber and How It Is Used in Data Centers appeared first on Justin Wilson (j2sw). ## Vercel Connect now supports CLI setup for 100+ connectors DevFeed: [Vercel Connect now supports CLI setup for 100+ connectors]() Original publisher: [Read original article]() Author: Bhrigu Srivastava Published: 2026-08-11T19:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Command-line interface](), [Shopify](), [GitHub]() Tags: [cli](), [connectors](), [github](), [shopify](), [vercel]() ### AI overview Vercel Connect now supports CLI setup for more than 100 services. Users can create and attach connectors from the terminal, with the CLI pre-populating service details and prompting for required credentials. Attached connectors can provide short-lived, scoped provider tokens. ### Source excerpt You can now integrate 100+ services through Vercel Connect from the CLI. Previously, vercel connect create completed setup in the terminal for some services, and opened the dashboard for everything else. Pass the service name to create a connector, then attach it to your project: The CLI pre-populates the brand name, icon, auth type, and MCP or discovery URL, then prompts for any credentials the service requires and creates the connector. After attaching the connector, call getToken with its UID (service/name) to request a short-lived, scoped token from the provider: Get started by browsing the connectors directory, or read the CLI reference. Read more ## iMessage support for eve agents DevFeed: [iMessage support for eve agents]() Original publisher: [Read original article]() Author: Owen Kephart Published: 2026-08-05T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Deployment]() Tags: [agents](), [channel](), [connectors](), [deployment](), [vercel]() ### AI overview Vercel announces iMessage support for eve agents through a new Photon channel. Each conversation stays in one eve session, incoming webhooks are verified, accepted messages are marked as read, and new messages can steer an in-progress reply. ### Source excerpt eve agents can now connect to iMessage through the new Photon channel. The channel keeps each iMessage conversation in one eve session, verifies incoming webhooks, and marks accepted messages as read. If more messages arrive while the agent is replying, they steer the in-progress reply instead of each getting a separate answer. The onMessage hook filters which messages the agent handles and adds context to a turn. Run eve add channel/photon-imessage to add the channel. iMessage delivery runs through Photon, so the command sets up a Photon project, registers your phone number, and scaffolds the channel: eve uses Vercel Connect to create the connector and configure Photon's webhook. On hosts without Connect support, choose Use portable credentials during setup and the channel reads its credentials from environment variables instead. Read the Photon channel docs to get started, or deploy an agent from a template. Read more ## Vercel Connect adds 100+ preset connectors DevFeed: [Vercel Connect adds 100+ preset connectors]() Original publisher: [Read original article]() Author: Ben Sabic Published: 2026-07-21T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Model Context Protocol](), [Shopify](), [Command-line interface](), [configuration]() Tags: [cli](), [configuration](), [connectors](), [mcp](), [product](), [shopify](), [update](), [vercel]() ### AI overview Vercel Connect now offers preset connectors for more than 100 services, including Shopify, Resend, Sanity, Okta, Workday, and Jira. These predefined configurations reduce setup work by supplying service metadata, authentication details, and MCP or discovery URLs, while users still need to provide required credentials and create the connector. ### Source excerpt Vercel Connect now includes preset connectors for 100+ services, including Shopify, Resend, Sanity, Okta, Workday, and Jira. Preset connectors are predefined configurations for supported services. They reduce manual setup by pre-populating the brand name, icon, auth type, and MCP or discovery URL. Unlike managed connectors, preset connectors don't register your app with the external service for you. Add a connector Select a preset from the connectors directory in the Vercel dashboard. Review the pre-populated configuration, add any credentials the service requires, and create the connector. You can also start from the CLI: Today, vercel connect create opens the dashboard to complete setup. Full CLI support for preset connectors is coming soon. Request tokens After attaching a preset connector, request tokens the same way you do for any other Connect provider. Call getToken with the connector's UID (service/name) to receive a short-lived, scoped token: To get started, browse the preset connectors or learn more in the documentation. Read more ## Stream Oracle changes to ClickHouse in real time DevFeed: [Stream Oracle changes to ClickHouse in real time]() Original publisher: [Read original article]() Author: Prakhar Garg Published: 2026-07-07T00:00:00Z Content type: tutorial Language: en Sources: [Redpanda]() Topics: [clickhouse](), [Redpanda-Connect](), [Oracle Database](), [Kafka](), [real-time](), [data](), [Database](), [YAML]() Tags: [clickhouse](), [connectors](), [data](), [database](), [event](), [integration](), [kafka](), [oracle](), [pipeline](), [real-time](), [redpanda-connect](), [schema](), [yaml]() ### AI overview A hands-on walkthrough shows how to stream Oracle change data capture events through Redpanda Connect into ClickHouse in real time. It uses Oracle LogMiner and YAML-configured pipelines, with a Redpanda topic serving as an intermediate store before data is delivered to ClickHouse or other destinations. ### Source excerpt A hands-on walkthrough of the new Oracle input in Redpanda Connect. No Debezium, no Kafka Connect runtime, no JVM. ## Real-time Change Data Capture with Redpanda Connect and MySQL DevFeed: [Real-time Change Data Capture with Redpanda Connect and MySQL]() Original publisher: [Read original article]() Author: Chandler Mayo Published: 2026-07-02T00:00:00Z Content type: tutorial Language: en Sources: [Redpanda]() Topics: [MySQL](), [Kafka](), [Databases](), [Docker Compose](), [real-time](), [Docker](), [SQL]() Tags: [apache-kafka](), [connectors](), [container](), [docker](), [event](), [how-to](), [kafka](), [mysql](), [network](), [pipeline](), [real-time](), [sql](), [tutorial](), [volume]() ### AI overview A step-by-step tutorial for building a real-time change data capture pipeline with MySQL and Redpanda Connect. It explains how row-level inserts, updates, and deletes become downstream events without polling, using compatibility with the Kafka Connect ecosystem. ### Source excerpt A step-by-step tutorial on how to stream every insert, update, and delete from your database using MySQL and a faster, simpler alternative to Kafka Connect. ## Vercel Connect: Secure access to external services for your agents DevFeed: [Vercel Connect: Secure access to external services for your agents]() Original publisher: [Read original article]() Author: Hannah Hearth Published: 2026-06-17T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Authorization](), [SDKs](), [API](), [API keys](), [Command-line interface](), [GitHub](), [Slack](), [Model Context Protocol](), [dashboards]() Tags: [agent](), [agents](), [apis](), [cli](), [connectors](), [external](), [github](), [mcp](), [sdk](), [slack]() ### AI overview Vercel Connect gives apps and agents secure, runtime access to external services through scoped, short-lived tokens. It supports connector management, automatic token refresh, environment isolation, revocation, provider webhooks, and dedicated or generic connectors. ### Source excerpt Vercel Connect lets your apps and agents access external services like Slack, GitHub, Salesforce, and your own custom APIs without storing a long-lived provider secret in your environment. You register a connector once, and your code requests scoped, short-lived tokens at runtime, only when it needs them. You can create a connector from your dashboard or the Vercel CLI: Your agent can then request a token from it at runtime, only when it needs it. The SDK fetches and refreshes that token automatically, so there is no secret for you to store or rotate by hand: Scoped tokens Each token is scoped to the task in front of it, with granularity that depends on the provider. A GitHub token can be limited to a single repository and read-only, instead of your whole organization. An agent gets exactly the access a task needs, never broad standing access to everything. A token can also be tied to a specific user instead of the app. It then acts with that user's identity and inherits their permissions, so the agent can do only what that user is allowed to do: Isolation and revocation A connector only works in the environments you attach it to, so you can run separate connectors for development, preview, and production. This means if a token leaks in development, it cannot be used against production: Because access is issued as tokens, you can revoke it with a single command, either your own or every token a connector has issued across all users and installations: Triggers Events can also flow from a provider to your app. With triggers enabled on a connector, Vercel Connect verifies the provider's incoming webhooks and forwards them to the projects you choose, so a new Slack message can reach an agent that acts on it. Triggers support Slack, GitHub, and Linear in Beta, and a connector can forward to up to three projects: Connectors and adapters Dedicated connectors for Slack, GitHub, Linear, Discord, Notion, Salesforce, Figma, and Snowflake are available from the dashboard, along ## Harness May 2026 Product Updates: 60+ New Features DevFeed: [Harness May 2026 Product Updates: 60+ New Features]() Original publisher: [Read original article]() Author: Chinmay Gaikwad Published: 2026-06-03T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [MCP](), [MCP Server](), [Development](), [Artificial Intelligence](), [ai-coding](), [Security](), [Claude]() Tags: [2026](), [agentic](), [ai](), [ai-coding](), [ai-infrastructure](), [api](), [claude](), [claude-code](), [coding-assistant](), [connectors](), [cves](), [development](), [features](), [infrastructure](), [integration](), [mcp](), [mcp-server](), [product-updates](), [security](), [updates]() ### AI overview Harness reports more than 60 product updates shipped in May 2026 across AI-native development, software delivery, security, cost management, and engineering insights. Highlights include AI cost tracking, AI adoption metrics, Claude connector access, and expanded MCP Server capabilities. ### Source excerpt See 60+ Harness updates from May 2026 across AI-native development, software delivery, security, artifact management, cost visibility, and engineering insights. | Blog ## Harness MCP Server Available in Claude Connectors Directory DevFeed: [Harness MCP Server Available in Claude Connectors Directory]() Original publisher: [Read original article]() Author: Rohan Gupta Chinmay Gaikwad Published: 2026-06-01T00:00:00Z Content type: release Language: en Sources: [Harness Blog]() Topics: [MCP Server](), [Model Context Protocol](), [Claude](), [AI Agent](), [Platform Engineering](), [API]() Tags: [ai](), [claude](), [connectors](), [developers](), [engineering](), [mcp](), [mcp-server](), [security](), [software]() ### AI overview Harness announces that its MCP Server is available in the official Claude Connectors Directory, allowing Claude users to discover and connect to Harness for structured, real-time access to pipelines, deployments, approvals, security scans, and software delivery context. The article attributes this context to the Harness Software Delivery Knowledge Graph. ### Source excerpt Harness is now available in the Claude Connectors Directory, giving teams real-time AI access to pipelines, builds, deployments, security scans, approvals, and software delivery context. | Blog ## clickhousectl v0.2.0: Postgres, ClickPipes and more DevFeed: [clickhousectl v0.2.0: Postgres, ClickPipes and more]() Original publisher: [Read original article]() Author: Al Brown Published: 2026-05-20T20:54:03Z Content type: release Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [API](), [Cloud](), [SQL](), [Command-line interface](), [Rust](), [API keys](), [Kafka](), [Docker]() Tags: [api](), [api-keys](), [cli](), [clickhouse](), [cloud](), [cloud-services](), [connectors](), [data](), [docker](), [http](), [kafka](), [release](), [rust](), [sql](), [update]() ### AI overview ClickHouse releases clickhousectl v0.2.0 with support for local and ClickHouse Cloud-managed Postgres, ClickPipes management, SQL over HTTP for Cloud services, agent-friendly output changes, and a standalone Rust client library for the ClickHouse Cloud API. ### Source excerpt We're releasing clickhousectl v0.2.0. This release adds Postgres, ClickPipes, SQL over HTTP, a few agent-friendly output tweaks, and a standalone Rust client library for the ClickHouse Cloud API. ## How to design agentic tools for work DevFeed: [How to design agentic tools for work]() Original publisher: [Read original article]() Author: Jenny Xie Published: 2026-04-29T16:44:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Artificial Intelligence](), [Google](), [Orchestration](), [User experience (UX)](), [dashboards]() Tags: [agentic](), [agentic-experience](), [connectors](), [design](), [gemini](), [google](), [google-cloud](), [how-to](), [interface](), [multi-agent](), [workflows]() ### AI overview The Gemini Enterprise team explains how it designed an agentic experience for complex, collaborative business work. The approach emphasizes simplicity, transparency, user intervention, and tools such as an AI Inbox, visual dashboards, connectors, and shared project spaces. ### Source excerpt The Gemini Enterprise team shares their approach to making complex, multi-agent workflows feel simple, intuitive, and trustworthy. ## Introducing Iceberg output for Redpanda Connect DevFeed: [Introducing Iceberg output for Redpanda Connect]() Original publisher: [Read original article]() Author: Prakhar Garg Published: 2026-03-05T00:00:00Z Content type: release Language: en Sources: [Redpanda]() Topics: [Apache Iceberg](), [Redpanda-Connect](), [Streaming](), [Routing (disambiguation)](), [schema-evolution](), [YAML](), [data]() Tags: [apache-iceberg](), [connectors](), [integration](), [pii](), [redpanda-connect](), [routing](), [schema-evolution](), [streaming](), [yaml]() ### AI overview Redpanda introduces an Iceberg output for Redpanda Connect that writes streaming data directly to Apache Iceberg tables through declarative YAML pipelines. The component supports transformations, enrichment, PII removal, and content-based routing across Redpanda Connect inputs and processors, enabling data from sources such as HTTP webhooks, Postgres CDC streams, and GCP Pub/Sub to reach lakehouse tables with less infrastructure and configuration overhead. ### Source excerpt Land any data into Apache Iceberg with Redpanda Connect. Maximize infra density, automate schema evolution, and scale 1-to-many routing without the toil. ## Branches are GA: data infrastructure for agents DevFeed: [Branches are GA: data infrastructure for agents]() Original publisher: [Read original article]() Author: Jorge Sancha Published: 2026-02-24T12:00:00Z Content type: release Language: en Sources: [Tinybird]() Topics: [Data Infrastructure](), [Kafka](), [Amazon S3](), [ci](), [Development]() Tags: [agentic-development](), [agents](), [ci](), [connectors](), [data](), [data-infrastructure](), [development](), [kafka](), [product-updates](), [s3](), [workflows]() ### AI overview Tinybird announces general availability for Branches, adding Kafka, S3, and GCS connectors, CI preview deployments, and agentic development workflows. ### Source excerpt Branches now support Kafka, S3, and GCS connectors, preview deployments from CI, and agentic development workflows. Branches are how agents develop with Tinybird. ## Tinybird, now in TypeScript DevFeed: [Tinybird, now in TypeScript]() Original publisher: [Read original article]() Author: Jorge Sancha Published: 2026-02-17T00:00:00Z Content type: release Language: en Sources: [Tinybird]() Topics: [TypeScript](), [SDK](), [Command-line interface](), [Development]() Tags: [autocomplete](), [cli](), [connectors](), [development](), [product-updates](), [sdk](), [typescript]() ### AI overview Tinybird introduces a TypeScript SDK for defining datasources, pipes, and connectors as TypeScript code, with type-safe ingestion, query autocomplete, and a CLI. ### Source excerpt Introducing Tinybird's TypeScript SDK. Define datasources, pipes, and connectors as TypeScript code. Get type-safe ingestion, autocomplete for queries, and a CLI that feels like modern app development. ## A free version of ChatGPT built for teachers DevFeed: [A free version of ChatGPT built for teachers]() Original publisher: [Read original article]() Published: 2025-11-19T00:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [ChatGPT](), [Artificial Intelligence](), [Security](), [Responsibility & Safety](), [Learning]() Tags: [ai](), [chatgpt](), [collaboration](), [compliance](), [connectors](), [education](), [free](), [generation](), [gpt](), [privacy](), [product](), [responsible-ai](), [security](), [tools](), [uploads]() ### AI overview OpenAI introduces ChatGPT for Teachers, a secure workspace with education-grade privacy, security, compliance, and administrative controls for teachers and school leaders. It is free for verified U.S. K-12 educators through June 2028 and includes features such as GPT-5.1 Auto, search, file uploads, connectors, and image generation. ### Source excerpt ChatGPT for Teachers is a secure workspace with education-grade privacy and admin controls. Free for verified U.S. K-12 educators through June 2027. ## Introducing low-code MCP servers in Redpanda Cloud DevFeed: [Introducing low-code MCP servers in Redpanda Cloud]() Original publisher: [Read original article]() Author: Johannes Brüderl Published: 2025-10-28T00:00:00Z Content type: article Language: en Sources: [Redpanda]() Topics: [Model Context Protocol (MCP)](), [Low code](), [AI Development](), [Cloud](), [YAML](), [stream-processing](), [PostgreSQL](), [Redis]() Tags: [ai](), [ai-agents](), [announcement](), [anthropic](), [apis](), [applications](), [cloud](), [connectors](), [kafka](), [low-code](), [mcp](), [postgresql](), [redis](), [servers](), [tool](), [yaml]() ### AI overview This article introduces Redpanda Cloud Remote MCP, a managed service for building MCP servers with low-code YAML. It explains how the service uses Redpanda Connect and more than 300 connectors to link data sources, APIs, and databases with AI applications, enabling standardized access to live organizational context. ### Source excerpt Introducing Redpanda Cloud Remote MCP, a managed solution for low-code MCP servers that easily integrates your data sources with AI apps. [Next page]()