Workspace context
Durable GTM memory: company profile, ICP, positioning, prompts, assets.
Workspace context is the long-lived state that AI assistants and workflows draw on when they act on your behalf. It survives across sessions and across operators.
Shape
The context profile is divided into sections that can be partially updated:
| Section | Fields |
|---|---|
company | name, domain, category, geography |
offering | products, value propositions, use cases |
icp | target accounts, personas, disqualifiers |
market | competitors, alternatives, segments |
gtm_stack | CRM, outbound tools, channels |
custom | tone, user preferences, constraints |
A profile is "complete" when company, offering, and icp have content. market and gtm_stack are still useful enrichment for downstream workflows, but they do not block onboarding completion.
Context assets
Beyond the profile, you can attach typed documents:
| Asset kind | Purpose |
|---|---|
playbook | Operational guides for a GTM motion |
strategy | High-level GTM approach |
campaign | Campaign brief, target segment, offers, and copy direction |
positioning | Messaging, differentiators, objections, and proof points |
persona | Buyer or user profile |
competitor | Notes on a market rival |
research_note | Ad-hoc research output (e.g. from onboarding) |
other | Flexible supporting context |
Resolving
oxygen context resolve --purpose general --require-ready --jsonThe resolver returns a task specific, revision-pinned context bundle. Purpose can be general, lead_sourcing, qualification, outbound_copy, or workflow_design — each requires different sections.
If the resolver returns context_missing or missing_required_context, run oxygen onboarding start to fill in the gaps.
Bootstrapping
oxygen onboarding start is an idempotent flow that:
- Confirms the active user and organization.
- Reports which context sections are present or missing.
- Returns a skill URL that guides an agent through the onboarding research and persistence steps.
oxygen onboarding start --jsonThe returned skill URL is the canonical procedure. Review the generated profile before using it for lead sourcing, scoring, or outbound copy.
Working with context
oxygen context profile get --json
oxygen context profile update \
--data-json '{"icp":{"segments":["B2B SaaS at $1M-$20M ARR"],"personas":["Founder","Revenue leader"]}}' \
--summary "Refine ICP" \
--json
oxygen context assets list --json
oxygen context assets upsert --type playbook --title "Outbound Q1" --body "..." --json
oxygen context assets archive <asset-id> --jsonUpdates merge by section. Re-running update with only the icp field leaves company and offering untouched.
Related
- Approvals — review context changes before letting them drive live work.
- Workflow templates — templates and blueprints can declare required context sections.