Centralize config paths and prompts into dedicated modules

- Add CODEY_DIR and TRANSCRIPTS_DIR constants to config.rs
- Create prompts.rs with all system prompts (SYSTEM_PROMPT,
  COMPACTION_PROMPT, SUB_AGENT_PROMPT, WELCOME_MESSAGE)
- Update app.rs to import from config and prompts modules
- Update transcript.rs to import paths from config
- Update spawn_agent.rs to import prompt from prompts module
- Add prompts module to lib.rs and main.rs

This removes the cross-module dependencies that required importing
from app.rs, making the codebase cleaner and avoiding issues with
library builds.

Author: claude

src/app.rs

@@ -17,86 +17,25 @@ use ratatui::{
 use tokio::sync::oneshot;
 
 use crate::commands::Command;
-use crate::config::{AgentRuntimeConfig, Config};
+use crate::config::{AgentRuntimeConfig, Config, CODEY_DIR};
 use crate::ide::{Ide, IdeEvent, Nvim};
 use crate::llm::{Agent, AgentId, AgentRegistry, AgentStep, RequestMode};
 #[cfg(feature = "profiling")]
 use crate::{profile_frame, profile_span};
+use crate::prompts::{COMPACTION_PROMPT, SYSTEM_MD_FILENAME, SYSTEM_PROMPT, WELCOME_MESSAGE};
 use crate::tool_filter::ToolFilters;
 use crate::tools::{
     init_agent_context, update_agent_oauth, Effect, ToolCall, ToolDecision, ToolEvent,
     ToolExecutor, ToolRegistry,
 };
-use crate::transcript::{BlockType, Role, Status, TextBlock, Transcript, CODEY_DIR};
+use crate::transcript::{BlockType, Role, Status, TextBlock, Transcript};
 use crate::ui::{Attachment, ChatView, InputBox};
 
 const MIN_FRAME_TIME: Duration = Duration::from_millis(16);
 
 pub const APP_NAME: &str = "Codey";
 pub const APP_VERSION: &str = env!("CARGO_PKG_VERSION");
 
-const WELCOME_MESSAGE: &str =
-    "Welcome to Codey! I'm your AI coding assistant. How can I help you today?";
-const SYSTEM_PROMPT: &str = r#"You are Codey, an AI coding assistant running in a terminal interface.
-
-## Capabilities
-You have access to the following tools:
-- `read_file`: Read file contents, optionally with line ranges
-- `write_file`: Create new files
-- `edit_file`: Make precise edits using search/replace
-- `shell`: Execute bash commands
-- `fetch_url`: Fetch web content
-
-## Guidelines
-
-### Reading Files
-- Always read a file before editing it
-- Use line ranges for large files: `read_file(path, start_line=100, end_line=200)`
-- Use `shell("ls -la")` to explore directories
-- When reading files, be careful about reading large files in one-go. Use line ranges, 
-    or check the file stats with `shell("stat <file_path>")` first.
-- shell grep is a great way to get a line number to read a targeted section of a file
-
-### Editing Files
-- Use `edit_file` for existing files, `write_file` only for new files
-- The `old_string` must match EXACTLY, including whitespace and indentation
-- If `old_string` appears multiple times, include more context to make it unique
-- Apply edits sequentially; each edit sees the result of previous edits
-- You can do multiple edits at once, but keep it under 1000 lines
-- Avoid the urge to completely rewrite files - make precise, minimal edits so the user can review them easily
-
-### Shell Commands
-- Prefer `read_file` over `cat`, `head`, `tail`
-- Use `ls` for directory exploration
-- Use `grep` or `rg` for searching code
-
-### Background Execution
-For long-running operations, you can execute tools in the background by adding `"background": true` to the tool call. This returns immediately with a task ID while the tool runs asynchronously.
-Use `list_background_tasks` to check status and `get_background_task` to retrieve results when complete.
-
-### General
-- Be concise but thorough
-- Explain what you're doing before executing tools
-- If a tool fails, explain the error and suggest fixes
-- Ask for clarification if the request is ambiguous
-- If you feel like backing out of a path, always get confirmation before git resetting the work tree
-- Always get confirmation before making destructive changes (this includes building a release)
-"#;
-const COMPACTION_PROMPT: &str = r#"The conversation context is getting large and needs to be compacted.
-
-Please provide a comprehensive summary of our conversation so far in markdown format. Include:
-
-1. **What was accomplished** - Main tasks and changes completed as a bulleted list
-2. **What still needs to be done** - Remaining tasks or open areas of work as a bulleted list
-3. **Key project information** - Important facts about the project that the user has shared or that we're not immediately apparent
-4. **Relevant files** - Files most relevant to the current work with brief descriptions, line numbers, or method/variable names
-5. **Relevant documentation paths or URLs** - Links to docs or resources we will use to continue our work
-6. **Quotes and log snippets** - Any important quotes or logs that the user provided that we'll need later
-
-Be thorough but concise - this summary will seed a fresh conversation context."#;
-
-const SYSTEM_MD_FILENAME: &str = "SYSTEM.md";
-
 /// Build the complete system prompt by appending content from SYSTEM.md files.
 /// Checks (in order):
 /// 1. User config: ~/.config/codey/SYSTEM.md

src/config.rs

@@ -11,6 +11,12 @@ use crate::tools::{
     EditFileTool, FetchUrlTool, ReadFileTool, ShellTool, WebSearchTool, WriteFileTool,
 };
 
+/// Directory name for Codey project-level configuration and data
+pub const CODEY_DIR: &str = ".codey";
+
+/// Directory name for storing conversation transcripts
+pub const TRANSCRIPTS_DIR: &str = "transcripts";
+
 /// Main configuration structure
 #[derive(Debug, Clone, Serialize, Deserialize)]
 #[serde(default)]

src/lib.rs

@@ -45,6 +45,7 @@ mod compaction;
 mod config;
 mod ide;
 mod llm;
+mod prompts;
 mod tool_filter;
 mod tools;
 mod transcript;

src/main.rs

@@ -7,6 +7,7 @@ mod ide;
 mod llm;
 #[cfg(feature = "profiling")]
 mod profiler;
+mod prompts;
 mod tool_filter;
 mod tools;
 mod transcript;

src/prompts.rs

@@ -0,0 +1,90 @@
+//! Centralized prompt definitions for Codey
+//!
+//! This module contains all system prompts used throughout the application.
+
+/// Welcome message shown when the application starts
+pub const WELCOME_MESSAGE: &str =
+    "Welcome to Codey! I'm your AI coding assistant. How can I help you today?";
+
+/// Main system prompt for the primary agent
+pub const SYSTEM_PROMPT: &str = r#"You are Codey, an AI coding assistant running in a terminal interface.
+
+## Capabilities
+You have access to the following tools:
+- `read_file`: Read file contents, optionally with line ranges
+- `write_file`: Create new files
+- `edit_file`: Make precise edits using search/replace
+- `shell`: Execute bash commands
+- `fetch_url`: Fetch web content
+
+## Guidelines
+
+### Reading Files
+- Always read a file before editing it
+- Use line ranges for large files: `read_file(path, start_line=100, end_line=200)`
+- Use `shell("ls -la")` to explore directories
+- When reading files, be careful about reading large files in one-go. Use line ranges,
+    or check the file stats with `shell("stat <file_path>")` first.
+- shell grep is a great way to get a line number to read a targeted section of a file
+
+### Editing Files
+- Use `edit_file` for existing files, `write_file` only for new files
+- The `old_string` must match EXACTLY, including whitespace and indentation
+- If `old_string` appears multiple times, include more context to make it unique
+- Apply edits sequentially; each edit sees the result of previous edits
+- You can do multiple edits at once, but keep it under 1000 lines
+- Avoid the urge to completely rewrite files - make precise, minimal edits so the user can review them easily
+
+### Shell Commands
+- Prefer `read_file` over `cat`, `head`, `tail`
+- Use `ls` for directory exploration
+- Use `grep` or `rg` for searching code
+
+### Background Execution
+For long-running operations, you can execute tools in the background by adding `"background": true` to the tool call. This returns immediately with a task ID while the tool runs asynchronously.
+Use `list_background_tasks` to check status and `get_background_task` to retrieve results when complete.
+
+### General
+- Be concise but thorough
+- Explain what you're doing before executing tools
+- If a tool fails, explain the error and suggest fixes
+- Ask for clarification if the request is ambiguous
+- If you feel like backing out of a path, always get confirmation before git resetting the work tree
+- Always get confirmation before making destructive changes (this includes building a release)
+"#;
+
+/// Prompt used when compacting conversation context
+pub const COMPACTION_PROMPT: &str = r#"The conversation context is getting large and needs to be compacted.
+
+Please provide a comprehensive summary of our conversation so far in markdown format. Include:
+
+1. **What was accomplished** - Main tasks and changes completed as a bulleted list
+2. **What still needs to be done** - Remaining tasks or open areas of work as a bulleted list
+3. **Key project information** - Important facts about the project that the user has shared or that we're not immediately apparent
+4. **Relevant files** - Files most relevant to the current work with brief descriptions, line numbers, or method/variable names
+5. **Relevant documentation paths or URLs** - Links to docs or resources we will use to continue our work
+6. **Quotes and log snippets** - Any important quotes or logs that the user provided that we'll need later
+
+Be thorough but concise - this summary will seed a fresh conversation context."#;
+
+/// System prompt for sub-agents (background research agents)
+pub const SUB_AGENT_PROMPT: &str = r#"You are a background research agent. Your task is to investigate, explore, or analyze as directed.
+
+## Capabilities
+You have read-only access to:
+- `read_file`: Read file contents
+- `shell`: Execute commands (for searching, exploring)
+- `fetch_url`: Fetch web content
+- `web_search`: Search the web
+- `open_file`: Signal a file to open in the IDE
+
+## Guidelines
+- Focus on the specific task assigned to you
+- Be thorough but concise in your findings
+- Report back with structured, actionable information
+- You cannot modify files - only read and explore
+- If you need to suggest changes, describe them clearly for the primary agent to implement
+"#;
+
+/// Filename for custom system prompt additions
+pub const SYSTEM_MD_FILENAME: &str = "SYSTEM.md";

src/tools/impls/spawn_agent.rs

@@ -3,14 +3,15 @@
 use std::sync::OnceLock;
 
 use super::{Tool, ToolPipeline};
-use crate::tools::ToolRegistry;
 use crate::auth::OAuthCredentials;
 use crate::config::AgentRuntimeConfig;
 use crate::impl_base_block;
-use crate::llm::{Agent, RequestMode};
 use crate::llm::background::run_agent;
+use crate::llm::{Agent, RequestMode};
+use crate::prompts::SUB_AGENT_PROMPT;
 use crate::tools::pipeline::{EffectHandler, Step};
-use crate::transcript::{render_approval_prompt, render_prefix, Block, BlockType, ToolBlock, Status};
+use crate::tools::ToolRegistry;
+use crate::transcript::{render_approval_prompt, render_prefix, Block, BlockType, Status, ToolBlock};
 use ratatui::{
     style::{Color, Style},
     text::{Line, Span},
@@ -19,25 +20,6 @@ use serde::{Deserialize, Serialize};
 use serde_json::json;
 use tokio::sync::RwLock;
 
-/// System prompt for sub-agents (background research agents)
-const SUB_AGENT_PROMPT: &str = r#"You are a background research agent. Your task is to investigate, explore, or analyze as directed.
-
-## Capabilities
-You have read-only access to:
-- `read_file`: Read file contents
-- `shell`: Execute commands (for searching, exploring)
-- `fetch_url`: Fetch web content
-- `web_search`: Search the web
-- `open_file`: Signal a file to open in the IDE
-
-## Guidelines
-- Focus on the specific task assigned to you
-- Be thorough but concise in your findings
-- Report back with structured, actionable information
-- You cannot modify files - only read and explore
-- If you need to suggest changes, describe them clearly for the primary agent to implement
-"#;
-
 // =============================================================================
 // Agent Context - global state for spawning sub-agents
 // =============================================================================

src/transcript.rs

@@ -13,11 +13,7 @@ use ratatui::{
 use serde::{Deserialize, Serialize};
 
 use crate::compaction::CompactionBlock;
-
-/// Directory name for Codey project-level configuration and data
-pub const CODEY_DIR: &str = ".codey";
-/// Directory name for storing transcripts
-pub const TRANSCRIPTS_DIR: &str = "transcripts";
+use crate::config::{CODEY_DIR, TRANSCRIPTS_DIR};
 
 
 /// Role of the message sender