README file from
GithubGlasscockpit
English | Deutsch

Glasscockpit is an Obsidian plugin that runs Claude Code sessions as terminal tabs inside your vault. A dashboard shows usage limits, context size, vault status and GitHub search results, either as cards or as a cockpit picture. Its "Heute" (today) card puts the points of today's briefing, due reminders from the macOS Reminders app (optional) and your task list into one list; points ticked there are ticked in the rendered briefing too, while the briefing file itself stays unchanged. The photo above uses example data.
Glasscockpit was inspired by the Agentic OS plugin from skaile.de and is an independent rebuild with its own code.
The plugin's settings and labels are in German. There is no English interface yet.
Features
- Sessions as tabs: Claude Code and shells run as terminal tabs in Obsidian, per project folder or in your home folder.
- Dashboard: usage limits, context size, today's tokens, the "Heute" (today) card, tasks, vault status, briefing, radars and GitHub searches, as cards or as a cockpit picture.
- Resume handoffs: open handoff notes show up as "Weiter" (continue) and start the next session in the right repo.
- Alerts: banner, sound and Telegram when a session finishes or asks a question, quiet while agents are still running in the background.
- Launcher: skills, agents and slash commands from the command palette, effort for the next session.
- Terminal comfort and protection: open and edit paths with Cmd+click (Ctrl+click on Windows), click
/clear, minimum contrast, IDE bridge, excluded files closed to Claude.
Requirements
- macOS on Apple Silicon (Intel Macs are untested), or Windows (see "Windows" below).
- Obsidian 1.13 or newer (desktop only).
- The Claude Code CLI (
claude), installed and logged in. jq, for the status line (optional, see "First steps").
Windows
Windows is supported alongside macOS, with these differences.
- Windows 10 version 1903 (build 18309) or newer, or Windows 11; x64 and ARM64. On an older build the plugin reports the missing version.
- Claude Code 2.1.139 or newer. The hooks for the alert signals use the field
args, which older versions do not know. - The binaries: Option B ships them in
native/win32-<arch>/. With Option A, "Binärdateien laden" downloads them (noxattrstep on Windows). - No status line and no limits yet. The switch "Tokens für die Statuszeile schreiben" is locked and says why; the stored value stays, but nothing is written on Windows, not even a value copied over from a Mac.
- No sandbox: Claude Code has none on Windows, so "Auch Shell-Befehle sperren (Sandbox)" is locked. Excluded files are blocked by rules only (setting "Ausgeschlossene Dateien für Claude sperren").
- Ctrl instead of Cmd (for example "Pfade per Ctrl+Klick öffnen"); copy with Ctrl+C only works with a selection, otherwise ^C goes to Claude.
- Smart App Control can block the terminal library, because
conpty.nodeis unsigned. The plugin then reports a blocked library. - Shell tabs start
pwsh.exe(PowerShell 7) if found, otherwise Windows PowerShell. The setting "Shell unter Windows" overrides this. - IDE bridge: if
claudeis the npm shimclaude.cmd, the bridge cannot match the connection to a tab (no@mention from the editor, no question marker for diffs). Withclaude.exeit matches. - The alert sound plays inside Obsidian (WAV or MP3); an empty field or a Mac path (starting with
/or~/) plays the Windows sound; the banner setting is called "Windows-Benachrichtigung".
Installation
Option A: without the ZIP (community plugins or BRAT).
- Install the plugin from the community plugins list in Obsidian or with BRAT (repository
nyko073006/glasscockpit). Both fetchmain.js,manifest.jsonandstyles.cssonly. - Enable Glasscockpit under Settings, Community plugins.
- Open Settings, Glasscockpit, section "Binärdateien", and press "Binärdateien laden". The plugin downloads the terminal library
node-ptyfor your computer once and checks it (see "Network" below). Then start a session.
Option B: the complete ZIP.
- Download the ZIP from the GitHub release: https://github.com/nyko073006/glasscockpit/releases/latest
- Unzip it. You get a folder
glasscockpitwithmain.js,manifest.json,styles.cssandnative/. - Move the folder to
<your vault>/.obsidian/plugins/. - In Obsidian, open Settings, Community plugins, and enable Glasscockpit.
native/ holds the terminal library node-pty as a compiled binary (Option B ships it, Option A downloads it). On macOS, the plugin removes the quarantine flag from that folder on first start (xattr); on Windows there is no such step.
Where the files come from. From version 0.3.6 on, the files of each GitHub release carry a GitHub attestation, a provenance record that they were published from this repository. You can check a downloaded file with gh attestation verify <file> --repo nyko073006/glasscockpit. The release is built locally, not in GitHub Actions: the attestation says where the files were published from, not how they were built.
First steps
Open the command palette and run "Neue Claude-Sitzung" (new Claude session) or "Dashboard öffnen" (open dashboard). Settings are under Settings, Glasscockpit.
The most useful commands in the palette (names are German):
| Command | What it does |
|---|---|
| Neue Sitzung | Menu with project folders and open handoffs. |
| Neue Claude-Sitzung, … im Home | Start Claude in the vault or in your home folder. |
| Neue Shell | Terminal without Claude. |
| Dashboard öffnen, Cockpit-Ansicht öffnen | Dashboard as cards or as the cockpit picture. |
| Skill starten, Agent starten, Slash-Befehl einfügen | Launcher for the most recently active session. |
| Auswahl an Claude erwähnen | Send the selected passage of the note as an @-mention (needs the IDE bridge). |
| Letzten Codeblock kopieren | Copy the last code block of the answer to the clipboard. |
| Sitzung frisch starten | New Claude conversation in the same tab, the old one is kept. |
Most vault-related settings start empty. Empty means "not set up", never an error. The matching card or field then shows "aus" or "nicht eingerichtet" and the plugin reads nothing for it:
| Setting | Empty means |
|---|---|
| Projektordner | "Neue Sitzung" offers no project subfolders. |
| Briefing-Ordner | No briefing card, no automatic git pull. |
| Aufgabenliste | The "Heute" card shows "fehlt" with a button to create the file. The default name is Cockpit Tasks.md. |
| Inbox-Ordner, Index-Datei, Ordner der Daily Notes | The vault panel shows "aus" for that line. |
| Lint-Befehl | No lint button. |
| Radare | No radar lamps. A radar is a name plus the path to a JSON state file you write yourself. |
Telegram, the research searches and the other switches have their own defaults, listed under "Disclosures".
Status line
Claude Code can show a status line. This repo ships one that also feeds the usage card, the token counter and the context gauge. It needs jq.
npm run deploy:statusline
This copies statusline/statusline-command.sh to ~/.claude/statusline-command.sh. It replaces a file that already exists there. Then point Claude Code at it in ~/.claude/settings.json:
{ "statusLine": { "type": "command", "command": "~/.claude/statusline-command.sh", "refreshInterval": 30 } }
Without the status line the plugin works, but the usage card and the context and token gauges stay empty.
Handoff signal (optional)
A Stop hook shows a coloured banner "Session clearable" after an answer in which Claude reports the session as ready to hand off: a code block whose first line starts with Handoff:, or the word "clearable" without "not"/"nicht" before it. The banner only appears once the session has enough context and enough of your own messages. Both thresholds are settings ("Handoff frühestens ab Kontext (%)", default 10, and "Handoff frühestens ab Nachrichten", default 2). Slash commands do not count as messages. The hook reads the context from the status line; without it only the message threshold applies. It needs python3. The banner text is German.
npm run deploy:hook
This copies hooks/clearable-banner.py to ~/.claude/hooks/clearable-banner.py. Then register it in ~/.claude/settings.json:
{ "hooks": { "Stop": [ { "hooks": [ { "type": "command", "command": "python3 \"$HOME/.claude/hooks/clearable-banner.py\" 2>/dev/null || true", "timeout": 10 } ] } ] } }
For Claude to set the signal, add an instruction to your CLAUDE.md, for example: "When the session is ready to hand off, end the answer with a code block that starts with Handoff:."
npm run deploy:hook also copies hooks/clear-sicherung.py next to the banner hook. It is a second, optional hook for the end of a session (for example after /clear): it looks for the last handoff block in the ending session and writes that session's ID and transcript path into the frontmatter of the handoff file named there (vorgaenger_session, vorgaenger_transkript), so the next session can find its predecessor. It never blocks and prints nothing. Register it only if you want it:
{ "hooks": { "SessionEnd": [ { "hooks": [ { "type": "command", "command": "python3 \"$HOME/.claude/hooks/clear-sicherung.py\" 2>/dev/null || true" } ] } ] } }
Handoffs
The plugin can continue a project from the handoff note of an earlier session. It is off until you set two paths.
| Setting | Meaning |
|---|---|
hubsDir |
Vault folder with one subfolder per project. Empty = off. |
handoffsDir |
Folder name inside each project folder that holds its handoff notes. Empty = off. |
hubSuffix |
Ending of the project's hub note. Default " - PMO HUB.md". |
handoffPrompt |
First message of a continued session. {datei} becomes the handoff path, {auftrag} the next task. |
A handoff is a Markdown note with this frontmatter:
status: offen # offen = waiting, aufgenommen = taken up
erstellt: 2026-01-05
naechster_auftrag: Short description of the next task
The hub note may name the project's repo folder with repo: ~/path/to/repo. ~ is your home folder. Without repo, or if the folder does not exist, the session starts in the vault and the entry says so.
Per project the newest open handoff counts. The field "Neue Sitzung" on the dashboard shows "N offen". The new-session menu lists each one as "Weiter" above the normal entries, and Enter without typing picks the top entry. The plugin sets status: aufgenommen (and aufgenommen: <date>) only once the session is running, so a failed start leaves the handoff open.
Minimum contrast in the terminal
Claude Code sends some text (for example the question of a choice prompt) as fixed white. In a light Obsidian theme that text is invisible. The setting "Mindestkontrast im Terminal" (1 to 21, default 4.5, 1 = off) lifts text that is too pale for the background up to that contrast ratio. It applies at once to open terminals.
Open paths with Cmd+click
File paths in the terminal open with Cmd+click: absolute, with ~ or relative to the session's start folder, each optionally with :line or :line:column. While Cmd is held, a path is underlined, but only if it exists as a file. Only Cmd with the left button opens it; Cmd with the middle or right button, or with Ctrl or Alt, does nothing. Files in the vault open as a tab, all others in a window with a small code editor: Cmd+S saves, Esc closes. TypeScript, JavaScript, JSON, Swift, CSS, Python, YAML, SQL, HTML and shell are shown in the theme's code colors; while you type, the window suggests words from the file and keywords of the language (Enter accepts, Esc first closes the list, Ctrl+Space opens it; turn it off with "Datei-Viewer: Vorschläge beim Tippen"). If the file changed since it was opened (for example by Claude), the window asks before overwriting. Text files larger than "Datei-Viewer: Höchstgröße (MB)" (default 2) are not shown. Images (png, jpg, jpeg, gif, webp, svg, bmp, ico) appear fitted into the window; zoom works as with text (Cmd+Plus, Cmd+Minus, Cmd+mouse wheel), 100 % shows real pixels with scrolling, Cmd+0 fits the image again, and the title shows size in pixels and file size (for SVG only the file size). Images have their own size limit ("Datei-Viewer: Höchstgröße Bilder (MB)", default 20) and a switch ("Datei-Viewer: Bilder anzeigen"). Other binary files are not shown, but a button opens them (and images) in the default program. Markdown files (.md) are colored by body text, code, commands, headings, links, markers and frontmatter; the text stays raw text, and the colors and the command list are configurable ("Datei-Viewer: Markdown färben", "Datei-Viewer: Farbe …", "Datei-Viewer: Befehle in Backticks"). Turn it off with "Pfade per Cmd+Klick öffnen". In shell sessions the start folder still applies after cd. The window starts at 90 % of the Obsidian window's width and height (settings "Datei-Viewer: Startbreite (%)" and "Datei-Viewer: Starthöhe (%)", 40 to 100) with the font size from "Datei-Viewer: Schriftgröße (px)" (default 14), and long lines wrap. Cmd+Plus, Cmd+Minus and Cmd+0 (or Cmd+mouse wheel) zoom the text, 50 to 200 %; the shortcuts are intercepted, so Obsidian's own zoom stays untouched. Drag the title bar to move the window, drag an edge or corner to resize it, double-click the title bar to go back to the start size. Nothing is remembered: the next window opens at the start size and 100 % again.
If a relative path is not in the start folder, the cockpit looks for it in the folders Claude has worked in during this session: cd targets and the folders of files it read or edited. So when Claude names src/main.ts:10 from a repo in a vault session, it becomes a link. If several of these folders have the file, for example the repo and a worktree, it opens from the folder Claude worked in most recently; the window title shows the full path. Turn it off with "Relative Pfade auch in Claudes Ordnern suchen".
Paths with spaces in the name work too, such as 02 Projekte/Report May.pdf. In quotes (open "02 Projekte/Report May.pdf") the whole text between the quotes counts. Without quotes the cockpit extends a word over single spaces (at most 16 words) as long as the folder part exists, and takes the longest path that exists as a file; text after it does not belong to the link. Claude Code wraps long lines at spaces, so such a path may run over up to three lines and stays one link (over four or five lines only the middle ones carry it, beyond that none do). Unquoted relative paths with spaces are only looked up in the session's start folder, not in Claude's folders. Turn it off with "Pfade mit Leerzeichen erkennen"; then a path ends at its first space.
Click /clear
A standalone /clear in the terminal of a Claude session (for example in the closing sentence of an answer or in the hook banner) is a link: it is underlined when you hover it, and a click types /clear into Claude's input line. It does not press Enter, you do that yourself. Selecting text by dragging over it inserts nothing, except in the mode "Eingabezeile fest (Vollbild)": there xterm has no selection, so even a drag inside /clear inserts it, while Shift+drag forces the selection and inserts nothing. Shell sessions have no such link. Turn it off with "/clear per Klick einfügen".
Banner auto-dismiss
The banner (setting "macOS-Banner", on Windows "Windows-Benachrichtigung") closes itself after "Banner ausblenden nach (Sekunden)" (1 to 60, default 6); on macOS it does not stay in Notification Center. Each session has at most one banner: a new one replaces the old one. Open banners are closed when the plugin is disabled. A click brings the session to the front. If @electron/remote is unavailable in Obsidian, the plugin falls back to the window's web notification; then closing is not guaranteed.
Quiet intermediate results
A chat that starts agents, workflows or background commands ends its answer, and every finished agent wakes it up again to write an intermediate result. Without a filter each of those answers would notify you. With "Zwischenstände bei laufenden Agents nicht melden" (on by default) an answer that ends while something still runs in the background stays silent: no Telegram, no sound, no banner, no mark on the tab. Only the answer after which nothing runs any more is reported. Questions are always reported. The tab shows how many background tasks are running as "⏳ 2" before its title ("Laufende Hintergrundaufgaben im Tab zeigen (⏳)").
The plugin reads this from the Claude transcript: a task counts as running from its start (an agent or workflow started in the background, a Bash command with run_in_background, an MCP tool moved to the background, an agent continued with SendMessage) until its completion notice appears. A start without a completion notice stops counting after "Höchstalter einer Hintergrundaufgabe (Minuten)" (1 to 1440, default 60), so a lost notice cannot silence a session for good. The Monitor tool is not recognised; an answer behind it is reported as before.
Skip permission prompts
The switch "Rechteabfragen überspringen" is off by default.
Warning: when it is on, new sessions start with --dangerously-skip-permissions. Claude then runs commands and edits files without asking you. Turn it on only in folders and vaults where you accept that.
The switch applies to sessions started after you change it. Running sessions keep their mode.
Excluded files stay closed to Claude
Files and folders listed in Obsidian under Settings → Files and links → Excluded files are blocked for every Claude session that Glasscockpit starts, whatever folder the session runs in. Claude can neither read nor edit them, including with cat. The plugin hands the rules to each session with --settings; your own Claude settings files stay untouched. A grey line at the start of a session says how many entries are blocked.
- "Ausgeschlossene Dateien für Claude sperren" (on by default) turns this off.
- Without the sandbox, shell commands that search a whole folder (
grep -r, scripts) still read excluded files. "Auch Shell-Befehle sperren (Sandbox)" (off by default) runs sessions in Claude's sandbox, which blocks those too, except commands listed insandbox.excludedCommandsin your own Claude settings, which keep running outside the sandbox. In the sandbox Claude writes only inside the working folder and the temp folder, and network access needs approval. - Shell tabs and Claude sessions started outside Glasscockpit are not covered. Changes to the list apply to sessions started afterwards.
- An entry that would need more than 500 single rules is not blocked; the grey line names it.
- With the IDE bridge on, Claude does not get the path or the selection of an excluded note.
Disclosures
This follows the disclosure rules of the Obsidian developer policies.
Runs programs.
claudein a terminal session, and your$SHELLfor shell sessions. On macOS the plugin starts your login shell once on load ($SHELL -i -l -c) to readPATHandLANG.git pull --ff-onlyin the briefing folder, only if you set one (every 5 minutes by default, while a dashboard is open).git statusin your project folders, for the repo panel. No fetch.- On macOS:
afplayfor the alert sound,xattrfor the quarantine flag,psto find the parent process for the IDE bridge,ioregfor the idle time (Telegram). - On macOS, only if "Erinnerungen in „Heute“ (nur macOS)" is on (off by default):
/usr/bin/osascriptwith AppleScript for the Reminders app. It reads the ID, name, list and due date of all open reminders in all lists; the "Heute" card shows only the due ones from the lists you chose. When you tick a reminder in the card, it marks it as completed, or open again. None of this is sent over the network. The name and ID of each reminder ticked in the cockpit are stored in the plugin'sdata.jsoninside your vault and stay there until you tick a reminder again on a later day, even if you turn the setting off; if you sync your vault, they are synced with it. Not on Windows. - On Windows:
powershell.exefor the hooks;pwsh.exeor Windows PowerShell for shell tabs and as your shell;cmd.exeto startclaude.cmd;taskkillwhen a session is ended by force;tar.exeto unpack the binaries. Noafplay,xattr,psorioreg. The system programs (powershell.exe,cmd.exe,taskkill,tar.exe) are started from the WindowsSystem32folder, not found throughPATH.pwsh.exeis the exception: it is looked up in thePATHfolders, and Windows PowerShell fromSystem32is the fallback.
Reads outside the vault.
~/.claude/projects/: the Claude transcripts, to count tokens, find the last code block, show the active session, know the folders Claude worked in (for relative paths) and know which background tasks still run (quiet intermediate results). In "Neue Sitzung" the modification times of the transcript files (not their contents) set the order of the project folders; the setting "Reihenfolge in „Neue Sitzung“" set to "Alphabetisch" turns this off.~/.claude/skills/,agents/,commands/,settings.jsonandplugins/installed_plugins.json: to list skills, agents and commands in the launcher. The same folders under the vault and the project folder are read too.~/.claude/cockpit/:usage.jsonandsessions/*.json(written by the status line script), plus the plugin's own files below.- Telegram only if enabled: the
.envfile named in settings (default~/.claude/channels/telegram/.env) for the bot token, andaccess.jsonnext to it for the chat ID. The token is read for each message and never stored by the plugin. - Radar state files at the paths you enter.
- Paths shown in the terminal: on hover only a
staton the paths of that line, the content only after Cmd+click (switch "Pfade per Cmd+Klick öffnen").
Writes outside the vault.
~/.claude/cockpit/tokens-today.json(today's output tokens for the status line, not written on Windows; switch "Tokens für die Statuszeile schreiben", on by default),thresholds.json(context thresholds from your settings) andresearch.json(cache of GitHub results).- The file you save with Cmd+S in the file viewer, and only that one (switch "Pfade per Cmd+Klick öffnen", on by default). It is written to a temporary file in the same folder, which is then renamed.
~/.claude/ide/<port>.lock: lock file of the IDE bridge (switch "IDE-Brücke", on by default). It lets Claude sessions started by the plugin see your selection and open notes. The server listens on127.0.0.1only. The lock file is removed on exit.npm run deploy:statuslinewrites~/.claude/statusline-command.sh. You run that yourself.npm run deploy:hookwrites~/.claude/hooks/clearable-banner.pyand~/.claude/hooks/clear-sicherung.py; you run that yourself too. The banner hook reads~/.claude/cockpit/thresholds.json,sessions/*.jsonand the session transcript, and appends a log to~/.claude/hooks/clearable-banner.log.clear-sicherung.py, only if you register it as a SessionEnd hook: reads~/.claude/cockpit/thresholds.json(handoff prefix) and the transcript of the ending session, writes the two fieldsvorgaenger_sessionandvorgaenger_transkriptinto the handoff file named in its last handoff block (via a temporary file that is then renamed; everything else in the file stays byte for byte), and appends one line per session end to~/.claude/cockpit/clear-log.jsonl(time, reason, session ID, transcript path, working folder, handoff path, whether it was stamped, and an error text if one occurred).
Writes inside the vault. The plugin's data.json (settings, session list, the briefing points ticked in the "Heute" card or in the briefing, and the ticked reminders; each of the two lists stays until you tick an item of the same kind again on a later day), the folder native/darwin-<arch>/ (on Windows native/win32-<arch>/) inside the plugin folder when you press "Binärdateien laden" (plus a temporary folder .native-download-* there while it runs, removed afterwards), the task file when you press "Anlegen", tick a task or add one in the "Heute" card, and the result of git pull in the briefing folder. On Windows also .sessions/<id>.settings.json in the plugin folder, one settings file per Claude session. The plugin removes these files when the session is stopped and when it loads and unloads. After a crash they stay until the next start.
Network.
- GitHub search (
api.github.com/search/repositories) for the Research card, without a token. It sends your search lines from the settings and nothing else. Without a token GitHub allows 10 searches per minute. - Telegram (
api.telegram.org), only if you enable "Telegram, wenn eine Sitzung fertig ist" or "…eine Frage hat" (both off by default). It sends a short status text. - Binary download, only when you press "Binärdateien laden" in the settings, never automatically: one ZIP (about 40 KB) with the compiled
node-ptyfor your computer fromgithub.com/nyko073006/glasscockpit/releases/download/<plugin version>/glasscockpit-native-<darwin|win32>-<arch>.zip. The plugin sends no data beyond the request itself. The address is fixed in the code. Before anything is installed, every file of the download is compared against a SHA256 list that is built into the plugin (no extra files, no symbolic links, every checksum must match); on any mismatch nothing is changed. The downloaded files are native code that Obsidian then loads, so the checksums are the safeguard: they come from the plugin itself, not from the download. - Claude Code itself talks to Anthropic. That is the
claudeprogram, not this plugin.
No telemetry. The plugin sends no usage data, no analytics and no crash reports.
No affiliation. Glasscockpit is not connected to Anthropic or Obsidian and not endorsed by either. "Claude" and "Obsidian" are trademarks of their respective owners.
Limits
- macOS and Windows only.
native/holds binaries for Apple Silicon (arm64) and Intel (x64) on macOS and for x64 and ARM64 on Windows; the loader picks by system and architecture. On macOS the arm64 build is the tested one, x64 is untested inside Obsidian. Windows has no status line, no limits and no sandbox yet (see "Windows"). - The interface is German.
- Parts of the IDE bridge use an unofficial protocol of Claude Code and may break with an update. Errors only go to the developer console.
- Some behavior can only be checked inside Obsidian. Tests cover the logic, not the whole plugin.
License
MIT, see LICENSE. Third-party licenses are in THIRD-PARTY-NOTICES.md.
The background image assets/cockpit-bg.jpg was generated with Google Flow (Nano Banana Pro).