Can we run without a separate issue tracker?
Yes for product and engineering delivery work managed in Stream Central. Many teams keep a tracker elsewhere for org process or adjacent teams; connectors help when you need that bridge.
Integrations
Developer Context First, Connectors Second
Stream Central’s strongest integration story is IDE and agent handoff. Optional connectors and API clients support import, link, create, and export workflows where they are shipped.
Integration Surfaces
Lead with the developer workstation and authenticated automation. Treat issue-tracker connectors as supporting compatibility, not the product promise.
Developer WorkflowLead surface
VS Code, Cursor, Spec Kit preset
Extend plan context, readiness findings, and implementation standards into the developer workstation instead of asking engineers to reconstruct them from browser tabs.
- VS Code / Cursor extension for work-item plans and status actions
- Agent handoff that can include readiness findings and standards
- Spec Kit preset that maps Stream Central artifacts into spec-driven delivery
- Export implementation standards for common agent config formats
API Clients & Automation
Key-based access for extensions and partner tools
Create named API clients for extensions, CLI tooling, partner systems, and other authenticated workflows that need controlled platform access.
- Named API clients with generated keys and rotation support
- Programmatic access for automation and third-party systems
- Shared auth model for extensions, CLI, and partner workflows
- Secure path for authenticated integrations without full user sessions
Feedback Ingestion & Public Sharing
External feedback API and public experiences
Bring customer signal in and share product narratives out without making every reviewer a platform user.
- External feedback submission with application-scoped client keys
- Public storyboard and showcase access for broader review
- Token-based sharing for external stakeholders
- Feedback experiences that stay tied to platform context
Optional Execution Connectors
GitHub, Azure DevOps, Jira
Where useful, link or import work from existing tools. Capabilities vary by connector—use precise verbs (import, link, create, update) rather than assuming full bidirectional sync.
- GitHub and Azure DevOps linking/create workflows for selected work artifacts
- Jira issue import into Stream Central work items
- Reduce duplicate context entry where connectors are configured
- Optional org compatibility—Stream Central remains the readiness-to-code system of record
SSO & Federated Identity
Microsoft Entra ID and social identity providers
Support single sign-on and federated identity patterns for organizations that need them.
- Single sign-on support for federated identity flows
- Federated Microsoft Entra ID support for enterprise organizations
- Social identity provider support where customer access requires it
- Email-first sign-in discovery and just-in-time provisioning patterns
Build On Top Of Authenticated API Clients
Use named API clients when you need secure access for partner systems, CI/CD automation, or developer tooling. Today that story is strongest around external feedback submission, developer workflows, and other key-based integrations.
Named API clients with generated keys
External feedback submission endpoint
Support for extensions, CLI tooling, and CI/CD automation
How teams typically connect
Most teams start with identity and IDE workflow, then add connectors only where they reduce friction.
Step 1
Connect identity
Configure Microsoft Entra ID SSO or use email-based sign-in. Organization admins invite team members from Settings.
Step 2
Enable developer workflow
Install the VS Code / Cursor extension, authenticate, and use plan download, readiness context, standards export, and completion actions.
Step 3
Add connectors only as needed
Optionally import or link work from GitHub, Azure DevOps, or Jira. Create named API clients for automation. Do not expect every connector to offer the same sync depth.
Integration FAQ
How deep are the issue-tracker connectors?
Depth varies. GitHub and Azure DevOps support selected link/create/update workflows. Jira currently supports importing issues into Stream Central. Always evaluate the exact verbs for the connector you need.
Does Stream Central support enterprise SSO?
Yes. Microsoft Entra ID federated SSO is supported for enterprise organizations, along with email-first discovery and social identity providers where required.
Can external stakeholders submit feedback without accounts?
Yes. The external feedback API and public storyboard/showcase experiences allow token-based sharing so reviewers can participate without full platform access.
Is there an API for custom integrations?
Named API clients provide key-based access for automation, CI/CD, extensions, and partner systems. See organization settings to create and rotate keys.
Start with readiness, not connector sprawl
See the readiness-to-code workflow first. Add integrations only where they support that path.