Everlearn is a local-first continual learning engine for Claude Code, Codex, and other AI agents.
It gives agents a simple, repeatable way to save durable learnings, decisions, research, customer signals, workflows, prompts, and weekly reviews into a Markdown vault you own. The vault works well in Obsidian, but it is just folders and .md files.
Use this path during the AI for Ecommerce workshop:
Fast install/update:
curl -fsSL https://raw.githubusercontent.com/tripleyak/everlearn/v2026-05-27-workshop/scripts/install.sh | bash -s -- --ref v2026-05-27-workshop --profile ecommerceZIP install:
cd ~/Downloads
unzip everlearn-workshop.zip
cd everlearn
./scripts/setup.sh --profile ecommerceThen test one capture:
~/.everlearn/bin/everlearn capture \
--type signal \
--title "Customer asked for a cheaper bundle" \
"A shopper wanted a lower-priced starter bundle before buying the full kit."Open ~/Everlearn Vault in Obsidian to see the note.
./scripts/setup.sh creates:
~/Everlearn Vaultby default~/.everlearn/config~/.everlearn/bin/everlearn~/.claude/skills/everlearn~/.claude/commands/everlearn.md~/.codex/skills/everlearn~/.codex/skills/everlearn/commands/everlearn.md~/.codex/commands/everlearn.md~/.codex/prompts/everlearn.md~/.agents/skills/everlearn
The extra ~/.agents/skills install keeps the skill visible in shared skill runtimes that both Claude Code and Codex can read.
The curl installer stores the downloaded source at ~/.everlearn/source and can be rerun later to update the local skill and command files.
~/.everlearn/bin/everlearn capture --type learning --title "What worked" "The short version of the learning."
~/.everlearn/bin/everlearn capture --type decision --title "Use Shopify bundle test" "Decision and rationale."
~/.everlearn/bin/everlearn capture --type research --title "Competitor review notes" "Summary and source links."
~/.everlearn/bin/everlearn capture --type workflow --title "Weekly ad review flow" "Steps that should be reused."
~/.everlearn/bin/everlearn signalsweep --topic "standing desk customer complaints" -- --quick
~/.everlearn/bin/everlearn review
~/.everlearn/bin/everlearn verifyIn Claude Code, restart after setup and use:
/everlearn signal Customers keep asking whether the starter bundle includes replacement filters.
In Codex, restart after setup and use:
/everlearn signal Customers keep asking whether the starter bundle includes replacement filters.
Plain English also works:
Use Everlearn to capture the reusable learning from this session.
Everlearn is general. Profiles tune the default examples and folder suggestions:
general: everyday learnings, decisions, research, workflowsecommerce: customer signals, product ideas, marketplace research, ad learningscoding: repo learnings, architecture decisions, debugging notes, reusable commandsresearch: source notes, evidence, claims, synthesisoperations: SOPs, process decisions, recurring reviews
The workshop uses ecommerce, but attendees can switch later:
./scripts/setup.sh --profile generalEverlearn starts explicit by design. It does not scrape private transcripts, index your whole computer, or send notes to a cloud service.
Good captures are short, reusable, and specific:
- What changed your mind?
- What should you reuse next time?
- What source or evidence supports it?
- Where should the agent look first next time?
Everlearn can run SignalSweep as a nested research step without changing SignalSweep's default save directory.
~/.everlearn/bin/everlearn signalsweep \
--topic "customer complaints about cold plunge accessories" \
-- --quickThat command:
- scopes
SIGNALSWEEP_MEMORY_DIRto this one run only - saves raw SignalSweep artifacts to
~/Everlearn Vault/30 Research/SignalSweep - creates an Everlearn
researchnote that links to the saved artifact
SignalSweep's normal default can remain your main Obsidian KB or any other directory you already use.
everlearn/
├── INSTALL.md
├── README.md
├── examples/
├── profiles/
├── scripts/
└── skills/
└── everlearn/
├── SKILL.md
├── examples/
├── references/
└── scripts/
Everlearn is meant for local knowledge capture, not secret storage. Do not capture API keys, cookies, passwords, payment data, customer private data, or confidential material unless you have a clear reason and a safe vault policy.