Context OSBy Accolade Solutions
Menu

How it works

A clear record.
A continuous thread.

Capture the decisions. Preserve the reasoning. Give the next authorized agent a verified starting point.

CaptureReviewContinue

01 Capture

Capture the work
that matters.

Keep your project context in a clear, portable format. Write in Markdown, organize your files, and capture the decisions behind the work.

For a new water-quality product line, that means keeping the pilot scope, supplier questions and next engineering review together.

Example project New Product Line — Water Quality
project-context.md

From concept to pilot.

Current state
The initial plan covers ten pilot sites. Two sensor options are shortlisted; supplier selection is still open.
Decision
Start with monitoring and alerts. Keep automated dosing out of the first release.
Next action
Engineering will compare installation and calibration requirements, then prepare the pilot checklist.
Open question
Who owns calibration and support at each pilot site?

02 Review

Make changes
deliberately.

A supplier review changes the rollout plan. Keep the existing decision visible, explain the proposed change, and let the project owner review it.

The next session should know both what changed and why.

Water Quality · Pilot scope · Awaiting review

CURRENT RECORD

Ten-site pilot

Begin installations at ten customer sites after selecting a sensor supplier.

PROPOSED CHANGE

Three sites first

Start at three sites. Review installation effort and calibration support before expanding to the remaining seven.

Reason for the change

The two shortlisted sensors have different calibration requirements. A smaller first phase lets the team validate its support plan before scaling.

Decision needed: The project owner must approve the revised scope before it replaces the current record.

Review checks the current revision before saving. A changed record requires a fresh proposal.

03 Continue

Continue in the
tool you choose.

Once the three-site pilot is approved, carry that decision into the next tool. Bring the agreed scope, open questions and next action into your next session.

ChatGPT / CodexClaudePerplexity AIMicrosoft / GitHub CopilotPersonal LLM

One project record. A useful next step.

“Use the water-quality project record to draft the three-site pilot checklist. Flag decisions that still need approval.”

Use a compatible MCP connection with project access, or bring your Markdown files into a tool that accepts them. Client compatibility, requested permissions, and approval presentation vary.

Explore connection options →

Using the desktop companion with Codex or Claude Code? Follow the session memory setup guide to capture new activity and review updates to your project record.

04 Clear boundaries

Your context has
clear boundaries.

Keep the right information in the right place, with separate personal, organization and project permissions.

Personal contextYour working preferences
Organization accessShared rules and guidance
Project contextDecisions, documents and handoffs

Organization membership does not grant access to every project.

Give the next session a better start.

Your work deserves a continuous thread.

Open Context OS