tower-studio 0.1.2 → 0.1.5

package/.next/standalone/tower/docs/en/modules/ai.md

@@ -1,110 +0,0 @@
----
-title: AI
-description: AI capability layer covering Claude Agent SDK, CLI adapter, assistant chat, task execution, and summaries
----
-
-# AI Module
-
-**Slug:** `ai`
-
-## Overview
-
-The AI capability layer manages all AI-powered features in Tower. There are 5 distinct capabilities, each serving a different purpose:
-
-1. **Assistant chat** — Multi-turn streaming conversation via the Claude Agent SDK. The assistant acts as a task management operator with access to Tower's MCP tools.
-2. **Mini summary** — Generates a short (~50 character) summary when a task execution stops, used for quick reference in the UI.
-3. **Dreaming** — Produces structured insight JSON when a task execution completes, capturing what was accomplished, patterns discovered, and learnings. These are auto-saved as notes.
-4. **Project analysis** — Analyzes a project's local directory structure on import, generating a structured description covering tech stack, architecture, and key directories.
-5. **Task execution** — Spawns a PTY terminal running Claude CLI in an isolated environment for interactive AI-driven development.
-
-Different capabilities can use different models. Lightweight tasks like mini summaries use Haiku for cost efficiency, while deeper analysis like Dreaming uses Sonnet for higher quality output.
-
-## Details
-
-- **Model routing**: Each capability specifies a suggested model. `generateSummaryFromLog` uses Haiku 4.5 for fast, cheap summaries. `generateDreamingInsight` and `analyzeProjectDirectory` use Sonnet 4.6 for deeper reasoning. Task execution and assistant chat use the system's configured default model.
-- **CLI adapter**: Currently hardcoded for Claude Code. The interface (`spawn`, `resume`, `continue`, `getSessionId`, `buildEnvOverrides`) is designed for future abstraction to support multiple CLI providers.
-- **Execution summaries**: When a task execution ends, Tower automatically extracts the terminal output log and generates both a mini summary and a Dreaming insight, attaching them to the execution record and saving the insight as a project note.
-
-## AI Capability Entry Points
-
-| Capability | File | Invocation Method | Suggested Model |
-|------------|------|-------------------|-----------------|
-| Assistant chat | `api/internal/assistant/chat/route.ts` | Agent SDK `query()` | Current default |
-| Short summary | `lib/claude-session.ts` -> `generateSummaryFromLog` | Agent SDK `aiQuery()` | Haiku 4.5 |
-| Long summary (Dreaming) | `lib/claude-session.ts` -> `generateDreamingInsight` | Agent SDK `aiQuery()` | Sonnet 4.6 |
-| Project analysis | `actions/project-actions.ts` -> `analyzeProjectDirectory` | Agent SDK `aiQuery()` | Sonnet 4.6 |
-| Task execution | `actions/agent-actions.ts` -> `startPtyExecution` | PTY spawn CLI | Current default |
-
-## File Reference
-
-### Core Library
-
-| File | Description |
-|------|-------------|
-| `lib/claude-session.ts` | Unified AI entry: `aiQuery()`, `generateSummaryFromLog()`, `generateDreamingInsight()` |
-| `lib/assistant-sessions.ts` | Assistant session management (localStorage registry) |
-| `lib/assistant-constants.ts` | `ASSISTANT_SESSION_KEY` and other constants |
-| `lib/assistant-message-converter.ts` | SDK message to UI message format conversion |
-| `lib/build-multimodal-prompt.ts` | Multimodal prompt construction (text + images) |
-| `lib/execution-summary.ts` | Post-execution summary and Dreaming insight generation |
-| `lib/cli-test.ts` | CLI adapter environment detection |
-
-### Server Actions
-
-| File | Function | Description |
-|------|----------|-------------|
-| `actions/agent-actions.ts` | `startPtyExecution` | Start Claude CLI PTY |
-| `actions/agent-actions.ts` | `resumePtyExecution` | Resume session |
-| `actions/agent-actions.ts` | `continueLatestPtyExecution` | Continue latest session |
-| `actions/cli-profile-actions.ts` | `getDefaultCliProfile` | Get active CLI profile |
-| `actions/prompt-actions.ts` | `getPrompts` / `createPrompt` | Prompt template management |
-| `actions/project-actions.ts` | `analyzeProjectDirectory` | AI project analysis |
-
-### API Routes
-
-| Route | Description |
-|-------|-------------|
-| `/api/internal/assistant/chat` | Assistant chat SSE streaming |
-| `/api/internal/assistant/sessions` | Session message retrieval |
-| `/api/internal/assistant/images` | Image serving |
-| `/api/adapters/test` | CLI adapter connection test |
-
-### Data Models
-
-| Model | Description |
-|-------|-------------|
-| `CliProfile` | CLI command, arguments, and environment variable config. `command` only allows `claude`/`claude-code` |
-| `AgentConfig` | Agent-specific config with unique constraint `(agent, configName)` |
-| `AgentPrompt` | Prompt templates, supporting global and workspace-level scopes |
-| `TaskExecution` | Execution records, including `sessionId`, `summary`, `gitLog`, `insightNoteId` |
-
-### Components
-
-| Component | Description |
-|-----------|-------------|
-| `settings/cli-profile-config.tsx` | CLI Profile configuration UI |
-| `settings/cli-adapter-tester.tsx` | CLI connection test UI |
-| `settings/prompts-config.tsx` | Prompt template management UI |
-| `settings/ai-tools-config.tsx` | Agent configuration UI |
-
-## CLI Adapter Interface (TODO)
-
-Currently hardcoded for Claude Code. Will be abstracted when integrating a second CLI:
-
-```
-spawn(cwd, args, env)        -- Start CLI process (PTY)
-resume(sessionId)            -- Resume session
-continue()                   -- Continue latest session
-getSessionId()               -- Get session ID
-getHooks() / installHooks()  -- Hook configuration and registration
-buildEnvOverrides(taskId)    -- Environment variable injection
-```
-
-See [README.md TODO](../../README.md#todo) for the detailed interface list.
-
-## Security Constraints
-
-- `CliProfile.command` is restricted to the whitelist: `claude`, `claude-code`
-- `baseArgs` prohibits shell metacharacters `;&|$()`
-- `envVars` prohibits dangerous keys: `PATH`, `LD_PRELOAD`, `NODE_OPTIONS`, etc.
-- Environment variables are injected via `envOverrides`; modifying `process.env` is forbidden

package/.next/standalone/tower/docs/en/modules/assets-notes.md

@@ -1,56 +0,0 @@
----
-title: Assets & Notes
-description: Project asset management and note-taking system
----
-
-# Assets & Notes Module
-
-**Slug:** `assets`
-
-## Overview
-
-The asset management system handles uploading images and documents with a gallery view for browsing and inline preview. Supported file types include common image formats and documents. Assets are scoped to projects and served via internal and public routes.
-
-The notes system provides project-level and task-level note-taking with category management for organization. When a task execution completes, Tower's Dreaming capability automatically generates structured insights and saves them as notes, capturing what was accomplished and any patterns discovered during the run.
-
-## Details
-
-- **Asset gallery**: Browse uploaded assets in a grid layout with image lightbox for full-size preview and text preview for document files.
-- **Upload management**: Upload images and documents through a drag-and-drop interface or file picker. Files are stored per project.
-- **Notes with categories**: Notes can be organized by category. A category filter makes it easy to find specific notes across a project.
-- **Dreaming insights**: After task execution completes, the AI generates structured insights (Dreaming) that are auto-saved as notes linked to the task. These capture patterns, decisions, and learnings from the execution.
-- **MCP access**: External agents can manage both assets and notes through MCP tools.
-
-## File Reference
-
-### Server Actions
-
-| File | Description |
-|------|-------------|
-| `asset-actions.ts` | Asset upload and management |
-| `note-actions.ts` | Note CRUD |
-
-### API Routes
-
-| Route | Description |
-|-------|-------------|
-| `/api/internal/assets/[projectId]/[filename]` | Internal asset file serving |
-| `/api/internal/assets/reveal` | Asset file location |
-| `/api/files/assets/[projectId]/[filename]` | Public asset serving |
-
-### Pages
-
-| Route | Description |
-|-------|-------------|
-| `/workspaces/[id]/assets` | Asset gallery |
-| `/workspaces/[id]/notes` | Note management |
-
-### Components
-
-**Assets** (`src/components/assets/`): `asset-upload`, `asset-list`, `image-lightbox`, `text-preview`
-
-**Notes** (`src/components/notes/`): `note-editor`, `note-list`, `note-card`, `category-filter`
-
-### MCP Tools
-
-- `manage_assets` / `manage_notes` (via `note-asset-tools.ts`)

package/.next/standalone/tower/docs/en/modules/assistant.md

@@ -1,63 +0,0 @@
----
-title: Assistant
-description: AI assistant chat system with streaming and multimodal support
----
-
-# Assistant Module
-
-**Slug:** `assistant`
-
-## Overview
-
-The built-in AI assistant is powered by the Claude Agent SDK with streaming chat support. It acts as a "task management operator" — rather than writing code directly, it manages workspaces, projects, and tasks through Tower's MCP tools. You can ask the assistant to create tasks, move them between statuses, search across projects, generate summaries, and more.
-
-The assistant supports image uploads for multimodal conversations and maintains chat history that is automatically saved. Sessions can be resumed later to continue where you left off.
-
-## Details
-
-- **Streaming responses**: Chat responses arrive via Server-Sent Events (SSE), so you see the assistant's reply as it is generated in real time.
-- **MCP tool integration**: The assistant has access to all Tower MCP tools, allowing it to perform actions like creating workspaces, listing tasks, or checking terminal output on your behalf.
-- **Multimodal input**: Upload images alongside text messages. Images are processed and included in the conversation context for the AI to reference.
-- **Session management**: Each conversation is a session with a unique ID. Sessions persist across page navigations and can be resumed from the session list.
-- **Message format conversion**: Internal SDK message formats are converted to a UI-friendly format for display, handling tool calls, thinking blocks, and rich content.
-
-## File Reference
-
-### Server Actions (`src/actions/assistant-actions.ts`)
-
-Session management and message handling.
-
-### API Routes
-
-| Route | Description |
-|-------|-------------|
-| `/api/internal/assistant/route.ts` | Assistant management |
-| `/api/internal/assistant/chat/route.ts` | Chat messages (SSE streaming) |
-| `/api/internal/assistant/images/route.ts` | Image upload |
-| `/api/internal/assistant/sessions/route.ts` | Session management |
-
-### Components (`src/components/assistant/`)
-
-| Component | Description |
-|-----------|-------------|
-| `assistant-chat.tsx` | Main chat interface |
-| `assistant-panel.tsx` | Assistant panel |
-| `image-preview.tsx` | Image preview |
-| `chat-bubble.tsx` | Message bubble |
-
-### Hooks (`src/hooks/`)
-
-| Hook | Description |
-|------|-------------|
-| `use-assistant-chat.ts` | SSE event handling |
-| `use-image-upload.ts` | Image upload |
-| `sse-event-reducer.ts` | SSE stream parsing |
-
-### Core Library
-
-| File | Description |
-|------|-------------|
-| `lib/assistant-sessions.ts` | Session management |
-| `lib/assistant-message-converter.ts` | Message format conversion |
-| `lib/claude-session.ts` | Claude API session |
-| `lib/build-multimodal-prompt.ts` | Multimodal prompt construction |

package/.next/standalone/tower/docs/en/modules/board.md

@@ -1,44 +0,0 @@
----
-title: Board
-description: Kanban board UI with drag-and-drop, filtering, and statistics
----
-
-# Board Module
-
-**Slug:** `board`
-
-## Overview
-
-The Kanban board visualizes tasks across 5 status columns: TODO, IN_PROGRESS, IN_REVIEW, DONE, and CANCELLED. Drag cards between columns to update their status, or drag within a column to reorder. A right-click context menu provides quick access to status changes, launching execution, and navigating to the task detail page. Filter tasks by labels and priority to focus on what matters. Each card displays the task title, description snippet, priority badge, and assigned labels. Pin important tasks to keep them at the top of their column.
-
-## Details
-
-- **Drag-and-drop**: Powered by dnd-kit. Dragging across columns triggers a status update; dragging within a column updates the `order` field.
-- **Context menu**: Right-click any card for quick actions — move to a different status, start or resume execution, open in detail view, or delete.
-- **Filtering**: Filter the board by one or more labels, priority levels, or both. Filters apply across all columns simultaneously.
-- **Statistics panel**: Shows task counts per status and overall progress at a glance.
-- **Pinning**: Pinned tasks always appear at the top of their column regardless of order value.
-- **Archive view**: Completed and cancelled tasks can be viewed in a separate archive page.
-
-## File Reference
-
-### Components (`src/components/board/`)
-
-| Component | Description |
-|-----------|-------------|
-| `kanban-board.tsx` | Main board container |
-| `board-column.tsx` | Status column |
-| `task-card.tsx` | Task card |
-| `board-filters.tsx` | Filters (labels, priority) |
-| `board-stats.tsx` | Statistics panel |
-
-### Pages
-
-| Route | Description |
-|-------|-------------|
-| `/workspaces/[workspaceId]` | Board main page (`board-page-client.tsx`) |
-| `/workspaces/[workspaceId]/archive` | Archived tasks (`archive-page-client.tsx`) |
-
-### State Management (`src/stores/board-store.ts`)
-
-Zustand store managing column state, filter conditions, and drag state.

package/.next/standalone/tower/docs/en/modules/git.md

@@ -1,55 +0,0 @@
----
-title: Git
-description: Git integration including repository cloning, worktree isolation, diff parsing, and merge operations
----
-
-# Git Module
-
-**Slug:** `git`
-
-## Overview
-
-Git integration provides worktree isolation so each task can work on an independent branch without affecting the main codebase. After a task execution completes, you can view diffs comparing the task branch against the base branch, and merge changes back with a single click. Tower also supports repository cloning, branch management, and auto-detection of Git information when importing a local project.
-
-## Details
-
-- **Worktree isolation**: When a task is created with `useWorktree` enabled and a `baseBranch` specified, Tower creates a separate Git worktree for that task's execution. This means the agent works in a completely isolated copy of the repository on its own branch.
-- **Diff viewing**: After execution, the task detail page shows a side-by-side diff of all changes made on the task branch compared to the base branch.
-- **One-click merge**: Review the diff and merge the task branch back into the base branch directly from the UI, with a confirmation dialog to prevent accidental merges.
-- **Auto-detection on import**: When you import a local project by specifying its directory path, Tower reads the Git remote URL, current branch, and other repository metadata automatically.
-- **Git URL resolution**: The Git Path Mapping feature in Settings maps host/owner combinations to local paths, enabling automatic resolution of Git URLs to local directories.
-
-## File Reference
-
-### Server Actions (`src/actions/git-actions.ts`)
-
-Git clone, branch management, and related operations.
-
-### API Routes
-
-| Route | Description |
-|-------|-------------|
-| `/api/git/route.ts` | Git operations API |
-| `/api/tasks/[taskId]/diff/route.ts` | Get task diff |
-| `/api/tasks/[taskId]/merge/route.ts` | Execute merge |
-
-### Core Library
-
-| File | Description |
-|------|-------------|
-| `lib/git-url.ts` | Git URL parsing and normalization |
-| `lib/worktree.ts` | Git worktree creation and management |
-| `lib/diff-parser.ts` | Git diff parser |
-
-### Components
-
-| Component | Description |
-|-----------|-------------|
-| `task-diff-view.tsx` | Diff visualization |
-| `task-merge-confirm-dialog.tsx` | Merge confirmation dialog |
-
-## Constraints
-
-- Each Task execution can run in an isolated worktree
-- `TaskExecution.worktreePath` / `worktreeBranch` record the isolation information
-- Controlled via `useWorktree` / `baseBranch` parameters when creating a task

package/.next/standalone/tower/docs/en/modules/i18n.md

@@ -1,35 +0,0 @@
----
-title: I18n
-description: Internationalization system supporting Chinese and English
----
-
-# I18n Module
-
-**Slug:** `i18n`
-
-## Overview
-
-Tower supports full internationalization with Chinese and English. All user-facing text in the application uses the `t("key")` translation function, ensuring consistent language coverage across every page and component. You can switch the language in Settings, and the change takes effect immediately without reloading the page.
-
-## Details
-
-- **Dual language maintenance**: Both Chinese (zh) and English (en) translation sets must be kept in sync. Adding a new UI string requires adding the key to both language files.
-- **Key naming convention**: Translation keys follow the format `module.feature.description` for clear organization and easy lookup.
-- **Instant switching**: Language changes apply immediately across the entire UI — no page reload or restart required.
-- **Provider-based architecture**: The i18n system uses a React Provider and hook pattern, making translations accessible from any component in the tree.
-
-## File Reference
-
-### Core Library (`src/lib/i18n/`)
-
-i18n configuration and resource management.
-
-### Usage
-
-- `src/lib/i18n.tsx` -- i18n Provider and hook
-
-## Conventions
-
-- All user-visible text must be wrapped with `t("key")`
-- Both zh/en translation sets must be maintained simultaneously
-- Key naming format: `module.feature.description`

package/.next/standalone/tower/docs/en/modules/mcp.md

@@ -1,62 +0,0 @@
----
-title: MCP
-description: Model Context Protocol Server exposing Tower tools to external AI agents
----
-
-# MCP Module
-
-**Slug:** `mcp`
-
-## Overview
-
-Tower exposes an MCP (Model Context Protocol) Server that allows external AI agents to interact with the platform programmatically. The server runs via stdio transport and provides 24 tools across 7 categories. Any MCP-compatible client — such as Claude CLI, OpenClaw, or Paperclip — can connect and manage workspaces, projects, and tasks, query live terminal output, send input to running terminals, and check execution status, all without touching the Tower UI.
-
-## Details
-
-- **Stdio transport**: The MCP server communicates over standard input/output, making it easy to integrate with any process-based MCP client.
-- **24 tools in 7 categories**: Workspace CRUD, Project CRUD, Task management, Label management, Terminal I/O, Search, and Reporting.
-- **Internal HTTP bridge**: Since MCP runs as a separate stdio process, it cannot access in-memory PTY sessions directly. Localhost-only HTTP routes (`/api/internal/terminal/[taskId]/buffer` and `/api/internal/terminal/[taskId]/input`) bridge this gap.
-- **External orchestration workflow**: Create a task, start execution, monitor via terminal output polling, send interactive input, and check completion status — all through MCP tools.
-
-## Startup Configuration
-
-```json
-{
-  "mcpServers": {
-    "tower": {
-      "command": "npx",
-      "args": ["tsx", "<project-root>/src/mcp/index.ts"]
-    }
-  }
-}
-```
-
-## File Reference
-
-### Core (`src/mcp/`)
-
-| File | Description |
-|------|-------------|
-| `server.ts` | MCP Server initialization and configuration |
-| `db.ts` | MCP-dedicated database connection |
-| `index.ts` | Entry point and exports |
-
-### Tool Modules (`src/mcp/tools/`)
-
-| File | Tool Count | Description |
-|------|------------|-------------|
-| `workspace-tools.ts` | 4 | Workspace CRUD |
-| `project-tools.ts` | 5 | Project CRUD + identify |
-| `task-tools.ts` | 5 | Task CRUD + move |
-| `label-tools.ts` | 4 | Label CRUD + set_task_labels |
-| `terminal-tools.ts` | 3 | Terminal output/input/status |
-| `search-tools.ts` | 1 | Global search |
-| `report-tools.ts` | 2 | daily_summary / daily_todo |
-| `note-asset-tools.ts` | -- | Notes and asset management |
-
-## Internal HTTP Bridge
-
-MCP stdio processes cannot access in-memory PTY sessions, so internal HTTP routes provide a bridge:
-- `GET /api/internal/terminal/[taskId]/buffer`
-- `POST /api/internal/terminal/[taskId]/input`
-- Restricted to localhost

package/.next/standalone/tower/docs/en/modules/missions.md

@@ -1,47 +0,0 @@
----
-title: Missions
-description: Multi-task monitoring dashboard with embedded terminals
----
-
-# Missions Module
-
-**Slug:** `missions`
-
-## Overview
-
-Mission Control is a multi-task monitoring dashboard that spans all workspaces. It shows every running task execution with a live embedded terminal, giving you a bird's-eye view of all ongoing AI agent work. Choose from grid layout presets (1x1, 2x1, 3x2, 2x2, 4x2, 3x3) to fit your screen — your preference is saved locally.
-
-Each mission card embeds a real-time xterm.js terminal so you can observe agent output as it happens. Cards can be reordered via drag-and-drop and are automatically removed when the execution completes naturally. You can also launch new task executions or resume previous sessions directly from the Task Picker without leaving the dashboard.
-
-## Details
-
-- **Grid layout presets**: Six layout options from single-card (1x1) to nine-card (3x3). The selected layout persists in localStorage across sessions.
-- **Workspace filtering**: A dropdown filter lets you narrow the view to tasks from a specific workspace.
-- **Task Picker**: Launch a new execution or resume a previous session by selecting a task from the picker dialog. Supports searching by task name.
-- **Auto-removal**: When a task execution completes or exits naturally, its card is automatically removed from the dashboard. Manually stopping an execution also removes the card.
-- **Drag-and-drop**: Reorder mission cards using dnd-kit to arrange your monitoring layout.
-- **Live polling**: The dashboard polls for execution status updates every 4 seconds to stay in sync.
-
-## File Reference
-
-### Pages
-
-| Route | File | Description |
-|-------|------|-------------|
-| `/missions` | `missions-client.tsx` | Missions main page |
-
-### Components (`src/components/missions/`)
-
-| Component | Description |
-|-----------|-------------|
-| `mission-card.tsx` | Task execution card (with terminal) |
-| `grid-preset-picker.tsx` | Grid layout selector |
-| `task-picker-dialog.tsx` | Task picker dialog |
-
-### Server Actions
-
-- `getActiveExecutionsAcrossWorkspaces()` -- Get all RUNNING executions
-
-### State Management (`src/stores/task-execution-store.ts`)
-
-Zustand store managing active execution state.

package/.next/standalone/tower/docs/en/modules/project.md

@@ -1,57 +0,0 @@
----
-title: Project
-description: Project management with support for regular and Git-based projects
----
-
-# Project Module
-
-**Slug:** `project`
-
-## Overview
-
-Projects belong to workspaces and serve as containers for tasks. A project can link to a Git repository or a local directory. The project type (frontend, backend, etc.) affects which features are available — for example, preview is only available for frontend projects. When importing a local project, Tower auto-detects the Git remote URL. The "Generate Description" button uses AI to analyze the project's directory structure and produce a structured description automatically.
-
-## Details
-
-- **Two project types**: `NORMAL` and `GIT`. The type is automatically derived from whether a `gitUrl` is provided — you cannot set it manually.
-- **Local import**: Point Tower at a local directory path. Git information (remote URL, current branch) is detected automatically.
-- **AI-powered analysis**: The "Generate Description" button on the project detail/import page scans the project's `localPath` and generates a structured description covering tech stack, architecture, and key directories.
-- **Repository linking**: Projects can have multiple associated repositories for broader context.
-
-## Data Model
-
-```
-Project (id, name, alias?, description?, type, gitUrl?, localPath?)
-  ├── Task[]
-  └── Repository[]
-```
-
-- `type`: `NORMAL` | `GIT`, automatically derived from whether `gitUrl` is present; cannot be set manually
-- `workspaceId`: FK to Workspace, cascade delete
-
-## File Reference
-
-### Server Actions (`src/actions/`)
-
-| File | Function | Description |
-|------|----------|-------------|
-| `workspace-actions.ts` | `createProject`, `updateProject`, `deleteProject` | Project CRUD |
-| `workspace-actions.ts` | `getProjectByLocalPath(path)` | Find by local path |
-| `workspace-actions.ts` | `getRecentLocalProjects(limit?)` | Recent local projects |
-| `project-actions.ts` | Project analysis functions | Project description generation, etc. |
-
-### Components (`src/components/project/`)
-
-| Component | Description |
-|-----------|-------------|
-| `create-project-dialog.tsx` | Create project dialog |
-| `import-project-dialog.tsx` | Import project dialog |
-
-### MCP Tools (`src/mcp/tools/project-tools.ts`)
-
-- `list_projects` / `create_project` / `update_project` / `delete_project` / `identify_project`
-
-## Constraints
-
-- `type` field is read-only, determined by the presence of `gitUrl`
-- Deleting a project cascades to all its Tasks

package/.next/standalone/tower/docs/en/modules/search.md

@@ -1,49 +0,0 @@
----
-title: Search
-description: Global search and code search across tasks, projects, and repositories
----
-
-# Search Module
-
-**Slug:** `search`
-
-## Overview
-
-Global search covers tasks, projects, repositories, notes, and assets using SQLite FTS5 full-text search. Results can be filtered by category to narrow down what you are looking for. Tower also provides in-project code search that searches within a project's local directory path, making it easy to find specific code patterns without leaving the platform.
-
-## Details
-
-- **Full-text search**: Powered by SQLite FTS5 for fast, relevance-ranked results. The FTS index must be initialized with `pnpm db:init-fts` before first use.
-- **Category filtering**: Search results can be scoped to a specific category — tasks, projects, or repositories — or left unfiltered to search across all categories.
-- **Code search**: For projects with a `localPath`, you can search code files within that directory. This is useful for finding function definitions, variable usage, or specific patterns across the codebase.
-- **Search dialog**: The global search dialog is accessible from the top bar, providing a unified entry point for all search functionality.
-
-## File Reference
-
-### Server Actions
-
-| File | Function | Description |
-|------|----------|-------------|
-| `search-actions.ts` | `globalSearch(query, category?)` | Global search |
-| `search-code-actions.ts` | Code search functions | In-project code search |
-
-### Core Library
-
-| File | Description |
-|------|-------------|
-| `lib/search.ts` | Full-text search implementation |
-| `lib/fts.ts` | SQLite FTS handling |
-
-### Components
-
-- `src/components/layout/search-dialog.tsx` -- Global search dialog
-
-### MCP Tools (`src/mcp/tools/search-tools.ts`)
-
-- `search` -- Search tasks/projects/repositories by query
-
-## Initialization
-
-```bash
-pnpm db:init-fts  # Create full-text search index
-```

package/.next/standalone/tower/docs/en/modules/settings.md

@@ -1,63 +0,0 @@
----
-title: Settings
-description: System configuration including general settings, AI tools, and CLI profiles
----
-
-# Settings Module
-
-**Slug:** `settings`
-
-## Overview
-
-System settings are organized into several sections that control Tower's behavior:
-
-- **General**: Theme selection (dark, light, or system), language toggle (Chinese/English), and default terminal application.
-- **Terminal**: WebSocket port for terminal connections and idle timeout duration.
-- **System**: Upload size limits, maximum concurrent task executions, Git operation timeout, and search tuning parameters.
-- **CLI Profile**: Configure the AI CLI command (`claude` or `claude-code`), base arguments, and environment variables. These settings affect every task execution across the platform. Only one profile can be set as the default at a time.
-- **Prompt Templates**: Create and manage custom AI prompt templates that can be scoped to a specific workspace. When launching a task execution, you can select which prompt template to use.
-- **Agent Config**: Additional prompt text and settings per AI agent type, with a unique constraint on agent + config name.
-- **Git Path Mapping**: Map Git host/owner combinations to local filesystem paths for automatic resolution of Git URLs to local directories.
-
-## Details
-
-- **Theme**: Follows system preference by default. Switching takes effect immediately without page reload.
-- **Language**: Switching between Chinese and English applies to all UI text instantly.
-- **CLI Profile security**: The `command` field only accepts `claude` or `claude-code`. The `baseArgs` field blocks shell metacharacters (`;&|$()`), and `envVars` blocks dangerous keys like `PATH`, `LD_PRELOAD`, and `NODE_OPTIONS`.
-- **Prompt templates**: Templates support both global scope (available everywhere) and workspace scope (only available within a specific workspace). Each task can select its own template before execution.
-
-## File Reference
-
-### Pages
-
-| Route | Description |
-|-------|-------------|
-| `/settings` | Settings main page |
-
-### Components (`src/components/settings/`)
-
-| Component | Description |
-|-----------|-------------|
-| `general-config.tsx` | General configuration |
-| `system-config.tsx` | System configuration |
-| `ai-tools-config.tsx` | AI tools configuration |
-| `cli-profile-config.tsx` | CLI Profile management |
-
-### Server Actions
-
-| File | Description |
-|------|-------------|
-| `config-actions.ts` | System config read/write |
-| `agent-config-actions.ts` | Agent config management |
-| `cli-profile-actions.ts` | CLI Profile CRUD |
-
-### Data Models
-
-**CliProfile**: Controls the CLI command and arguments used by PTY sessions
-- `command`: CLI command (default `claude`)
-- `baseArgs`: JSON string array
-- `envVars`: JSON object
-- `isDefault`: Only one default profile allowed
-
-**AgentConfig**: Agent-specific configuration
-- Unique constraint: `(agent, configName)`