articulate.

THE PRACTICAL DETAILS

Start small.
Make it yours.

Install the local pilot, choose your scope and bring reviewed preferences to your coding agents.

START HERE

Get your terminal ready

Articulate’s local npm package needs Node.js and npm on your computer. An npm command cannot run if those tools are missing.

  1. Install Node.js if needed. Use the official Node.js download page ↗ and choose the latest patch of Node.js 24 LTS for your OS. The pilot requires at least 24.22.2 within 24.x. The installer includes npm.
  2. Open a fresh terminal. Check the runtime selected in that terminal:
node --version
npm --version

If either command says “command not found” or “not recognized”, finish installing Node.js, reopen your terminal and check again. If you use a version manager, select a supported runtime there.

Checked in this browser only. No device detection or data sent.

Supported pilot minimums: 22.23.4 in 22.x, 24.22.2 in 24.x, or 26.13.0 in 26.x. Use the newest patch within a supported line.

A project folder does not contain its own Node installation by default. A version manager may switch versions when you enter it. Keep an older runtime your project needs; use a separate terminal with a supported Node for Articulate.

Install once, then run in your project

Once the Node and npm checks pass, install in your own terminal:

npm i -g articulate-local@pilot
cd /path/to/your-project
articulate

This installs articulate-local@0.0.1, the testing pilot. It works locally without an Articulate account or payment details. Keep a global install so agent connection paths remain stable.

Follow the visual walkthrough ↗

Choose one project or all local work

One project uses the current folder. You can also pass a project path directly:

articulate project /path/to/your-project

On Windows, for example: articulate project "C:\work\sample-project".

All local work looks across supported, attributable coding-agent history for your OS account:

articulate all

The scan asks for your approval. Review suggested preferences before keeping them. Local history coverage can vary; remote-only conversations and deleted chats may not be available.

Connect your agents

Follow the connection prompts after setup, or run:

articulate connect

Supported connections include Codex, Claude Code, Claude Desktop and Cursor. Their available conversation sources differ: a Claude Desktop connection does not imply access to its cloud chat history.

The updated preview lets you select hosts individually with Space, then save with Enter. This picker is newer than npm pilot 0.0.1. Each agent still needs its own sharing approval. Reload the connection in that app and start a fresh chat after setup.

Connection settings and permission to receive reviewed preferences are separate. Review sharing locally; see the privacy notes for disconnect and removal details.

Local package, plugins and hosted access

Available: the local npm pilot. Planned: verified plugin downloads and easier host-specific installation, alongside the npm package.

Hosting package downloads does not upload your profile. A remote MCP service is a separate component and is not available yet. It cannot read a profile on your computer without a separate, explicitly approved device connection or cloud copy. Neither is enabled by installing the pilot.

ACCOUNT-CONNECTED PREVIEW

Browser sign-in

The hosted Google/GitHub flow is available to preview testers using the account-enabled source build. It has not been added to the public npm pilot. If you’re testing that build:

  1. Run articulate login and press Enter. Use the private link if the browser doesn’t open.
  2. Choose Google or GitHub. On first use, complete your name, work setting and role. N/A leaves organization empty.
  3. Enter the browser’s one-time code in the initiating terminal. Wait for its sign-in confirmation before closing the page.

Later sign-ins to the same account skip the introduction. The session is saved in the OS credential store. Account login does not approve a scan or agent sharing.

Account-enabled commands:

articulate account status --online
articulate logout

Your account details are stored in Supabase. Chats, local project analysis and local working preferences remain separate. A cloud workspace and a web profile/preferences editor are planned, not available in this preview.

If something gets stuck

  • npm WARN EBADENGINE / unsupported engine? npm found Node, but it is below this package’s requirement. The installation may still say “changed 1 package”; that does not establish compatibility. Compare node --version with the minimums above, select a supported runtime, then reinstall under that runtime. Changing folders or repeating the same install won’t upgrade Node.
  • Using nvm? Run nvm install 24 and nvm use 24, then node --version, npm --version and the install command again. Global npm tools can be separate for each Node version. Do not change a project’s .nvmrc just for Articulate.
  • articulate not found after install? Reopen the terminal, check that the same supported Node version is selected, and reinstall there. Confirm your npm global executable directory is on PATH.
  • No browser window? Copy the private link from your terminal. Don’t share the full link.
  • Code expired or already used? Start a fresh login. Use its new link and code in the same terminal.
  • Already signed in? Check articulate account status --online. Use articulate logout before switching accounts in the preview.
  • No activity found? Check that you’re in the intended project and have supported local history. A connection to an agent does not download its cloud history.
  • An agent can’t see your preferences? Check its local sharing approval, reload its MCP connection, and start a new chat.

For help, email hello@i-ops.dev. Describe the step and error; keep login links, codes, private conversations and credentials out of your report.