General settings
Workspace-wide settings that apply across all projects. Per-project settings live in Project settings.
AI platform
Dropdown: claude / gemini / codex. Sets the default agent Ideafy spawns when starting work on a card that has no per-card override. Each platform has its own default config path and skills path; switching the dropdown updates those paths to the platform's defaults.
See Choose an AI agent for the per-card override workflow.
Skills path
The directory Ideafy looks in for skills files. Defaults by platform:
- Claude Code:
~/.claude/skills - Gemini CLI:
~/.gemini/skills - Codex CLI:
~/.codex/skills
Project-local skills in <project>/.claude/skills/ take precedence when both exist.
Ideafy uses this path to:
- Populate the
@skillmention autocomplete in card chat - Decide where to write bundled skills when you enable the Ideafy MCP & Skills toggle in a project
If you point this at a non-existent folder, Ideafy creates it on first write.
MCP config path
The file Ideafy edits to register its MCP server with the agent CLI. Defaults:
- Claude Code:
~/.claude.json - Gemini CLI:
~/.gemini/settings.json - Codex CLI:
~/.codex/config.toml
The path is per-user, not per-project. Ideafy modifies only the mcpServers.ideafy entry — your other MCP servers in the same file are preserved.
Terminal app
Which terminal emulator Ideafy spawns when you click Open in Terminal on a card. Options:
- iTerm2 (if installed)
- Ghostty (if installed)
- Terminal.app (macOS default, always available)
Auto-detection picks the first installed option. Override if you want a specific one.
Remote connection
Toggle for the Electron remote device job listener. When on, Ideafy subscribes to ai_jobs via Supabase Realtime and the device can claim jobs dispatched from another device on the same team. Off in Public edition (feature not shipped). Opt-in on the Team edition.
See Remote device for the full workflow.
Theme
Light / Dark toggle. Inherits from system by default. Change it any time — your choice is stored per device.
Hooks
An Install Hooks button at the bottom of the modal re-runs the phase-aware hook install across every registered project at once. Use it after an Ideafy update that ships a new hook body — existing projects pick up the newer entries without opening each project's settings.
The button only touches hooks. It does not reinstall MCP servers or bundled skills — those stay on the per-project Ideafy MCP & Skills toggle in project settings. See Bundled Claude Code hooks for what the installed hooks do.
The button only appears if the active AI platform supports hooks (Claude Code does; Gemini and Codex stubs don't yet).
Claude Code plugin
Visible only when AI platform is claude. Toggle that installs the Ideafy plugin at user scope — the plugin becomes active in every project on this machine, no per-project install needed.
When enabled, a status line underneath the toggle reports what the Ideafy UI knows about the current install:
| Badge | Meaning |
|---|---|
| 🔄 Checking for updates… | Fetching the manifest from GitHub |
| ✓ You are up to date (v0.1.0) | Installed version matches the marketplace's latest |
| ✨ v0.2.0 available — click Update to pull it in | Newer version published; click Update to run the install flow again |
| ⚠ Could not check for updates | Network or GitHub issue (tooltip has the error) |
See Claude Code plugin for the full story — what's bundled, how install/update/uninstall work under the hood, and how user-scope interacts with project-scope.
When the platform is Codex or Gemini, this section is hidden and the equivalent install shows up in project settings instead.
Where General Settings live on disk
The AppSettings values are stored in the settings table of the local SQLite database. Back up ~/Library/Application Support/ideafy/kanban.db and you back up your settings along with everything else.
Next: Project settings Up: User guide index