Preferences

Use Preferences to control your profile, default workspace, locale, coding tools, folders, launch behavior, and how completed initiatives and bugs roll into recap.

Profile and locale

Profile settings include display name, avatar, language, timezone, and time format. These settings affect dashboard display and scheduled notifications.

Default workspace

Choose the default workspace used when MCP clients or the CLI create work without an explicit workspace. If a command or tool call includes a workspace, that explicit value wins.

Coding tools and folders

Select which AI coding tools and IDEs you use so One Horizon only shows relevant Open in actions. Supported tool settings include ChatGPT, Claude Desktop, Claude Code, OpenCode, Codex, Conductor, Cursor, GitHub Copilot, JetBrains IDEs, Windsurf, and n8n.

Add terminal folders for quick launch targets when opening Claude Code or OpenCode from a task.

Launcher mode

Default launcher mode controls whether task handoff starts in Plan, Build, or Review.

Preferences shape MCP, CLI, and Use in Terminal behavior.

Completed work

When you mark an initiative or a bug completed, One Horizon can add a completed day task that links back to that record. That link is what lets the closure show up in Worked on on your recap and in your work journal.

Under Create completed task when completing an initiative or bug, pick one of these behaviors:

• Ask every time — a short prompt offers to create the task or skip it. You can save your choice for next time from the prompt.
• Create automatically — a completed task is added when recap still needs a place to show the closure and nothing already represents the same work.
• No — finishing the initiative or bug does not create this extra task.

If captured work already represents the closure, the product skips the prompt because recap already has enough material.

For how that work appears in recap, see Recaps and Captured Work.