articulate.

FROM FIRST RUN TO YOUR NEXT CONVERSATION

A little setup.
A better starting point.

Choose the work Articulate can learn from. Review what it finds. Decide which agents can use it.

A look at the account-connected preview. Screens below use John Smith, a sample project and simulated account responses. Codes and links are demonstrations. The public npm pilot works locally without an account; hosted sign-in and the updated agent picker are being prepared for a future package release.

Select any screenshot to view it at full size.

01

Start in your terminal.

In the account preview, run articulate login. Press Enter when you’re ready to open your browser. If it doesn’t open, paste the private link printed in the terminal into your browser.

The public local pilot starts with articulate. See installation instructions ↗

Articulate block-letter banner and terminal-first sign-in prompt with a demo link
Account preview · Captured from the real login renderer with a simulated handoff. The demo link cannot connect a terminal.
02

One account. A short introduction.

Continue with Google or GitHub. The first time, add your name, work or study setting, and role. Choose Company, School or Startup to enter its name; choose N/A to leave it out.

Those details are saved with your account in Supabase. On later sign-ins to that account, the introduction is skipped and you’re welcomed back.

Articulate account screen with Continue with Google and Continue with GitHub
Browser preview · Both sign-in choices. Provider passwords are entered on the provider’s own page.
First-time introduction filled with John Smith, Sample Studio and Founder
Browser preview · Demo account: John Smith at Sample Studio. Account details and local working preferences are separate.
03

Bring the code back to your terminal.

Copy the one-time code from the browser into the same terminal where you started sign-in. Wait for “You are now signed in.” Then it’s safe to close the browser page.

Signing in connects your account. Choosing local history and approving agent sharing come next, as separate decisions.

Demo completion screen welcoming John Smith with a demonstration code, How it works and Docs links
Browser preview · Demonstration code only. Real codes belong in your terminal. The guide and docs open in a new tab.
04

Choose the work that matters.

Run articulate from the project folder you want to work with. Use ↑ and ↓ to move through the menu, then Enter to confirm. Articulate asks before reading local activity.

One project

Start here for a focused repository. The current folder sets the project scope. To choose a different one, change folders first, or run articulate project /path/to/project.

All local work

Choose this for patterns across your supported local projects. It covers attributable history on this device; remote-only or deleted conversations may be missing.

Actual terminal menu with One project selected and All local work as the next choice
Setup preview · Actual menu renderer with a sample project path. One project uses the current folder; it is not a cloud repository selector.
05

Your project scope. Your choice of agents.

Project scope chooses the work to review. The agent picker chooses which apps to connect. They answer different questions.

In the updated picker, use ↑/↓ to move, Space to select each agent and Enter to save. Choose only the tools you use. Installing a connection and allowing it to read your reviewed preferences are separate prompts; each selected agent has its own sharing approval.

Actual multi-select terminal picker with Codex and Cursor checked and Claude options unchecked
Setup preview · Actual picker renderer with controlled app-detection fixtures. Codex and Cursor are selected here; nothing was installed or shared during this capture.
06

Review, then carry it forward.

Articulate brings supported local activity together and suggests working preferences. Review them before keeping them. The quick scan finds explicitly stated preferences; deeper interpretation needs a local model.

Once an agent’s connection and sharing are approved, reload its MCP connection and start a new chat. You can manage profiles and shortcuts, revisit sharing, or disconnect agents from the local interface.

The useful test is your own work: does the next explanation need less correction? A saved preference is guidance, not a guarantee of better understanding.

Ready for your first project?

Open the setup docs ↗   Read the privacy notes ↗

For ambitious projects and organization-scale setups: cloud services coming soon.