Icor For Life Terminal — Development skill for Claude Code

ICOR for Life - Terminal

A real terminal inside your vault. Your login shell in a tab or a split, keyboard capture that still lets the command palette through, and a one-command launcher for Claude Code in the vault folder.

The terminal is a pane like any other: it lives in Obsidian's own tabs and splits, it is renamed from its tab, it comes back after a reload in the same folder, and it is skinned by the ICOR for Life - INKLINE theme while staying legible on any other theme.

**Beta release, desktop only.** It runs in a real vault every day and it has rough edges. If something looks off, open an issue.

What this plugin does on your machine, stated plainly

Read this before installing. A terminal is the largest capability a plugin can have, and the point of this section is that nothing below surprises you later.

• It runs local processes. Every terminal pane starts a process: your login shell by default ($SHELL -l), a command you configured as a profile, or claude. The process runs as you, with your permissions. The plugin spawns it through a small Python helper (shipped inside main.js as readable source, src/pty/helper.py in this repository) that gives the process a real pseudo-terminal, because Node has no pseudo-terminal without a native module and a native module cannot ship through the Obsidian directory.
• It accesses files outside the vault. A shell reads and writes whatever you can. The plugin itself also looks for the claude executable on your PATH and uses your vault's folder on disk as the working directory.
• It makes no network connection of its own. No telemetry, no update check, no fetch. What you run inside the shell is yours.
• It uses the clipboard only on your key. Cmd+C copies the selection and Cmd+V pastes, through the browser's own copy and paste events on the terminal's input; the plugin never reads the clipboard itself. Its one write of its own is opt-in: with "Copy on select" e