articulate.
LOCAL FIRST · EARLY ACCESS

Context for
the way you
understand.

The way an explanation clicks for you deserves a place in your AI context.

Articulate turns available local coding activity into working preferences you review—so your next agent has a starting point for how to explain, build and collaborate with you.

Free testing release. Built for feedback, still evolving.

DIFFERENT TOOLSONE SHARED STARTING POINT
Codex Claude Cursor
WORKING PROFILEHow I like to work through a task.
✓ Reviewed
WHEN WE’RE BUILDING
  • Start with the intended outcome.
  • Make the next step concrete.
  • Explain the tradeoff that matters.
Selected by you. Shared by permission.
Illustrative preferences, not an actual user’s data.
FOR YOUR LOCAL CODING SETUP

Codex Claude Code Claude Desktop Cursor

CONNECTED THROUGH MCP

THE IDEA BEHIND ARTICULATE

Same information.
A different way in.

Imagine ten people reading the same technical guide. One asks for an example. Another wants the steps. A third wants the reasoning behind the decision.

Think about the last time something finally made sense. What helped: a concrete example, a connection to work you already knew, or a chance to try it yourself?

That is the motivation behind Articulate: give you and your AI a clearer, shared starting point for how to work through things together. Your preferences can change with the task, the project and what you already know.

Today, the local pilot starts with requests you have actually made in supported coding-agent history. You review what it finds and decide what travels to another agent.

CONVERSATION MEMORY

What should carry forward?

Past messages, facts and decisions give an agent continuity.

ARTICULATE’S FOCUS

How should we work through it?

Reviewed preferences add guidance for explaining and collaborating—such as walking through an example before the abstraction, or showing the cause before a fix.

Memory tools can support personalization too. Our focus is making your reviewed working preferences portable across agents. The pilot does not measure intelligence or claim proven learning gains.

How it works

THE FLOW

Bring the context.
Keep the control.

Start with one project or your work across projects. Choose your agents when you’re ready to connect.

  1. 01

    Bring your work together.

    Find supported local activity from Codex, Claude Code and Cursor. Articulate can use the traces available on your device; cloud-only and deleted chats may be missing.

  2. 02

    Review what carries forward.

    Check suggested preferences, edit them, or keep your own. The default scan finds explicitly stated requests. Broader interpretation needs a configured local model.

  3. 03

    Connect on your terms.

    Choose which agents can receive your reviewed preferences. Each connection needs its own approval. Use profiles and saved workflows for different kinds of work.

LOCAL BY DESIGN

Your activity.
Your decisions.

A profile should be useful to you.
And understandable to you.

Read the privacy notes

History stays on your device.

Raw imported activity is not returned through Articulate’s MCP tools. Connected AI providers can process the reviewed context you choose to share.

Preferences, with boundaries.

They guide how an agent presents its work. Your current task, facts and safety still take priority. A stored preference is not proof of a better answer.

Change your mind whenever.

Review profiles, revoke an agent’s access, or erase Articulate’s local data through the CLI. Removing a package and deleting saved data are separate steps.

SMALL START. REAL FEEDBACK.

Try it on your
own kind of work.

Install the public pilot, run the guided setup, and try one real task with an agent you use.

  1. Start with Node.js. Install Node.js 24 LTS ↗, version 24.22.2 or newer within 24.x. No Node or npm yet? Start here before copying the install command.
  2. Check this terminal. Run node --version and npm --version. Check your version and get help ↗
  3. Install once, then choose your project. The command installs Articulate globally. Changing project folders won’t fix an unsupported Node version.

Local pilot for macOS, Windows and Linux. Keep an existing project’s Node setting; use a supported runtime in the terminal running Articulate.

AFTER THE NODE CHECKPILOT
npm i -g articulate-local@pilot
articulate

One project
My work across projects
Connect my agents

Then run articulate in your project.
↑ / ↓ choose · Enter confirm · You review before sharing

IN TESTING

The public pilot is available on npm. Browser account connection is being tested separately; required CLI/plugin sign-in is not in the published pilot. No paid plan or Pro trial is running.

HELP SHAPE WHAT’S NEXT

Did it save a repeat explanation?
Tell us where it helped.

Share your feedback

Describe the experience. Keep secrets and private conversations out of your report.