myICOR vs notebrain-cli

myICOR and notebrain-cli are both productivity tracked by AIDiveForge. Below is a side-by-side comparison of pricing, capabilities, platforms, and ownership — sourced from each tool's live website and verified before publishing.

myICOR

The system is a local markdown folder pre-loaded with a six-person AI team: a routing orchestrator (Larry), a research specialist (Pax), a capture agent (Penn), and others — each with a named contract and a session journal so the next model picks up where the last one left off. You bring your own LLM; the folder supplies the memory. Research produces structured notes in place, drafts inherit your established voice, and weekly review prompts surface stale items automatically. The ceiling appears when you need real-time data, API integrations, or collaborative editing — none of that is in the folder. Teams that need those reach for purpose-built tools alongside this one.

notebrain-cli

NoteBrain indexes your Markdown notes into a local ChromaDB vector database and gives you semantic search, wikilink graph traversal, and hidden-connection discovery through structured CLI output. Every bit of it runs on your machine — no API calls, no cloud dependency, no data leaving the host. The structured output is designed to be consumed directly by shell pipelines or LLM tool-use workflows, which means a coding agent can query your vault the same way it queries a function. The ceiling appears when your query logic needs to span multiple hops or filter by metadata at scale — ChromaDB local mode is not a production vector database, and the index will need a rebuild whenever the vault structure shifts significantly.

Attribute	myICOR	notebrain-cli
Pricing	Paid	Free
Free trial	No	No
Open source	No	Yes
Has API	No	No
Self-hosted option	Yes	Yes
Platforms	Local disk (any OS with markdown support)	Linux (binaries); source compiles on other platforms
Pros	LLM-agnostic folder architecture, so switching from Claude to Gemini mid-project is a matter of opening the same folder in a different app — no re-pasting context, no lost session history. Persistent agent journals mean each specialist picks up from the last session, so you stop spending the first ten minutes of every AI conversation re-explaining who you are and what you're working on. Plain markdown on your local disk means zero migration risk — if the vendor disappears tomorrow, every note, contract, and workflow you built is still readable by any text editor or LLM. Larry's routing layer matches requests to the right specialist automatically, so you don't have to remember which prompt style triggers good research versus good drafting — the team handles the handoff. Open-source scaffold under CC BY-NC-SA 4.0, so you can inspect, fork, and extend the agent contracts without waiting on a vendor roadmap or paying for access to the base system.	Fully local ChromaDB indexing with zero network calls, so your vault contents never touch an external server — which matters when notes contain unpublished code, client context, or anything you cannot route through a third-party API. Structured CLI output designed for agent tool-use, so a coding agent can query your vault the same way it calls a function — rather than scraping unformatted text and hoping the LLM parses it correctly. Wikilink graph traversal alongside semantic search, so you get two retrieval signals instead of one — structurally connected notes surface even when the embedding similarity score would have missed them. MIT license with self-hosted operation, so there is no vendor lock-in, no pricing gate on features, and no dependency on a service that can change its terms or go offline. Ships with an agent skill definition and OpenCode integration documented in the repository, so wiring it into an existing agent setup does not require building the tool-call interface from scratch.
Cons	The folder has no mechanism for live data: API calls, web scraping, calendar reads, and CRM syncs are all outside its scope. Teams that need agents to pull live information must wire up a separate integration layer and maintain it alongside the folder — which is a second system to debug. There is no multi-user collaboration model. Two people cannot edit the same folder simultaneously with conflict resolution. Teams of more than one person sharing a PKM workspace hit this wall immediately and typically move the shared layer to a tool with real-time sync — Notion, Obsidian Sync, or a shared Git repo — while keeping individual folders local. No hosted inference or built-in LLM access means every new user must already have API credentials or a local model running before the team scaffold does anything. For non-technical users who came for the AI workflows, the setup friction before first use is real and the docs leave meaningful configuration detail to the user to figure out. The agent team is fixed at the scaffold level — expanding it requires running Nolan's eight-step hiring procedure, which is a prompt-driven workflow inside the folder. Teams used to GUI-based agent builders who want to add a specialist in two clicks will find the process slower and more text-heavy than competing tools that offer visual agent creation.	There is no persistent HTTP API — the CLI is the only interface, which means any workflow that needs a long-running queryable endpoint (a web app, a multi-agent system polling for context, a teammate's machine) cannot use NoteBrain without wrapping it in a custom server layer that the project does not provide. The local ChromaDB backend is not designed for large-scale or high-frequency writes: when vault structure changes significantly, the index requires a rebuild, and teams with vaults that evolve rapidly report that the rebuild cycle interrupts agent workflows that depend on fresh results. A team whose vault scales to tens of thousands of frequently-updated notes, or whose agents need concurrent read access from multiple processes, will hit local ChromaDB's performance and concurrency limits — at that point, the path forward is a dedicated vector database (Qdrant, Weaviate, or a hosted alternative) with a custom ingestion pipeline, which means migrating off NoteBrain entirely.

Bottom line

MyICOR is paid while notebrain-cli is free; notebrain-cli is open source. Choose based on which difference matters most for your workflow.

Frequently asked questions

What is the difference between myICOR and notebrain-cli?

myICOR is Paid, while notebrain-cli is Free and open source. Compare pricing, free trial, API, platforms, and pros/cons in the table above on AIDiveForge.

Is myICOR better than notebrain-cli?

It depends on your workflow. Use the side-by-side attributes (pricing, open source, API, self-hosted, platforms) to decide. AIDiveForge does not rank a universal winner — we publish verified facts so you can choose.