Project settings
Per-project configuration. Opened from the sidebar by clicking the gear icon next to the project name, or by right-clicking the project.
Core fields
| Field | Editable after creation | Notes |
|---|---|---|
| Name | ✓ | Human label. Changing it doesn't rename the folder |
| Folder path | ✗ | Fixed at creation; to change, create a new project and import |
| ID prefix | ✓ | Short identifier (e.g., KAN). Changing it affects new cards; existing cards keep their old prefix on their display ID |
| Color | ✓ | The coloured strip on every card |
| Next task number | ✓ | Counter for auto-incrementing task IDs. Usually auto-managed; edit if you need to jump (e.g., skip 13 for superstitious reasons) |
Voice
Voice is the project-level tone for every AI surface — plan, tests, AI opinion, chat, autonomous flows, and solution summaries. One setting drives the prose style across all of them, so a single mental model controls how the assistant sounds.
Voice changes only tone. Technical content (file paths, change lists, trade-offs) is preserved across all three personas — the entrepreneur voice doesn't strip the content, it just describes it in plainer language.
Choose one of three personas (radio group, default Builder):
| Voice | Audience | Prose style | Example phrasing |
|---|---|---|---|
| Entrepreneur | Product person who doesn't read code daily | Plain prose; lead with user impact and "why"; no monospace jargon, no file:line references; describe technical decisions in one human sentence | "the login flow, the session check, and the logout cleanup" instead of file paths |
| Builder (default) | Solo founder who codes — fluent in technical terms but allergic to spec verbosity | Plain technical sentences; names files when relevant, skips line numbers and snippets unless the change is non-obvious; one paragraph per change beats five terse bullets | "I added an expiry check to the auth callback because the old token was reused after sign-out" |
| Engineer | SWE reviewing the change in passing | Spec-style; bullets, file:line references, code snippets when they clarify; surfaces trade-offs explicitly; Changed Files table when more than two files move | "chose A over B because of N+1 risk" |
How each section reacts
The persona above sets the base tone. Each AI surface then layers a section-specific accent on top so the prose adapts to what the surface is actually for.
| Section | Entrepreneur accent | Builder accent | Engineer accent |
|---|---|---|---|
| Plan (Solution tab) | What we're building, why, who feels it, what's the risk. Files described in one human sentence each | Ordered prose paragraphs per step. "Files" line at the end with paths | Numbered steps with file:line scope, function/symbol names, 1-line trade-offs. Ends with a Changed Files table |
| Tests | Plain-language step descriptions. References UI labels users actually see | UI labels mixed with the occasional technical hint | Manual scenario steps may include the related code path or function name in parentheses |
| Opinion | Verdict focuses on user impact, scope creep, MVP fit | Balanced product + technical lenses; one-sentence callouts on risks | Leads with technical risk: race conditions, n+1, schema drift, perf cliffs |
| Chat | Plain conversational, no jargon | Technical-fluent conversation; mentions files naturally | Terse and structured: bullets, file refs, code blocks |
| Autonomous | Plain-language summary at the end of the run | Short prose summary plus a Files line | Changed Files table, root-cause one-liner, trade-off note |
| Solution summary | Narrates the fix as a story; files mentioned by name, not path | Prose paragraphs grouped by feature area; Files table if more than 3 files moved | Root cause → architecture context → step-by-step changes with snippets → Changed Files table |
The Tests tab keeps the underlying manual-tester format (imperative steps, checkbox-driven) regardless of voice. Voice only colors the prose around each step — it doesn't break the format.
When to switch voice
- Solo founder, no team — Builder is the default and usually the right fit.
- Sharing the board with non-developers (designers, founders, business analysts) — Entrepreneur keeps plans and opinions readable without translation.
- Engineering-heavy team or working with reviewers — Engineer matches the SWE workflow and reduces back-and-forth on PRs.
Voice is per-project, so different projects can use different personas. Changing the voice doesn't rewrite existing content — only new AI output picks up the new tone.
Document paths
Ideafy always runs smart discovery on the project folder — it walks docs/, documentation/, wiki/, notes/, specs/, design/, architecture/, adr/, plans/, and .github/ for .md files, plus key root files like CLAUDE.md, README.md, CONTRIBUTING.md, CHANGELOG.md, ARCHITECTURE.md, SECURITY.md, and LICENSE.md. Anything it finds appears in the sidebar Documents tree and in the @ mention popup without you configuring anything.
Document Paths (the multi-line text field in project settings) lets you add files or folders that smart discovery would otherwise miss — or surface a non-standard location at the top of the list. One path per line, relative to the project folder. Both files and directories are accepted:
docs/
specs/
ARCHITECTURE.md
ops/runbooks/
Your paths are not an override. They render at the top of the Documents tree in user-defined order; smart discovery fills in whatever's left below a divider. A file matched by both sources is de-duplicated in favour of the user-supplied entry. If you don't set any custom paths, smart discovery is still active on its own.
When a document is available — from either source — you can mention it with @document in card chat, and Ideafy loads it into the agent's context.
Memory (Claude auto-memory)
When the active agent is Claude Code, Ideafy surfaces Claude's per-project memory folder as a separate Memory section in the sidebar, just below Documents. The folder lives at ~/.claude/projects/<dash-encoded-folder>/memory/ — Claude Code writes notes there as you work (preferences, project facts, decisions to remember across sessions).
MEMORY.mdis pinned to the top; everything else is sorted alphabetically- Memory files are mentionable with
@in card chat; they insert as absolute paths so the Claude CLI resolves them correctly even when the working directory is elsewhere - The section only appears when the workspace AI platform is
claudeand the memory folder actually exists on disk - Switching the AI platform to Gemini or Codex hides the Memory section (those agents don't have an equivalent auto-memory layout)
Memory files are not managed by Ideafy — they belong to Claude Code. Ideafy only reads and mentions them.
Narrative
Narrative file path — defaults to docs/product-narrative.md. Points at the project's Product Narrative file, the living document the agent reads as context for every evaluate run.
Narrative mode — how the narrative was set up:
- Create — Ideafy generated it through the interview
- Existing — points at a file you wrote
- Skip — no narrative;
evaluateruns without project context - Skill — configured to be generated interactively via the
product-narrativeskill
You can change the mode later. Switching to Create re-runs the interview and overwrites the file. Switching to Existing lets you repoint at a different file.
Git worktrees
Use worktrees — toggle. Default on. When on, Ideafy creates a .worktrees/kanban/[PRJ-N-...] worktree for each card that goes into implementation. When off, all work happens on the project's main branch.
Turn off only if:
- Your project setup breaks with worktrees (very rare)
- You prefer the simpler single-branch flow and accept losing per-card isolation
Team assignment (Team edition)
Team — dropdown of teams you're a member of, plus a None option. Linking the project to a team enables pool sync — every card mutation fires a sync-card call to Supabase. See Team overview.
Unlinking (setting the dropdown back to None) keeps all local data, but stops pool sync for new mutations. Existing pool cards remain in the pool but won't update from your edits anymore.
MCP & Skills installation
The project dialog picks one of two toggles based on the active AI platform. You never see both at once.
Claude Code → Claude Code plugin
For Claude Code users, the project dialog exposes a Claude Code plugin toggle (project scope). When on, it installs / enables the Claude Code plugin only for this project.
Three sub-states:
| Project state | What you see |
|---|---|
| User-scope plugin already on | Row shows an Inherited badge instead of a toggle. Nothing per-project needed — the user-scope install already applies |
| User-scope off, project-scope off | Toggle visible, off. Flipping on runs the project-scope install flow |
| User-scope off, project-scope on | Toggle visible, on. The plugin's MCP + hooks + skills are active only when this project is the active one |
A status badge underneath shows whether the install is up to date (same four states as in general settings.
Codex / Gemini → Ideafy MCP & Skills
For Codex / Gemini users, the project dialog exposes the classic Ideafy MCP & Skills toggle. It installs all three integrations for this project in one click. When on, Ideafy writes:
| What | Where | Endpoint |
|---|---|---|
| MCP server entry | .codex/config.toml or .gemini/settings.json | POST /api/projects/[id]/mcp |
Bundled skills (ideafy.md, human-test.md, product-narrative.md) | ~/.codex/skills/ or ~/.gemini/skills/ | POST /api/projects/[id]/skills |
| Phase-aware hooks | no-op on Codex / Gemini | POST /api/projects/[id]/hook (returns installed:true, applicable:false) |
See Bundled skills for the skills catalogue. Hooks don't fire on these platforms — the phase-aware policy described in Bundled Claude Code hooks is a Claude Code feature today.
Flipping the toggle off fires the matching DELETE on each endpoint — Ideafy's entries are removed from the config files but any other MCP servers or skills you have stay untouched.
The toggle reports as on only when all three endpoints report installed. If one of them drifts (e.g. you manually deleted a skill file), Ideafy will show the toggle off and flipping on reinstalls everything.
Global Install Hooks button
The main settings modal (gear icon top-right, not per-project) exposes an Install Hooks button. It re-runs the hook install across every registered project at once — useful after an Ideafy update that ships a new hook body. Existing projects pick up the changes without a manual click per project.
Note that this button only touches hooks. It does not reinstall MCP servers or skills — the per-project Ideafy MCP & Skills toggle (or the Claude Code plugin toggle) is the only way to install those. The button is hidden on Codex / Gemini since those platforms don't support hooks.
Where settings live
Per-project settings are stored in rows of the SQLite projects table. Backed up along with the rest of the local database.
Prev: General settings Next: Team settings Up: User guide index