TabDump (macOS)

Use this skill when the user asks to dump tabs, capture browser tabs, operate TabDump, check reading queue output, troubleshoot Obsidian inbox notes, or inspect launch agent status.

Runtime layout

Expected install paths:

• •App: ~/Applications/TabDump.app
• •App Support: ~/Library/Application Support/TabDump/
• •Config: ~/Library/Application Support/TabDump/config.json
• •Monitor: ~/Library/Application Support/TabDump/monitor_tabs.py
• •Monitor state: ~/Library/Application Support/TabDump/monitor_state.json
• •Legacy app state: ~/Library/Application Support/TabDump/state.json
• •Logs:
  • •~/Library/Application Support/TabDump/logs/monitor.out.log
  • •~/Library/Application Support/TabDump/logs/monitor.err.log
• •Launch agent plist: ~/Library/LaunchAgents/io.orc-visioner.tabdump.monitor.plist

Primary commands

1. •Check status and logs:
   • •scripts/tabdump_status.sh
2. •Count current tabs (monitor path; same TCC surface):
   • •tabdump count
   • •tabdump count --json
3. •Run one-shot dump (default dump-only):
   • •scripts/tabdump_run_once.sh
4. •Run one-shot dump+close:
   • •scripts/tabdump_run_once.sh --close
5. •Reload launch agent:
   • •scripts/tabdump_reload_launchagent.sh
6. •Reset TCC AppleEvents permissions:
   • •scripts/tabdump_permissions_reset.sh
7. •Safe smoke checks:
   • •scripts/test_skill_smoke.sh
8. •Active smoke checks (may open app and trigger prompts):
   • •scripts/test_skill_smoke.sh --active

Config updates

Prefer CLI config commands instead of manual JSON editing:

• •tabdump config show
• •tabdump config get <key>
• •tabdump config set <key> <value> [<key> <value> ...]

One-shot output contract

tabdump_run_once.sh always prints:

• •RAW_DUMP=<absolute-path-or-empty>
• •CLEAN_NOTE=<absolute-path-or-empty>

Exit codes:

• •0 if monitor status is ok
• •3 if monitor status is noop
• •1 for runtime/JSON errors

Tab count output contract

tabdump count:

• •Prints a single integer tab count to stdout.

tabdump count --json:

• •Returns monitor JSON payload with status, reason, mode=count, and tabCount.

Verify successful operation

After a run, verify by:

1. •Checking newest TabDump *.md and TabDump* (clean).md in vaultInbox.
2. •Inspecting monitor state (lastStatus, lastReason, lastProcessed, lastClean).
3. •Tailing monitor logs.

TCC / Automation troubleshooting

If browser automation is blocked:

1. •Run scripts/tabdump_permissions_reset.sh
2. •Or run directly:
   • •tccutil reset AppleEvents io.orc-visioner.tabdump
3. •Re-run a one-shot command and approve prompts in:
   • •System Settings -> Privacy & Security -> Automation

Reference

• •Config fields and semantics: references/config.md