byterover-cli 1.7.2 → 1.8.0

package/dist/agent/infra/tools/implementations/create-knowledge-topic-tool.js

@@ -1,149 +0,0 @@
-import { join } from 'node:path';
-import { z } from 'zod';
-import { DirectoryManager } from '../../../../server/core/domain/knowledge/directory-manager.js';
-import { MarkdownWriter } from '../../../../server/core/domain/knowledge/markdown-writer.js';
-import { sanitizeFolderName } from '../../../../server/utils/file-helpers.js';
-import { ToolName } from '../../../core/domain/tools/constants.js';
-const CreateKnowledgeTopicInputSchema = z.object({
-    // Base path for knowledge storage
-    basePath: z.string().default('.brv/context-tree'),
-    domains: z.array(z.string()).describe('Array of domain names (dynamically created based on content)'),
-    // Manual topics (optional)
-    topics: z
-        .array(z.object({
-        domain: z.string().describe('Domain category name (can be any semantically meaningful name)'),
-        name: z.string().describe('Topic name'),
-        relations: z
-            .array(z.string())
-            .optional()
-            .describe('Related topics using domain/topic or domain/topic/subtopic notation'),
-        snippets: z.array(z.string()).describe('Code/text snippets'),
-        subtopics: z
-            .array(z.object({
-            name: z.string().describe('Subtopic name'),
-            relations: z
-                .array(z.string())
-                .optional()
-                .describe('Related topics using domain/topic or domain/topic/subtopic notation'),
-            snippets: z.array(z.string()).describe('Code/text snippets'),
-        }))
-            .describe('Array of subtopics'),
-    }))
-        .describe('Array of topics for each domain'),
-});
-/**
- * Execute function for create knowledge topic tool
- */
-async function executeCreateKnowledgeTopic(input, _context) {
-    const { basePath, topics } = input;
-    // Ensure base knowledge structure exists
-    await DirectoryManager.ensureKnowledgeStructure(basePath);
-    const created = [];
-    const updated = [];
-    // Process each topic sequentially (domains/topics must be created in order)
-    /* eslint-disable no-await-in-loop -- Sequential processing required for domain/topic hierarchy */
-    for (const topicData of topics) {
-        const { domain, name: topicName, relations, snippets, subtopics: subtopicData } = topicData;
-        // Create or update domain folder
-        const domainPath = join(basePath, sanitizeFolderName(domain));
-        const domainResult = await DirectoryManager.createOrUpdateDomain(domainPath);
-        // Create or update topic folder
-        const topicPath = join(domainPath, sanitizeFolderName(topicName));
-        const topicResult = await DirectoryManager.createOrUpdateTopic(topicPath);
-        // Generate and write topic context.md
-        const topicContextContent = MarkdownWriter.generateContext({
-            name: topicName,
-            relations,
-            snippets,
-        });
-        const topicContextPath = join(topicPath, 'context.md');
-        await DirectoryManager.writeFileAtomic(topicContextPath, topicContextContent);
-        // Process subtopics in parallel
-        const subtopicResults = await Promise.all(subtopicData.map(async (subtopic) => {
-            // Create subtopic folder
-            const subtopicPath = join(topicPath, sanitizeFolderName(subtopic.name));
-            const subtopicResult = await DirectoryManager.createOrUpdateTopic(subtopicPath);
-            // Generate and write subtopic context.md
-            const subtopicContextContent = MarkdownWriter.generateContext({
-                name: subtopic.name,
-                relations: subtopic.relations,
-                snippets: subtopic.snippets,
-            });
-            const subtopicContextPath = join(subtopicPath, 'context.md');
-            await DirectoryManager.writeFileAtomic(subtopicContextPath, subtopicContextContent);
-            return {
-                existed: !subtopicResult.created,
-                name: subtopic.name,
-            };
-        }));
-        // Separate created vs updated subtopics
-        const createdSubtopics = subtopicResults.filter((r) => !r.existed).map((r) => r.name);
-        const updatedSubtopics = subtopicResults.filter((r) => r.existed).map((r) => r.name);
-        // Track what was created vs updated
-        if (domainResult.created || topicResult.created) {
-            created.push({
-                domain,
-                subtopics: createdSubtopics,
-                topic: topicName,
-            });
-        }
-        else {
-            updated.push({
-                domain,
-                subtopics: updatedSubtopics,
-                topic: topicName,
-            });
-        }
-    }
-    /* eslint-enable no-await-in-loop */
-    return {
-        created,
-        updated,
-    };
-}
-/**
- * Creates the create knowledge topic tool.
- *
- * Creates organized knowledge topics within domain folders, where each topic and subtopic
- * has its own folder containing a context.md file with relevant snippets. This tool should
- * be used after detecting domains to organize the extracted knowledge into a structured hierarchy.
- *
- * @returns Configured create knowledge topic tool
- */
-export function createCreateKnowledgeTopicTool() {
-    return {
-        description: `Create organized knowledge topics within dynamically-created domain folders. This tool structures knowledge by creating domain, topic, and subtopic folders, each containing a context.md file with relevant snippets and optional relations.
-
-**Dynamic Domain Creation:**
-Domains are created dynamically based on the content being organized. Choose domain names that:
-- Are semantically meaningful and descriptive (e.g., "authentication", "api_design", "data_models")
-- Use snake_case format (1-3 words)
-- Group related concepts together
-- Avoid overly generic names (e.g., "misc", "other") or overly specific names
-
-**Hierarchical Structure:**
-- Domain folders (e.g., .brv/context-tree/authentication/)
-- Topic folders (e.g., .brv/context-tree/authentication/oauth_flow/)
-- Topic context.md files (e.g., .brv/context-tree/authentication/oauth_flow/context.md)
-- Subtopic folders (e.g., .brv/context-tree/authentication/oauth_flow/token_refresh/)
-- Subtopic context.md files (e.g., .brv/context-tree/authentication/oauth_flow/token_refresh/context.md)
-
-**Each topic should include:**
-1. A clear topic name
-2. Relevant code/text snippets that demonstrate the knowledge
-3. Optional relations to other topics using domain/topic or domain/topic/subtopic notation
-4. Subtopics (optional) that break down the topic into smaller pieces
-
-**Relations** enhance knowledge discovery by linking related contexts. Example:
-- relations: ['authentication/session_management', 'api_design/endpoints/validation']
-
-**The tool automatically:**
-- Creates the base knowledge structure if it doesn't exist
-- Creates domain, topic, and subtopic folders as needed
-- Generates context.md files with snippets and relations
-- Handles existing topics gracefully (updates instead of recreating)`,
-        execute: executeCreateKnowledgeTopic,
-        id: ToolName.CREATE_KNOWLEDGE_TOPIC,
-        inputSchema: CreateKnowledgeTopicInputSchema,
-    };
-}

package/dist/agent/infra/tools/implementations/delete-memory-tool.d.ts

@@ -1,12 +0,0 @@
-import type { Tool } from '../../../core/domain/tools/types.js';
-import type { MemoryManager } from '../../memory/memory-manager.js';
-/**
- * Delete memory tool.
- *
- * Removes a memory from the scratch pad. Also deletes any blob attachments
- * associated with the memory. Use this to clean up outdated or unnecessary context.
- *
- * @param memoryManager - Memory manager service dependency
- * @returns Configured delete memory tool
- */
-export declare function createDeleteMemoryTool(memoryManager: MemoryManager): Tool;

package/dist/agent/infra/tools/implementations/delete-memory-tool.js

@@ -1,37 +0,0 @@
-import { z } from 'zod';
-import { ToolName } from '../../../core/domain/tools/constants.js';
-/**
- * Input schema for delete memory tool.
- */
-const DeleteMemoryInputSchema = z
-    .object({
-    id: z.string().min(1).describe('Unique identifier of the memory to delete'),
-})
-    .strict();
-/**
- * Delete memory tool.
- *
- * Removes a memory from the scratch pad. Also deletes any blob attachments
- * associated with the memory. Use this to clean up outdated or unnecessary context.
- *
- * @param memoryManager - Memory manager service dependency
- * @returns Configured delete memory tool
- */
-export function createDeleteMemoryTool(memoryManager) {
-    return {
-        description: 'Delete a memory by ID. Removes the memory and all associated attachments from the scratch pad. Use this to clean up outdated context.',
-        async execute(input, _context) {
-            const { id } = input;
-            // Delete memory
-            await memoryManager.delete(id);
-            // Return confirmation
-            return {
-                deleted: true,
-                id,
-                message: `Memory ${id} has been deleted successfully`,
-            };
-        },
-        id: ToolName.DELETE_MEMORY,
-        inputSchema: DeleteMemoryInputSchema,
-    };
-}

package/dist/agent/infra/tools/implementations/edit-file-tool.d.ts

@@ -1,13 +0,0 @@
-import type { Tool } from '../../../core/domain/tools/types.js';
-import type { IFileSystem } from '../../../core/interfaces/i-file-system.js';
-/**
- * Creates the edit file tool.
- *
- * Edits a file by replacing text.
- * By default, requires oldString to be unique (only one occurrence).
- * Set replaceAll to true to replace all occurrences.
- *
- * @param fileSystemService - File system service dependency
- * @returns Configured edit file tool
- */
-export declare function createEditFileTool(fileSystemService: IFileSystem): Tool;

package/dist/agent/infra/tools/implementations/edit-file-tool.js

@@ -1,50 +0,0 @@
-import { z } from 'zod';
-import { ToolName } from '../../../core/domain/tools/constants.js';
-/**
- * Input schema for edit file tool.
- */
-const EditFileInputSchema = z
-    .object({
-    filePath: z.string().describe('Absolute path to the file to edit'),
-    newString: z.string().describe('Replacement text'),
-    oldString: z.string().describe('Text to replace (must be unique unless replaceAll is true)'),
-    replaceAll: z
-        .boolean()
-        .optional()
-        .default(false)
-        .describe('Replace all occurrences (default: false, requires unique match)'),
-})
-    .strict();
-/**
- * Creates the edit file tool.
- *
- * Edits a file by replacing text.
- * By default, requires oldString to be unique (only one occurrence).
- * Set replaceAll to true to replace all occurrences.
- *
- * @param fileSystemService - File system service dependency
- * @returns Configured edit file tool
- */
-export function createEditFileTool(fileSystemService) {
-    return {
-        description: 'Edit a file by replacing text. By default requires unique match (set replaceAll=true for multiple replacements).',
-        async execute(input, _context) {
-            const { filePath, newString, oldString, replaceAll } = input;
-            // Call file system service
-            const result = await fileSystemService.editFile(filePath, {
-                newString,
-                oldString,
-                replaceAll,
-            }, {});
-            // Return formatted result
-            return {
-                bytesWritten: result.bytesWritten,
-                path: result.path,
-                replacements: result.replacements,
-                success: result.success,
-            };
-        },
-        id: ToolName.EDIT_FILE,
-        inputSchema: EditFileInputSchema,
-    };
-}

package/dist/agent/infra/tools/implementations/edit-memory-tool.d.ts

@@ -1,13 +0,0 @@
-import type { Tool } from '../../../core/domain/tools/types.js';
-import type { MemoryManager } from '../../memory/memory-manager.js';
-/**
- * Creates the edit memory tool.
- *
- * Updates an existing memory's content, tags, or pinned status. Metadata is merged
- * while content and tags are replaced if provided. Use this to refine or update
- * context in the scratch pad.
- *
- * @param memoryManager - Memory manager service dependency
- * @returns Configured edit memory tool
- */
-export declare function createEditMemoryTool(memoryManager: MemoryManager): Tool;

package/dist/agent/infra/tools/implementations/edit-memory-tool.js

@@ -1,53 +0,0 @@
-import { z } from 'zod';
-import { ToolName } from '../../../core/domain/tools/constants.js';
-/**
- * Input schema for edit memory tool.
- */
-const EditMemoryInputSchema = z
-    .object({
-    content: z
-        .string()
-        .min(1, 'Memory content cannot be empty')
-        .max(10_000, 'Memory content cannot exceed 10,000 characters')
-        .optional()
-        .describe('Updated content for the memory'),
-    id: z.string().min(1).describe('Unique identifier of the memory to edit'),
-    pinned: z.boolean().optional().describe('Updated pinned status'),
-})
-    .strict();
-/**
- * Creates the edit memory tool.
- *
- * Updates an existing memory's content, tags, or pinned status. Metadata is merged
- * while content and tags are replaced if provided. Use this to refine or update
- * context in the scratch pad.
- *
- * @param memoryManager - Memory manager service dependency
- * @returns Configured edit memory tool
- */
-export function createEditMemoryTool(memoryManager) {
-    return {
-        description: 'Edit an existing memory. Update content, tags, or pinned status. Use this to refine or update previously stored context.',
-        async execute(input, _context) {
-            const { content, id, pinned } = input;
-            // Build update input
-            const updateInput = {};
-            if (content !== undefined) {
-                updateInput.content = content;
-            }
-            if (pinned !== undefined) {
-                updateInput.metadata = { pinned };
-            }
-            // Update memory
-            const updatedMemory = await memoryManager.update(id, updateInput);
-            // Return formatted result
-            return {
-                content: updatedMemory.content,
-                id: updatedMemory.id,
-                updatedAt: new Date(updatedMemory.updatedAt).toISOString(),
-            };
-        },
-        id: ToolName.EDIT_MEMORY,
-        inputSchema: EditMemoryInputSchema,
-    };
-}

package/dist/agent/infra/tools/implementations/kill-process-tool.d.ts

@@ -1,12 +0,0 @@
-import type { Tool } from '../../../core/domain/tools/types.js';
-import type { IProcessService } from '../../../core/interfaces/i-process-service.js';
-/**
- * Create kill_process tool.
- *
- * Terminates a background process started by bash_exec.
- * Uses graceful shutdown (SIGTERM) with escalation to SIGKILL after 5 seconds.
- *
- * @param processService - Process service for killing processes
- * @returns kill_process tool instance
- */
-export declare function createKillProcessTool(processService: IProcessService): Tool;

package/dist/agent/infra/tools/implementations/kill-process-tool.js

@@ -1,55 +0,0 @@
-import { z } from 'zod';
-import { ToolName } from '../../../core/domain/tools/constants.js';
-/**
- * Input schema for kill_process tool.
- */
-const KillProcessInputSchema = z
-    .object({
-    /**
-     * Unique process identifier from bash_exec.
-     */
-    processId: z.string().describe('Unique process identifier from bash_exec'),
-})
-    .strict();
-/**
- * Create kill_process tool.
- *
- * Terminates a background process started by bash_exec.
- * Uses graceful shutdown (SIGTERM) with escalation to SIGKILL after 5 seconds.
- *
- * @param processService - Process service for killing processes
- * @returns kill_process tool instance
- */
-export function createKillProcessTool(processService) {
-    return {
-        description: `Terminate a background process started by bash_exec.
-
-Features:
-- Graceful shutdown: Sends SIGTERM first to allow cleanup
-- Force kill: Escalates to SIGKILL after 5 seconds if still running
-- Idempotent: Safe to call on already-terminated processes
-
-Signal handling:
-1. Sends SIGTERM (allows process to cleanup gracefully)
-2. Waits 5 seconds
-3. Sends SIGKILL if process still running (force terminate)
-
-Use cases:
-- Stop long-running commands that are no longer needed
-- Cancel background processes that are taking too long
-- Clean up processes before starting new ones`,
-        async execute(input, _context) {
-            const { processId } = input;
-            // Kill process via process service
-            await processService.killProcess(processId);
-            // Return success confirmation
-            return {
-                message: `Process ${processId} terminated successfully`,
-                processId,
-                success: true,
-            };
-        },
-        id: ToolName.KILL_PROCESS,
-        inputSchema: KillProcessInputSchema,
-    };
-}

package/dist/agent/infra/tools/implementations/list-memories-tool.d.ts

@@ -1,12 +0,0 @@
-import type { Tool } from '../../../core/domain/tools/types.js';
-import type { MemoryManager } from '../../memory/memory-manager.js';
-/**
- * Creates the list memories tool.
- *
- * Lists and filters memories stored in the scratch pad. Supports filtering by
- * tags, pinned status, and source. Results are sorted by most recently updated first.
- *
- * @param memoryManager - Memory manager service dependency
- * @returns Configured list memories tool
- */
-export declare function createListMemoriesTool(memoryManager: MemoryManager): Tool;

package/dist/agent/infra/tools/implementations/list-memories-tool.js

@@ -1,63 +0,0 @@
-import { z } from 'zod';
-import { ToolName } from '../../../core/domain/tools/constants.js';
-/**
- * Input schema for list memories tool.
- */
-const ListMemoriesInputSchema = z
-    .object({
-    limit: z
-        .number()
-        .int()
-        .positive()
-        .optional()
-        .describe('Maximum number of memories to return'),
-    offset: z
-        .number()
-        .int()
-        .nonnegative()
-        .optional()
-        .describe('Number of memories to skip (for pagination)'),
-    pinned: z.boolean().optional().describe('Filter by pinned status'),
-    source: z
-        .enum(['agent', 'system', 'user'])
-        .optional()
-        .describe('Filter by source (default: agent)'),
-})
-    .strict();
-/**
- * Creates the list memories tool.
- *
- * Lists and filters memories stored in the scratch pad. Supports filtering by
- * tags, pinned status, and source. Results are sorted by most recently updated first.
- *
- * @param memoryManager - Memory manager service dependency
- * @returns Configured list memories tool
- */
-export function createListMemoriesTool(memoryManager) {
-    return {
-        description: 'List and filter memories from the scratch pad. Returns memories sorted by most recent first. Use this to discover what context has been stored.',
-        async execute(input, _context) {
-            const { limit, offset, pinned, source } = input;
-            // List memories with filters
-            const memories = await memoryManager.list({
-                limit,
-                offset,
-                pinned,
-                source,
-            });
-            // Return formatted result with preview
-            return {
-                count: memories.length,
-                memories: memories.map(m => ({
-                    contentPreview: m.content.length > 200 ? `${m.content.slice(0, 200)}...` : m.content,
-                    createdAt: new Date(m.createdAt).toISOString(),
-                    id: m.id,
-                    pinned: m.metadata?.pinned ?? false,
-                    updatedAt: new Date(m.updatedAt).toISOString(),
-                })),
-            };
-        },
-        id: ToolName.LIST_MEMORIES,
-        inputSchema: ListMemoriesInputSchema,
-    };
-}

package/dist/agent/infra/tools/implementations/read-memory-tool.d.ts

@@ -1,12 +0,0 @@
-import type { Tool } from '../../../core/domain/tools/types.js';
-import type { MemoryManager } from '../../memory/memory-manager.js';
-/**
- * Read memory tool.
- *
- * Retrieves a specific memory by its ID. Use this to recall previously stored
- * context, intermediate results, or findings from the scratch pad.
- *
- * @param memoryManager - Memory manager service dependency
- * @returns Configured read memory tool
- */
-export declare function createReadMemoryTool(memoryManager: MemoryManager): Tool;

package/dist/agent/infra/tools/implementations/read-memory-tool.js

@@ -1,39 +0,0 @@
-import { z } from 'zod';
-import { ToolName } from '../../../core/domain/tools/constants.js';
-/**
- * Input schema for read memory tool.
- */
-const ReadMemoryInputSchema = z
-    .object({
-    id: z.string().min(1).describe('Unique identifier of the memory to retrieve'),
-})
-    .strict();
-/**
- * Read memory tool.
- *
- * Retrieves a specific memory by its ID. Use this to recall previously stored
- * context, intermediate results, or findings from the scratch pad.
- *
- * @param memoryManager - Memory manager service dependency
- * @returns Configured read memory tool
- */
-export function createReadMemoryTool(memoryManager) {
-    return {
-        description: 'Read a specific memory by ID. Use this to retrieve previously stored context, findings, or intermediate results from the scratch pad.',
-        async execute(input, _context) {
-            const { id } = input;
-            // Retrieve memory
-            const memory = await memoryManager.get(id);
-            // Return formatted result
-            return {
-                content: memory.content,
-                createdAt: new Date(memory.createdAt).toISOString(),
-                id: memory.id,
-                metadata: memory.metadata,
-                updatedAt: new Date(memory.updatedAt).toISOString(),
-            };
-        },
-        id: ToolName.READ_MEMORY,
-        inputSchema: ReadMemoryInputSchema,
-    };
-}

package/dist/agent/infra/tools/implementations/read-todos-tool.d.ts

@@ -1,11 +0,0 @@
-import type { Tool } from '../../../core/domain/tools/types.js';
-import type { ITodoStorage } from '../../../core/interfaces/i-todo-storage.js';
-/**
- * Creates the read todos tool.
- *
- * Reads the current todo list from session storage.
- *
- * @param todoStorage - Storage service for retrieving todos
- * @returns Configured read todos tool
- */
-export declare function createReadTodosTool(todoStorage: ITodoStorage): Tool;

package/dist/agent/infra/tools/implementations/read-todos-tool.js

@@ -1,39 +0,0 @@
-import { z } from 'zod';
-import { ToolName } from '../../../core/domain/tools/constants.js';
-/**
- * Input schema for read todos tool.
- * No parameters required - reads todos for current session.
- */
-const ReadTodosInputSchema = z.object({}).strict();
-/**
- * Tool description for read todos.
- */
-const TOOL_DESCRIPTION = `Read the current todo list for this session.
-
-Use this tool to check the current state of your task list before making updates.
-Returns all todo items with their id, content, activeForm, and status.`;
-/**
- * Creates the read todos tool.
- *
- * Reads the current todo list from session storage.
- *
- * @param todoStorage - Storage service for retrieving todos
- * @returns Configured read todos tool
- */
-export function createReadTodosTool(todoStorage) {
-    return {
-        description: TOOL_DESCRIPTION,
-        async execute(_input, context) {
-            const sessionId = context?.sessionId ?? 'default';
-            const todos = await todoStorage.get(sessionId);
-            const incompleteCount = todos.filter((t) => t.status !== 'completed').length;
-            return {
-                content: JSON.stringify(todos, null, 2),
-                metadata: { todos },
-                title: `${incompleteCount} todos`,
-            };
-        },
-        id: ToolName.READ_TODOS,
-        inputSchema: ReadTodosInputSchema,
-    };
-}

package/dist/agent/infra/tools/implementations/search-history-tool.d.ts

@@ -1,10 +0,0 @@
-import type { Tool } from '../../../core/domain/tools/types.js';
-/**
- * Creates the search history tool.
- *
- * NOTE: This is a stub implementation. SearchService is not yet implemented.
- * This tool will throw an error until the SearchService is available.
- *
- * @returns Configured search history tool (stub)
- */
-export declare function createSearchHistoryTool(): Tool;

package/dist/agent/infra/tools/implementations/search-history-tool.js

@@ -1,36 +0,0 @@
-import { z } from 'zod';
-import { ToolName } from '../../../core/domain/tools/constants.js';
-/**
- * Input schema for search history tool.
- */
-const SearchHistoryInputSchema = z
-    .object({
-    limit: z.number().optional().default(20).describe('Maximum number of results to return (default: 20)'),
-    mode: z
-        .enum(['messages', 'sessions'])
-        .describe('Search mode: "messages" searches for individual messages, "sessions" finds sessions containing the query'),
-    offset: z.number().optional().default(0).describe('Offset for pagination (default: 0)'),
-    query: z.string().describe('The search query to find in conversation history'),
-    role: z.enum(['user', 'assistant', 'system', 'tool']).optional().describe('Filter by message role (optional)'),
-    sessionId: z.string().optional().describe('Limit search to a specific session (optional)'),
-})
-    .strict();
-/**
- * Creates the search history tool.
- *
- * NOTE: This is a stub implementation. SearchService is not yet implemented.
- * This tool will throw an error until the SearchService is available.
- *
- * @returns Configured search history tool (stub)
- */
-export function createSearchHistoryTool() {
-    return {
-        description: 'Search conversation history. Supports searching messages or sessions. Can filter by role and session.',
-        async execute(_input, _context) {
-            // Stub implementation - SearchService not yet available
-            throw new Error('Search history tool is not yet implemented. This feature requires the SearchService which is not currently available.');
-        },
-        id: ToolName.SEARCH_HISTORY,
-        inputSchema: SearchHistoryInputSchema,
-    };
-}

package/dist/agent/infra/tools/implementations/spec-analyze-tool.d.ts

@@ -1,7 +0,0 @@
-import type { Tool } from '../../../core/domain/tools/types.js';
-/**
- * Creates the detect domains tool.
- *
- * @returns Configured detect domains tool
- */
-export declare function createSpecAnalyzeTool(): Tool;