Explore the solution.

See what stays personal, what your team shares, and the dashboard we’re building.

← Back to the overview

Your preference.
Your team’s decision.

Personal by default. Shared only when explicitly requested.

ChatGPT01 / FINISH THE WORK

“Always answer me in short bullet points. We launch v1 on Friday 24 October — share that with the team.”

The connected client calls the memory tools.

02 / SAVE IN THE RIGHT SPACE

Personal

THE DEFAULT

Answer me in short bullet points.

Available to your account.
Not shared with teammates.

Shared

EXPLICIT REQUEST

v1 launches Friday 24 October.

A common decision for members of the project.

03 / CONTINUE IN ANOTHER AI

Your next chat

Claude answers you in short bullet points.

Your teammate’s chat

Grok already knows v1 launches on 24 October.

Two spaces.
A deliberate boundary.

PersonalTHE DEFAULT

Your working context.
For your account.

Preferences, individual notes and background for the way you work.

Access through Boring Context: Your account and its connected AI clients.
Where does new AI memory go?: Here, unless the request explicitly asks to share it.

EXAMPLE

“Always answer me in Swedish, in short bullet points, and skip the small talk.”

SharedEXPLICITLY SHARED

Common project knowledge.
For the whole team.

Shared decisions, project facts and context that members need to work together.

Access through Boring Context: Members of that shared space and their connected AI clients.
How does AI memory get here?: The request explicitly asks to share it with the team.

EXAMPLE

“We launch v1 on Friday 24 October. Five testers get access first and Melker owns the release checklist. Share that with the team.”

Memory you can see.
Context you can manage.

Find the context.

Explore memories by project and category, switch between spaces, and search for what you need.

Understand what changed.

Review a memory’s history, including earlier text and who changed it.

Keep information current.

Edit memory content, move it between projects, and manage deletions in the dashboard.

Recover a deleted memory.

The internal dashboard includes a Deleted view and restoration of saved information.

Projects and spaces

Organise shared project context alongside your own working information.

Goals and deadlines

Organise date-based memories in a checklist and calendar.

Backup and restoration

Export a backup and review missing records before restoring them.

These features are part of the internal dashboard work. Testing is in progress; public access comes later.

Good questions.
Straight answers.

What it does. How it connects.
Where we are today.

Still curious? hello@boringcontext.com

Is this another chatbot?

No. Boring Context is a shared memory layer for AI tools. You keep using those tools; the connected client can retrieve context and save information through Boring Context.

What can become a memory?

Project facts, decisions, goals, deadlines, preferences and lessons. We’re also extending the model with Documents for research and reports, multiple categories and Work/Private Life context. Those extensions are part of the development direction.

Does it automatically record every conversation?

No. It does not automatically archive every conversation. A connected client must call the memory tools; those calls can extract structured information from a message or completed task.

Can the team see my personal context?

Personal and team memory are separate in the internal version. Memory stays personal by default and is shared with the team when the request explicitly asks for it.

Which tools are connected?

Claude Desktop, ChatGPT and Grok are the current AI clients in the internal integration work. Workplace connections are part of the development plan and are listed separately. Availability depends on implementation and compatibility testing.

Can I use Boring Context today?

Public access is not open yet. We’re testing the internal version before opening it more widely. This website explains what we’re building and the people behind it.

Can I edit or remove a memory?

Memory management belongs in the dashboard. The internal dashboard work includes editing, history, deletion and restoration. Deletion is not exposed as an MCP tool.

Does the dashboard decide what my AI shares?

No. Selecting Team in the dashboard changes the space you’re viewing. Memory saved through an AI client remains personal unless the request explicitly asks to share it.

Will it work with every AI tool?

A client needs compatible support for the MCP connection and must call the memory tools. We verify clients individually instead of assuming that every app works.