Does Ambience need direct Linear credentials?

No direct connector is required for the lightweight agent-powered path. A user can approve an agent that already has access to source material, choose what should be included, and save the redacted result into Ambience with source metadata.

What does Ambience add to Linear?

Ambience turns approved source material into typed, scoped, source-linked memory that future agents can reuse under redaction, access, and audit controls.

Connection

Linear + Ambience.

Updated 2026-06-07 · Issues and planning

Seed Ambience memories from approved Linear issues, specs, and delivery decisions through agents that already have Linear access.

Linear is where teams decide what should happen. Ambience is where those decisions become reusable, scoped context for future agents.

Ambience stores the reusable decision, convention, skill, failure, or reference. The original linear issue stays visible as source context.

Example source-linked memories

decision

Use WorkOS org membership as the access boundary

Source: Linear issue: AUTH-128

failure

Avoid unbounded transcript scans during onboarding

Source: Linear issue: ONB-42

From ticket to team memory

When a user asks an approved agent to summarize a Linear ticket or project, Ambience can save the durable decisions, conventions, risks, and references as typed memories.

The original Linear issue stays the source of record. Ambience stores the reusable context agents need later.

What future agents get

A Claude Code or Codex session working in the same project can start with the relevant Linear-derived memories: rollout constraints, accepted tradeoffs, customer caveats, and known failure modes.

Governed by scope

Project-scoped memories stay with the project. Team-wide planning conventions can be promoted to team or org scope. Sensitive customer notes can stay restricted.