myICOR
Summary
Every time you switch LLMs, you start over — repasting context, re-explaining your projects, re-establishing your voice from scratch. myPKA solves that by making the folder, not the model, the source of truth.
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.
Bottom line: Pick this if you switch LLMs often and need context that survives the switch; plan a different architecture if your workflows require live API calls, multi-user collaboration, or anything that can't live in a markdown file.
Pricing Plans
Subscription- Free Tier
- Folder only; course and coaching require paid membership
Free
myPKA folder with six specialists, open source under CC BY-NC-SA 4.0
- Local markdown files
- AI team with journals
- LLM-agnostic
Membership
Course, coaching, community, and expansion packs
- Full methodology course
- Expansion packs
- Community and coaching
View full pricing on myicor.com →
Pricing may have changed since last verified. Check the official site for current plans.
Community Performance Report Card
No community ratings yet. Be the first to rate this tool!
Community Benchmarks Community
Sign in to submit a benchmarkNo community benchmarks yet. Be the first to share a real-world data point.
Pros
Sign in to edit- 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.
Cons
Sign in to edit- 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.
Community Reviews
Sign in to write a reviewNo reviews yet. Be the first to share your experience.
About
- Platforms
- Local disk (any OS with markdown support)
- API Available
- No
- Self-Hosted
- Yes
- Last Updated
- 2026-06-12T14:24:36.564Z
Best For
Who it's for
- Users seeking a local, vendor-independent PKM system
- Teams that want an always-available AI staff with memory
- People who switch between LLMs frequently
- Anyone building custom workflows on top of markdown files
What it does well
- Research that produces structured notes and shippable deliverables inside the folder
- Drafting documents in the user's established voice and brand context
- Scanning projects for stale or overdue items during weekly reviews
- Maintaining persistent context across multiple LLM sessions and model switches
Integrations
Discussion Community
Sign in to commentNo discussion yet. Sign in to start the conversation.
Compare myICOR
Spotted incorrect or missing data? Join our community of contributors.
Sign Up to ContributeCommunity Notes & Tips Community
Sign in to contributeBe the first to contribute. General notes, observations, gotchas, and tips from people who use this tool day-to-day.
Frequently Asked Questions
- Is myICOR free?
- myICOR is a paid tool. No permanent free tier is offered.
- Is myICOR open source?
- No — myICOR is a closed-source tool. Source code is not publicly available.
- Can I self-host myICOR?
- Yes. myICOR supports self-hosting on your own infrastructure.
- What platforms does myICOR support?
- myICOR is available on: Local disk (any OS with markdown support).
Hours Saved & ROI Stories Community
Sign in to contributeBe the first to contribute. Concrete time/cost savings, with context. e.g. "Cut my code review backlog from 4h to 45m per week."
Curated lists that include this category
Most AI productivity setups collapse the moment you change models — every new session is a blank slate that knows nothing about your projects, your voice, or your team’s history. myPKA is a local folder of plain markdown files that carries that context forward regardless of which LLM you open it with. Inside the folder is a pre-built team scaffold: Larry routes every request to the right specialist, Pax runs structured research, Penn handles capture, Nolan manages the hiring procedure when you want to add new agents, and Mack and Silas cover connections and database architecture. The vendor describes the model as ‘the keyboard’ and the folder as ‘the database’ — you swap keyboards; the database stays put.
The key differentiator is LLM-agnosticism enforced at the file level. Because every agent contract, journal, and project note is a plain text file on your disk, Claude, Gemini, Codex, Cursor, or any future model can read it without migration, without a cloud account, and without vendor lock-in. The vendor licenses the base scaffold under CC BY-NC-SA 4.0, which means the folder structure and agent contracts are open source — your data remains yours even if the company stops operating. MCP integration is available for members, which the vendor describes as removing the need to manually keep configuration files updated.
This fits solo operators and small teams who want an always-available AI staff that accumulates institutional memory across sessions and model switches. It breaks down when your work requires live data fetches, webhooks, multi-user simultaneous editing, or workflows that span systems outside the folder. Teams doing real-time integrations or needing a shared cloud workspace will hit that wall quickly. The folder-plus-agent model also requires you to supply your own LLM access — there is no hosted inference or managed API; you wire up the model yourself.
The paid membership gates the ICOR methodology course, coaching, community access, and expansion packs like the Designer Pack. The base folder scaffold — the agents, contracts, and folder structure — is free and open source. Self-hosting in the literal sense is inherent: the folder runs on your local disk with no server required.