Checkout rollout uses project-scoped context
The rollout note is available to the platform project, with customer identifiers redacted before storage.
Shared memory
for your team's agents.
Your people use ChatGPT, Claude, and Cursor every day. Ambience captures what they figure out, then gives every other agent the same context the next time anyone asks.
Without it,
every session starts from zero.
Without Ambience
› Draft the kickoff for next week's launch.
→ Who's the audience here?
→ What tone do you usually use?
→ Any examples of past launches I should mirror?
→ Any constraints I should know about?
▌
With Ambience
› Draft the kickoff for next week's launch.
→ Loaded 4 team memories: tone of voice, audience, last launch postmortem, calendar constraints.
→ Drafting in the team's voice. Opening with the metric the audience converts on.
▌
Context is only useful when control travels with it.
The public site can show the same primitives as the app: memory records, read rules, redaction, and audit events. This is the trust story without another abstract feature grid.
Capture
Session takeaways are proposed when work finishes.
Redact
Secrets and identifiers are stripped before storage.
Scope
Personal, team, project, org, or sensitive access is applied.
Audit
Every read and write becomes inspectable evidence.
- OLOlliegrantedteam:platform
Granted contributor access to the project team.
- COCodexcreatedproject:checkout
Captured a project decision from an agent session.
Every decision your team makes. Kept, scoped, shared.
Browse the memories your agents have written. Scope them. Audit who read what. Edit, redact, or revoke any time.
Scope
Personal12
Team47
Project18
Org6
Sensitive3
People
Maya · Design14
Ali · Ops11
Jordan · Sales9
Sources
Claude Code31
Cursor9
ChatGPT7
Team · Voice
Conversational, opinionated, never "leverage."
Active voice. Numbers in the first sentence of every announcement.
Maya · 4d ago · read 11×
Team · Audience
Series A-C SaaS, 50–500 people.
Decision cycle 18–28 days.
Ali · 2w ago · read 23×
Team · Vendors
Always require SOC 2 + COI before kickoff.
No exceptions for vendors handling customer data.
Ali · 1mo ago · read 17×
Team · Process
Standups async, decisions in writing.
No verbal commitments without a Linear ticket.
Jordan · 3w ago · read 9×
Team / Voice
Conversational, opinionated, never "leverage."
● TeamSource · Claude Code11 reads
Body
Active voice always.
Numbers in the first sentence of every announcement.
Never start with "We're excited to…" Start with the metric.
Avoid: leverage, synergy, robust, seamless, unlock.
Numbers in the first sentence of every announcement.
Never start with "We're excited to…" Start with the metric.
Avoid: leverage, synergy, robust, seamless, unlock.
Why
Last 12 months: posts opening with a metric got 2.8× engagement vs ones opening with "We're excited."
Read by Ali · Tue 09:14via Claude Code
Read by Sarah · Mon 16:02via ChatGPT
Saved by Maya · last Frivia Claude Code
Server-side redaction. Per-scope reads. Append-only audit.
● Captured
- Conventions, decisions, what's worked
- The reasoning behind every call
- Failures and what resolved them
- Skills your team has earned
● Redacted before storage
- API keys, secrets, tokens
- Customer emails, phone numbers, addresses
- Account names and tenant identifiers
- Anything matching your DLP rules