neosianneosian

Memory for the agent you already use

Pick up where
you left off.

Keep the investigation, the decisions and the next step. Move between agents without starting over.

Install neosian

curl -fsS https://neosian.com/install | sh
Connect your agent Other install options

Your agents. Your context. Your storage.

Open source 2.11.1
Claude CodeBefore you leave

Checkout retries are failing.

Found
The retry reuses an expired token.
Tried
A longer timeout didn’t help.
Next
Refresh the token. Add a regression test.
CodexNext session

Continue the checkout fix.

Codex

The timeout didn’t help. I’ll refresh the token and add the regression test.

The next step survives the switch.

Connect the agent
you already use

Search your memory

The answer exists.
Your agent finds it.

The rollback plan. The decision behind a change. That detail you saved three sessions ago.

Your agent searches current project knowledge and gets the source, its revision and the relevant text. Even when it wasn’t in the context at the start.

Explore memory search
CodexIn your project

What’s the rollback procedure for checkout?

Search memorycheckout rollback
Checkout rollbackCurrent · v3
  1. 01Disable checkout_v2.
  2. 02Redeploy the last stable release.
  3. 03Verify payment success before reopening traffic.
/project/runbooks/checkout
Find the answer. Keep the source.

Remember to come back

“Temporary” deserves
a follow-up.

Leave a reminder with the project. When it’s due, it comes back in your next active session—even if you’ve switched agents.

Still blocked? Snooze it with what you found. The next check starts with that context.

Explore reminders
Claude CodeThis week

Remind me next week to check whether we can remove the checkout workaround.

Reminder saved for next week

One week later · next project session

CodexBack in the project
Reminder due

Check whether we can remove the checkout workaround.

Codex

Still blocked upstream. Keep the checkout workaround for now.

↗ Snoozed 7 days Finding kept

A follow-up with its context still attached.

Bring your way of working

Good instructions are worth keeping.

Reusable skills live alongside your knowledge. Choose what your agent can load, inspect each revision, and bring the same instructions to your next project.

Explore skills

A place for your context

You choose
where it lives.

Start with ordinary files on your machine. Use Postgres for distributed writers, or connect to a state service over HTTP.

Mounts and permissions determine what each agent can read or change. Profiles select the context you bring along.

Understand your storage options

Files on your machineA directory you can inspect and back up.

Default

Your PostgresShared storage for distributed writers.

A remote state serviceConnect through authenticated HTTP.

Start with your next session

Install. Connect.
Carry on.

One binary provides CLI, MCP and HTTP access. No model account or hosted service is needed to run neosian locally.

Read the quickstart

01 Install neosian

curl -fsS https://neosian.com/install | sh

or

npm install -g [email protected]

One binary provides CLI, MCP and HTTP. Existing v1 users should read the migration guide. Browser downloads can trigger security warnings while publisher signing is deferred; installation details.

02 Connect your clients

neosian setup --write
neosian status

Choose the clients to connect, then restart them. Profiles select your context; new profiles start with conversation capture off.

Choose your context and recording settings

A small, open core.

Use the CLI, MCP or authenticated HTTP from your own application. Your host owns the models and orchestration; neosian supplies the state.

Source on GitHub ↗Read the documentation ↗For agents: llms.txt ↗
What is coming

A hosted neosian is planned for app.neosian.com: your projects and agents behind one URL, with a screen for the ledger and history search. Today you can run the state process yourself.

Explore the current deployment options or hear about what comes next.