Claude Coder

Your kanban board is now a one-click AI development pipeline.

Overview

Every developer using Claude Code has the same problem: it lives in the terminal, tasks live in the project board, and context lives in your head. You context-switch constantly — copying task titles into prompts, re-explaining checklists you already wrote, manually marking things done afterward.

Claude Coder eliminates every one of those steps. A real embedded terminal sits right next to your board. Click Ask Claude Code on any task, and Navique generates the full structured prompt, navigates to your project directory, and submits it automatically. Claude starts working immediately — with your complete task context on the first message.

Getting Started — Your First Session

One requirement: For task-linked sessions, your project needs a local folder path set. Open the project settings on your kanban board and point it at the directory on your Mac. Blank sessions work without one.

The fastest way to open a Claude Coder session:

—Open any task on your kanban board.
—Scroll to the bottom of the task detail panel.
—Click Ask Claude Code.
—The Prompt Composer opens — review the auto-generated prompt.
—Click Launch Claude.

Navique opens a terminal, navigates to your project directory, and submits the prompt to Claude automatically. Claude begins working immediately.

The Prompt Composer

The Prompt Composer is the sheet that appears before every task-linked session launch. It lets you review and adjust what gets sent to Claude before committing.

What it contains

Preamble The opening instruction sent before your task details. Defaults to a clear system instruction that tells Claude it's working through a development task. Edit it for any session that needs special behaviour — for example, if you want Claude to explain everything it does rather than just doing it.

Task card Shows your task title and description (if any) at a glance. Read-only — edit the task itself if you need changes.

Checklist (shown only when the task has checklist items) Every checklist item is listed with its current done/not-done state. Items already checked off appear struck-through. Claude receives this list in [ ] / [x] format as part of its work order.

Additional Context A free-text field for anything the prompt doesn't already cover. Examples:

—Use the existing auth pattern in AuthService.swift
—Don't modify the database schema
—This is a hotfix — keep changes minimal

Session indicator (project-linked tasks only) If this project already has an existing Claude session, a line at the bottom reads "Will resume session project-name." This means Claude will remember context from your previous conversations on this project.

Launching the session

Click Launch Claude to open the session. Navique:

—Opens a terminal tab in the Claude Coder section.
—Starts your login shell in your project directory.
—Launches Claude Code with the appropriate session flags.
—Submits your prompt automatically — Claude starts working without any further input from you.

Starting fresh

If you see "Will resume session…" but want a clean slate:

—Click Start fresh next to the session indicator.
—Confirm in the dialog that appears.
—Click Launch Claude as normal.

Navique will re-run project initialization and start a new named session. Your code is not affected — only the Claude conversation history is reset.

The Terminal

The Claude Coder terminal is a real, full-featured terminal — not a chat window. It behaves identically to opening a new terminal window on your Mac.

What you can do inside the terminal

—Read Claude's output — streaming responses, file diffs, and tool output display exactly as they do in a standalone terminal.
—Talk back to Claude — type questions, corrections, or additional instructions mid-task. Claude responds in context.
—Use slash commands — all Claude Code slash commands work: /clear, /exit, /init, /help, and others.
—Answer tool confirmations — when Claude asks permission to run a command or modify a file, you respond here.
—Run your own commands — the terminal is a real shell. You can run git status, open files, or do anything else while Claude is paused or between tasks.

Ending a session

Type /exit inside Claude Code to end the session. Navique detects the exit automatically and:

—If the session was linked to a task — presents the Session Wrap-Up card.
—If the session was not task-linked — closes the tab immediately.

Managing Multiple Sessions

You can run up to 4 Claude Code sessions simultaneously, each in its own tab.

Opening additional sessions

—From a task — click Ask Claude Code on any task. A new tab opens if you have available slots.
—From the New Session button — opens a blank interactive session with no task linked. Use this for exploratory questions or one-off work.
—From Quick Launcher — press ⌘K, type claude, and select the result to open a blank session. Type claude <your question> to open a session with a pre-filled prompt.

Switching between sessions

—Tab bar — click any tab at the top of the Claude Coder section to bring that session forward. All other sessions continue running in the background.
—Sessions sidebar — the panel on the right shows all active sessions with their task name, project directory, and how long they've been running. Click any entry to switch.

Closing a session

Click the × on any tab to close that session. If the session is linked to a task, the Session Wrap-Up card appears first. If not, the tab closes immediately.

Session Wrap-Up

When a task-linked session ends, the wrap-up card replaces the terminal output. It lets you update the task status without leaving the Claude Coder section.

What the wrap-up card shows

—The task title.
—Every checklist item, with incomplete items pre-selected — on the assumption that Claude just finished them.
—Two primary action buttons and a skip option.

Your options

Mark Done Marks all selected checklist items as complete and moves the task to the Done column on your kanban board.

Move to Review Marks all selected checklist items as complete and moves the task to the Review column. Use this when the work is done but needs a human check before closing.

Skip Closes the tab without making any changes. Use this if Claude only partially addressed the task and you intend to continue later.

Adjusting checklist items before closing

Before clicking any action, you can untick items Claude didn't actually complete. Only the ticked items get marked done. Everything else stays as-is on the task.

Sending the Next Task — Task Picker

You don't have to close the current session to start a new task. The Task Picker lets you assign Claude its next job while the session keeps running.

How to open the Task Picker

Click the Pick a Task button in the Claude Coder toolbar while a session is active.

The three-stage flow

Stage 1 — Choose a task All non-done tasks appear in a searchable list. If the current session is project-linked, the list automatically filters to show only tasks from that project. Tap any task to select it.

Stage 2 — Wrap up the current task (only shown if the session already has a linked task) Before moving on, you're given the chance to close out the task Claude just worked on. You see:

—The current task's title.
—Its checklist items, with incomplete ones pre-selected.
—The same Mark Done, Move to Review, and Skip options as the end-of-session wrap-up.
—A preview of the next task you've chosen, so you know what's coming.

Complete the current task's status, then continue.

Stage 3 — Review and send The auto-generated prompt for your newly chosen task appears for review. Click Send to Session to inject it directly into the running terminal. Claude receives the prompt immediately and begins the next task. The session's linked task is updated to the new one.

Alternatively, click Copy to Clipboard if you'd prefer to paste the prompt manually.

Project Sessions — How Continuity Works

Claude Code supports named sessions that preserve conversation context across multiple launches. Navique manages this automatically.

First session on a project

The first time you launch a Claude Coder session on a project, Navique:

—Shows a progress modal: "Initializing Claude Code for [Project Name]"
—Runs claude --init-only in your project directory — this scans your codebase and generates a CLAUDE.md file, Claude's persistent memory for the project.
—Opens the session with claude --name your-project-name, creating a named session.

You only see the initialization modal once per project.

Returning sessions

Every session after the first skips initialization entirely. Navique starts with claude --resume your-project-name. Claude remembers:

—Your codebase structure and patterns.
—Conventions and preferences established in previous sessions.
—Context from earlier conversations.

If initialization fails

A Skip Init & Open Session button appears. This bypasses initialization and opens the session directly. Claude may ask more questions about the codebase until you run /init manually inside the session.

Managing Named Sessions in Settings

Go to Settings → Claude Code to see and manage every named session the app has recorded.

What the sessions list shows

Each row displays the project name and the exact --resume command the app would use for that project (claude --resume nav-project-name).

Deleting a session record

Click the trash icon on any row and confirm. This removes the app's record for that project. The next time you open Claude Code for that project, Navique will run initialization and create a fresh named session — as if it were the first time.

Note: Deleting the record in Navique does not delete the session from Claude's own storage. It only tells Navique to treat the project as uninitialized on the next launch.

When to delete a session record

—The project was renamed and the session name is stale.
—You want Claude to re-scan the codebase and generate a fresh CLAUDE.md.
—A --resume attempt is failing and you need to start clean.
—You migrated the project to a new directory.

Quick Launcher Integration

Press ⌘K from anywhere in Navique to open the Quick Launcher.

| What you type | What happens | |---|---| | claude | Opens a blank interactive Claude Code session | | claude fix the login bug | Opens a session with "fix the login bug" pre-filled as the prompt | | claude explain AuthService.swift | Opens a session with that as the opening question |

The session opens immediately — no task required, no project navigation needed.

Frequently Asked Questions

Does Claude Coder work with any project, or only Navique-managed projects? Both. Task-linked sessions (with automatic prompt generation, session continuity, and wrap-up) require a project linked to a local folder on your Mac. But you can open a blank interactive session pointed at any directory at any time using the New Session button or Quick Launcher.

What happens if I close Navique while a session is running? The terminal process is terminated. The session ends. If the session was task-linked, Navique does not show a wrap-up card on next launch — the task remains in whatever state it was in. Reopen the task to update it manually or launch a new session.

Can I have sessions from different projects open at the same time? Yes. Each tab is a completely independent shell session in its own directory. Switching tabs doesn't affect any other running session.

What is CLAUDE.md and do I need to manage it? CLAUDE.md is generated by claude --init-only in your project root. It contains a description of your project's architecture, commands, and conventions — Claude reads it at the start of every session to understand your codebase without you having to re-explain it. Navique generates it automatically on first launch. You can edit it by hand at any time to add conventions, update architecture notes, or include anything you want Claude to always know about the project.

Can I use Claude Coder without a kanban task? Yes. Use the New Session button or the Quick Launcher to open a blank session. You get the full terminal experience without any task association. Session continuity and wrap-up are not available in blank sessions.

The session says "Will resume" but I want to start over without resetting the whole project. Go to Settings → Claude Code, find the project row, and delete it. The next launch runs init fresh and creates a new named session. Or use the Start Fresh link in the Prompt Composer.

I deleted a session record in Settings but it still tried to resume. Quit and relaunch Navique. The session store is read at launch time.

Troubleshooting

"claude: command not found" in the terminal The claude CLI is not on your $PATH. Install it (npm install -g @anthropic-ai/claude-code) and ensure your shell's PATH is configured correctly in your .zshrc or .bashrc.

Session opens but Claude immediately exits The named session referenced by --resume may no longer exist in Claude's own storage. Go to Settings → Claude Code, delete the session record for this project, and relaunch. Navique will run initialization and create a fresh session.

Initialization modal appears every time I open a session The initialization step marks the project as initialized only when --init-only completes successfully. If your project directory path is wrong or the folder doesn't exist, initialization fails silently and the record is not saved. Check that the folder path in your project settings is correct and the folder exists.

Prompt is sent but Claude doesn't start working Claude's TUI may still be loading. The prompt is submitted after a short delay to allow Claude to initialize. If it consistently fails, try launching the session and submitting the prompt manually — open the task picker and use Copy to Clipboard instead of Send to Session.

Wrap-up card doesn't appear when I close a session The wrap-up card only appears for sessions launched from a task with a task ID. Sessions opened via the New Session button or Quick Launcher without a task are not task-linked and close without a wrap-up.