ICOR for Life - AI Chat

Your AI team, in the room with your notes.

Ask a question next to the note you are working on, and get an answer from a model that already knows which note is open and which lines you selected.

Part of the ICOR for Life suite.

What it is for

Copying a note into a chat window strips the context that made it worth asking about. You paste the paragraph and lose the project it belongs to, the person it is about and the six other notes that would have changed the answer.

This is a window onto a model that is already in your vault. It reads your vault's own instructions, so your team behaves the way you wrote it, not the way a plugin decided.

The plugin is a window, not a second brain. Behaviour, identity and context rules live in your vault's own files. It sends no instructions of its own, with one visible exception in settings, which makes answers come back as ICOR cards instead of terminal text.

Before you start

You need the Claude Code command line tool, installed and signed in on this machine. This is the one thing that trips people up:

• The Claude desktop app is not the same thing.
• claude.ai in a browser is not the same thing.

The plugin has no API key field on this engine. It finds the claude program already on your machine and talks to that. If it is not installed, nothing happens, and that is far and away the most common reason a fresh install appears to do nothing.

Desktop Obsidian 1.8.7 or newer. Mobile cannot run a local program, so this engine is desktop only. Your own API key runs on a phone or tablet too; see "Where your keys live".

Optionally, the Codex command line tool as a second engine.

Getting started

1. Install the Claude Code command line tool and sign in.
2. Enable the plugin and open the chat pane.
3. Ask something about the note you have open.

Continue on your phone

Hand a conversation to your phone and pick it up there. From that point permissions follow your own command line tool's settings rather than this plugin's.

Safety

• Permission mode starts at Ask. Every tool call that wants a decision gets one, from you.
• Bypass is never a saved default. It is a choice you make for one conversation, never a setting that quietly stays on.
• Sessions are scoped to this vault. The plugin does not go looking at your other projects.

Where your keys live

One setting decides whether keys stay on this device or follow the vault. Most people need nothing here: on the default engine there is no key at all, because your command line tool is already signed in.

If you pick My own API key under Settings, AI engine on this device, two things change:

• You need an account at Anthropic (console.anthropic.com) or OpenRouter (openrouter.ai), and a key from there. Use is billed to that account.
• The plugin talks to the internet itself. Your messages, the notes you attach and tool results go over HTTPS to api.anthropic.com or openrouter.ai, and nowhere else. Nothing goes to myICOR.

The key lives where you choose:

• Obsidian's keychain (the default; Obsidian 1.11.4 or newer; see Settings, General, Keychain). Keys in Obsidian's keychain stay on this device. Obsidian Sync does not carry them; enter the key once per device. Any plugin in the vault can read any keychain entry, which is why this plugin's entries carry its name: icor-for-life-chat-anthropic-api-key and icor-for-life-chat-openrouter-api-key.
• An env file in the vault, by default 06 AI Team/AI Team Knowledge/.env, as ANTHROPIC_API_KEY= and OPENROUTER_API_KEY=. Keep that file out of anything that syncs or publishes your vault.

The plugin reads only the place you chose. The settings tab shows where each key is and can move it. No key is ever shown back.

Settings

Plumbing only, by design: where the program is, which model, how hard it thinks, the default permission mode, where conversations are archived and for how long.

There is no prompt box, because your vault already has one.

What it touches

• Runs the command line tool you already installed, in your vault folder.
• Reads and writes notes in your vault, with your permission, the same as you would.
• Archives your conversations as notes in a folder you choose.
• Reads your life snapshot, if one is there. When the pane opens and again before the first message of a conversation, the plugin reads .icor-for-life/scripts/snapshot.json in your vault: the file the ICOR for Life life-snapshot.py script writes, holding the names of your open goals, your focus projects, your week and your key elements. It is only ever read, never written, and if it is not there the pane says so and nothing is invented. The file is per device, because Obsidian Sync skips folders whose name starts with a dot, so running the script on your laptop does not put it on your phone. On the own API key engine, the short brief built from it travels to the model provider with the first message, the same way the note context you pin already does.

The plugin itself makes no network calls on the default engine. Your command line tool talks to Anthropic under your own account.

Good to know

• Desktop, plus phones and tablets on your own API key.
• Beta. If something looks off, open an issue.

Support

What myICOR supports: the plugin as published in a tagged release, on the current version, installed from that release. Bugs go to this repo's issues, security reports to the process in SECURITY.md.

What the community maintains: anything marked community-maintained, including community source adapters. We review it before it is merged. We do not support it, we cannot promise it keeps working, and it can be disabled or removed in any release.

What is yours: your own changes, your fork, your local patch. Please reproduce the problem on a clean install of the current release before reporting it.

Licence

MIT, see LICENSE. Install it, run it, read it, change it, sell it, ship it in your own product; keep the copyright and licence notice. Releases before 0.16.0 stay under the ICOR for Life Source-Available License (Code) v1.0 they were published with.

The licence covers the code only. "ICOR", "ICOR for Life", "myICOR" and "Paperless Movement" are trademarks of Paperless Movement, S.L.; a fork needs its own plugin id and name. See TRADEMARK.md.

Contributions are welcome as pull requests under the same MIT terms, with a DCO sign-off on every commit. See CONTRIBUTING.md.

Bundled third-party components keep their own licences; see THIRD-PARTY-NOTICES.md. The built main.js also contains @anthropic-ai/claude-agent-sdk, Copyright (c) Anthropic PBC, which is not under MIT; forks that redistribute main.js redistribute it on Anthropic's terms.