LoginSign Up
← Back to all sparks
P

Port

INFRA · APIS
Velocity2.5

Internal developer portal for platform engineering, service catalogs, and scorecards.

www.port.io ↗

Port now runs Claude agents end to end, acting as the user who started them.

developer-platformai-agentsidentityworkflow-orchestrationdashboards
◆Current state
Port's October release lets workflows create, run and archive Claude Managed Agents, stream their progress into the run log and use their output, with Port MCP access granted as the triggering user or a service account. Identity Propagation makes self-hosted GitHub, GitLab and Azure DevOps actions run with the triggering user's own credentials. Dashboards gain saved filter presets, advanced filter rules and a Board view in closed beta, and new orgs get a guided Solutions Onboarding.
◆Where it's heading
Port has spent 2026 turning its catalog into a governed place where both people and agents act. September let other apps inherit Port permissions; October carries the user's identity all the way into third-party tools and into agents, so audit logs show who really acted.
◆Prediction
Expect Identity Propagation to reach more integrations beyond the three self-hosted ones, and more agent providers to get the same end-to-end lifecycle support Claude has now.

◆Recent moves

  1. 4d ago

    Port Product Updates - What we built in October 2026

    October moves Claude Managed Agents from a connected integration to a full lifecycle inside Port workflows, and makes integration actions run as the user who triggered them. It extends September's identity work into third-party tools and agents rather than opening a new direction.

  2. 1mo ago

    Port Product Updates - What we built in September 2026

    ⚡ SPARK

    September moves Port from a place engineers visit to a layer other tools inherit from: custom apps authenticate with Sign in with Port, and Port properties now drive GitHub Rulesets directly. It extends the governance arc of Workflows GA, with scoped building permissions and a wide set of new native actions.

  3. 2mo ago

    Port Workflows reaches GA with Cursor agents and MCP scoping

    ⚡ SPARK

    Port Workflows reaching GA is the foundational move — it defines the governed orchestration layer that everything else (Cursor agent sync, Slack approvals, MCP permissions) plugs into. Adding Cursor Cloud Agent sync and triggering from workflows means Port can now orchestrate AI agent work alongside human approvals in a single governed flow.

  4. 3mo ago

    Port AI Builder executes catalog changes; Claude agents ship

    ⚡ SPARK

    Port AI Builder executing real catalog changes — with plan-before-execute and per-tool approval controls — shifts Port from a query interface to an active agent operating on engineering infrastructure. The Claude Managed Agents integration in the same release extends the catalog to include AI agent activity as first-class catalog data.

  5. 4mo ago

    Port Product Updates - What we built in June 2026

    Workflows in open beta with GitLab CI/CD triggers and external MCP server connections expands the orchestration surface significantly — more CI/CD systems covered, more external tools reachable from inside Port AI. The private pages and Slack thread memory round out usability gaps that would slow adoption.

  6. 5mo ago

    Port Product Updates - What we built in May 2026

    The public port-plugins repo opens the extensibility model and is the earliest signal of Port's ecosystem ambition. The multiple workflow triggers and sidebar redesign both reduce friction for teams building complex automation flows, and tracking Claude Code / Copilot usage natively extends Port's AI observability story.