byterover-cli 1.8.0 → 2.1.0

package/dist/server/templates/skill/WORKFLOWS.md

@@ -1,229 +0,0 @@
-# ByteRover Workflows
-
-## Pattern 1: Research Before Implementation
-
-Use when starting new features or working in unfamiliar areas.
-
-**Workflow:**
-```
-Query existing knowledge → Implement following patterns → Curate new decisions
-```
-
-**Example: Adding a new API endpoint**
-
-```bash
-# 1. Query for existing patterns
-# Be SPECIFIC to get faster, more relevant results
-brv query "What middleware chain is used for authenticated API endpoints?"
-brv query "What is the standard error response format for API routes?"
-
-# 2. Implement following discovered patterns
-# ... write code ...
-
-# 3. Curate decisions made
-# Don't read the file first - let ByteRover read it via -f flag
-brv curate "Added /api/users/profile endpoint. Uses authMiddleware for JWT validation, returns UserProfileDTO. Error handling follows ApiError pattern" -f src/api/routes/users.ts
-```
-
-**Example: Implementing a new React component**
-
-```bash
-# 1. Query patterns - specific questions save time
-brv query "What data fetching hook pattern is used in list components?"
-brv query "Are CSS modules or styled-components used for component styling?"
-
-# 2. Implement
-# ... write component ...
-
-# 3. Curate with file reference - ByteRover reads the file
-brv curate "Created UserAvatar component. Uses React Query for data fetching, CSS modules for styling. Follows existing pattern in src/components/common/" -f src/components/UserAvatar.tsx
-```
-
-## Pattern 2: Debug and Document
-
-Use when fixing bugs to capture learnings and prevent recurrence.
-
-**Workflow:**
-```
-Query known issues → Debug and fix → Curate root cause and solution
-```
-
-**Example: Fixing a race condition**
-
-```bash
-# 1. Query for context - be specific about the symptom
-brv query "Are there known race condition patterns or AbortController usage in data fetching hooks?"
-
-# 2. Debug and fix
-# ... investigate, find root cause, implement fix ...
-
-# 3. Curate the learning with structured format
-brv curate "Bug: stale data after rapid navigation. Cause: useEffect cleanup not cancelling requests. Fix: AbortController with cleanup. Pattern: always abort fetch in useEffect cleanup" -f src/hooks/useUserData.ts
-```
-
-**Example: Fixing an authentication issue**
-
-```bash
-# 1. Specific query about the problem area
-brv query "How are credentials and cookies configured in the API client fetch calls?"
-
-# 2. Fix
-# ... debug and fix ...
-
-# 3. Curate with emphasis on the gotcha
-brv curate "Bug: unexpected logouts. Cause: fetch missing credentials option. Fix: added 'credentials: include' to fetch config. IMPORTANT: all API calls must include credentials for cookie-based auth" -f src/lib/api-client.ts
-```
-
-## Pattern 3: Multi-File Changes
-
-Use when changes span multiple files to maintain context.
-
-**Example: Adding a new feature across layers**
-
-```bash
-# 1. Query architecture - specific about the layers
-brv query "How are full-stack features organized across API routes, service layer, and React components?"
-
-# 2. Implement across files
-# ... write code ...
-
-# 3. Curate with multiple files (max 5)
-# Let ByteRover read all files - don't read them yourself first
-# Specify the topics you want created
-brv curate "Added user notifications feature. Create separate topics for: 1) API endpoint structure, 2) NotificationService business logic, 3) useNotifications React hook pattern, 4) NotificationBell UI component" -f src/api/notifications.ts -f src/services/NotificationService.ts -f src/hooks/useNotifications.ts -f src/components/NotificationBell.tsx
-```
-
-**Example: Database schema change with migrations**
-
-```bash
-# 1. Query migration patterns
-brv query "What is the migration naming convention and how are schema changes tested?"
-
-# 2. Implement
-# ... create migration, update models, update queries ...
-
-# 3. Multiple curates for different concerns - break down large context
-brv curate "Added user_preferences table with JSONB settings column. Migration: 20240115_add_user_preferences" -f migrations/20240115_add_user_preferences.ts
-
-brv curate "UserPreferences model with type-safe JSONB access. Includes validation for theme, notifications, locale settings" -f src/models/UserPreferences.ts
-
-brv curate "Updated UserService to load/save preferences. Uses transaction for atomic updates with user record" -f src/services/UserService.ts
-```
-
-## Pattern 4: Updating Existing Knowledge
-
-Use when changes make previous context outdated.
-
-**Example: Refactoring authentication system**
-
-```bash
-# 1. Query current documented state
-brv query "What is currently documented about authentication implementation and token handling?"
-
-# 2. Implement refactor
-# ... refactor code ...
-
-# 3. Curate with explicit cleanup signal
-# Tell ByteRover to clean up outdated context
-brv curate "OUTDATED: Previous auth used session cookies stored in Redis. NEW: Migrated to JWT with refresh tokens. Access token in memory (15min), refresh token in httpOnly cookie (7d). Remove/update any session-based auth context in the tree" -f src/auth/jwt.ts -f src/auth/refresh.ts
-```
-
-**Example: Replacing a library**
-
-```bash
-# 1. Query what's documented about the old library
-brv query "What patterns are documented for moment.js date handling?"
-
-# 2. Implement replacement
-# ... replace library usage ...
-
-# 3. Curate the replacement with cleanup signal
-brv curate "REPLACED: Removed moment.js (bloated, mutable). Now using date-fns (tree-shakeable, immutable). Clean up any moment.js context. New patterns: format(date, 'yyyy-MM-dd'), parseISO(string), differenceInDays(date1, date2)" -f src/utils/dates.ts
-```
-
-**Example: API versioning change**
-
-```bash
-# Curate with explicit version context
-brv curate "OUTDATED: API v1 endpoints deprecated. NEW: All endpoints now v2 with breaking changes. v2 uses camelCase response keys, pagination via cursor (not offset), errors include requestId. Update any v1 API context" -f src/api/v2/routes.ts
-```
-
-## Pattern 5: Comprehensive Documentation
-
-Use when documenting complex systems that need detailed breakdown.
-
-**Example: Documenting a payment module**
-
-```bash
-# Break into multiple curates - don't try to capture everything in one
-# Specify structure and detail level for each topic
-
-# Overview first
-brv curate "Payment module overview: Stripe integration with webhooks for subscription management. Create 4 separate detailed topics covering the full payment lifecycle" -f src/payments/
-
-# Topic 1 - detailed with line count guidance
-brv curate "Topic: Payment checkout flow. Cover: 1) cart validation, 2) createPaymentIntent call, 3) client-side confirmation, 4) success/failure handling. Include error scenarios. At least 50 lines of detailed documentation" -f src/payments/checkout.ts -f src/payments/intent.ts
-
-# Topic 2 - webhook handling
-brv curate "Topic: Stripe webhook handling. Cover: 1) signature verification with STRIPE_WEBHOOK_SECRET, 2) idempotency with processed_events table, 3) event types (payment_intent.succeeded, payment_intent.failed, customer.subscription.*). At least 40 lines" -f src/payments/webhooks.ts
-
-# Topic 3 - subscription management
-brv curate "Topic: Subscription lifecycle. Cover: trial period handling, upgrade/downgrade proration, cancellation with grace period, reactivation flow" -f src/payments/subscriptions.ts
-
-# Topic 4 - error handling
-brv curate "Topic: Payment error handling. Cover: StripeError types (CardError, InvalidRequestError, APIError), retry logic for transient failures, user-facing error messages mapping" -f src/payments/errors.ts
-```
-
-**Example: Documenting a state management system**
-
-```bash
-# Multiple focused curates instead of one massive one
-
-brv curate "State management overview: Using Zustand with persistence middleware. Create topics for: store structure, async actions, persistence, devtools integration" -f src/store/
-
-brv curate "Topic: Store structure. Separate stores per domain (userStore, cartStore, uiStore). Each store follows pattern: state interface, actions, selectors. No cross-store dependencies" -f src/store/userStore.ts -f src/store/cartStore.ts
-
-brv curate "Topic: Async actions. Pattern: set loading -> try/catch -> set data/error -> clear loading. All API calls go through apiClient. Optimistic updates for cart operations" -f src/store/cartStore.ts -f src/store/actions/
-
-brv curate "Topic: Persistence. userStore persisted to localStorage (excluding sensitive data). cartStore persisted to sessionStorage. Custom serializer excludes functions and timestamps" -f src/store/middleware/persist.ts
-```
-
-## Pattern 6: Exploratory Documentation
-
-Use when you need to document an unfamiliar codebase area.
-
-**Example: Understanding and documenting an existing module**
-
-```bash
-# 1. Query what's already known
-brv query "What is documented about the notification system and real-time updates?"
-
-# 2. Explore the code (agent reads files to understand)
-# ... read and understand the code ...
-
-# 3. Curate in chunks as you understand different parts
-# First curate: high-level architecture
-brv curate "Notification system uses WebSocket for real-time delivery with Redis pub/sub for horizontal scaling. Three components: NotificationService (creation/storage), NotificationGateway (WebSocket), NotificationWorker (background processing)" -f src/notifications/
-
-# Second curate: specific implementation detail
-brv curate "WebSocket authentication: JWT token passed in connection query params, validated on connect, stored in socket.data. Rooms: user_{id} for personal, team_{id} for team broadcasts" -f src/notifications/NotificationGateway.ts
-
-# Third curate: gotchas discovered
-brv curate "Notification gotchas: 1) Must call gateway.joinRoom after auth, 2) Unread count cached in Redis (5min TTL) - call invalidateUnreadCount after marking read, 3) Batch notifications throttled to max 10/second per user" -f src/notifications/NotificationService.ts
-```
-
-## What to Curate
-
-**Do curate:**
-- Architecture decisions: "Chose Redis for sessions because of horizontal scaling"
-- Patterns: "All forms use react-hook-form with zod. Pattern in LoginForm.tsx"
-- Non-obvious conventions: "File uploads go to /tmp first, then S3 after validation"
-- Bug root causes: "Memory leak from event listeners not removed on unmount"
-- Gotchas: "PostgreSQL JSONB queries need explicit casting for arrays"
-- Replacements: "OUTDATED: X, NEW: Y" when refactoring
-
-**Don't curate:**
-- Obvious facts: "Uses TypeScript", "Has a README"
-- Temporary states: "Currently debugging X"
-- Personal preferences: "I prefer tabs"
-- Trivial changes: "Fixed typo in comment"

package/dist/server/utils/environment-detector.d.ts

@@ -1,20 +0,0 @@
-/**
- * Check if running in WSL environment (cached).
- * Detects both WSL1 and WSL2. Result is cached after first call for performance.
- */
-export declare function isWsl(): boolean;
-/**
- * Check if running in headless Linux environment (cached).
- * Result is cached after first call for performance.
- */
-export declare function isHeadlessLinux(): boolean;
-/**
- * Determine if file-based token storage should be used.
- * Returns true for WSL or headless Linux environments where keychain is unavailable.
- */
-export declare function shouldUseFileTokenStore(): boolean;
-/**
- * Reset cached values (for testing only).
- * @internal
- */
-export declare function _resetCaches(): void;

package/dist/server/utils/environment-detector.js

@@ -1,92 +0,0 @@
-import { existsSync, readFileSync } from 'node:fs';
-let wslCached;
-let headlessLinuxCached;
-/**
- * Detect if running in WSL (Windows Subsystem for Linux) environment.
- * Checks WSL-specific environment variables first, then falls back to /proc/version.
- */
-function detectWsl() {
-    if (process.platform !== 'linux') {
-        return false;
-    }
-    if (process.env.WSL_DISTRO_NAME !== undefined || process.env.WSLENV !== undefined) {
-        return true;
-    }
-    try {
-        const version = readFileSync('/proc/version', 'utf8');
-        return /microsoft|wsl/i.test(version);
-    }
-    catch {
-        return false;
-    }
-}
-/**
- * Check if running in WSL environment (cached).
- * Detects both WSL1 and WSL2. Result is cached after first call for performance.
- */
-export function isWsl() {
-    if (wslCached === undefined) {
-        wslCached = detectWsl();
-    }
-    return wslCached;
-}
-/**
- * Detect if running in a headless Linux environment where keychain is unavailable.
- *
- * Checks for:
- * - SSH session (SSH_TTY, SSH_CONNECTION)
- * - No display server (DISPLAY, WAYLAND_DISPLAY not set)
- * - No D-Bus session (required for most Linux keyrings)
- * - Running in container (/.dockerenv)
- */
-function detectHeadlessLinux() {
-    if (process.platform !== 'linux') {
-        return false;
-    }
-    // WSL is handled separately
-    if (isWsl()) {
-        return false;
-    }
-    // SSH session
-    if (process.env.SSH_TTY !== undefined || process.env.SSH_CONNECTION !== undefined) {
-        return true;
-    }
-    // No display server (X11 or Wayland)
-    if (process.env.DISPLAY === undefined && process.env.WAYLAND_DISPLAY === undefined) {
-        return true;
-    }
-    // No D-Bus session (required for gnome-keyring, KWallet)
-    if (process.env.DBUS_SESSION_BUS_ADDRESS === undefined) {
-        return true;
-    }
-    // Docker container
-    if (existsSync('/.dockerenv')) {
-        return true;
-    }
-    return false;
-}
-/**
- * Check if running in headless Linux environment (cached).
- * Result is cached after first call for performance.
- */
-export function isHeadlessLinux() {
-    if (headlessLinuxCached === undefined) {
-        headlessLinuxCached = detectHeadlessLinux();
-    }
-    return headlessLinuxCached;
-}
-/**
- * Determine if file-based token storage should be used.
- * Returns true for WSL or headless Linux environments where keychain is unavailable.
- */
-export function shouldUseFileTokenStore() {
-    return isWsl() || isHeadlessLinux();
-}
-/**
- * Reset cached values (for testing only).
- * @internal
- */
-export function _resetCaches() {
-    wslCached = undefined;
-    headlessLinuxCached = undefined;
-}

package/dist/tui/app.d.ts

@@ -1,9 +0,0 @@
-/**
- * TUI App - Main Layout
- *
- * Two main states:
- * - Unauthorized: Show login prompt
- * - Authorized: Show main app with tabs
- */
-import React from 'react';
-export declare const App: React.FC;

package/dist/tui/app.js

@@ -1,28 +0,0 @@
-import { jsx as _jsx, Fragment as _Fragment, jsxs as _jsxs } from "react/jsx-runtime";
-/**
- * TUI App - Main Layout
- *
- * Two main states:
- * - Unauthorized: Show login prompt
- * - Authorized: Show main app with tabs
- */
-import { Box } from 'ink';
-import { useEffect } from 'react';
-import { Footer, Header } from './components/index.js';
-import { useAuth, useServices } from './contexts/index.js';
-import { useTerminalBreakpoint, useUIHeights } from './hooks/index.js';
-import { LoginView } from './views/index.js';
-import { MainView } from './views/main-view.js';
-export const App = () => {
-    const { columns: terminalWidth, rows: terminalHeight } = useTerminalBreakpoint();
-    const { appBottomPadding, footer, header } = useUIHeights();
-    const { connectorManager } = useServices();
-    const { isAuthorized } = useAuth();
-    const contentHeight = Math.max(1, terminalHeight - header - footer);
-    useEffect(() => {
-        // Clean up orphaned connectors from agents that no longer support them.
-        // Runs in the background to avoid blocking REPL startup.
-        connectorManager.migrateOrphanedConnectors().catch(console.error);
-    }, []);
-    return (_jsxs(Box, { flexDirection: "column", height: terminalHeight, paddingBottom: appBottomPadding, width: terminalWidth, children: [_jsx(Box, { flexShrink: 0, children: _jsx(Header, { compact: isAuthorized }) }), isAuthorized ? (_jsxs(_Fragment, { children: [_jsx(MainView, { availableHeight: contentHeight }), _jsx(Box, { flexShrink: 0, children: _jsx(Footer, {}) })] })) : (_jsx(Box, { flexGrow: 1, paddingX: 1, children: _jsx(LoginView, {}) }))] }));
-};

package/dist/tui/commands/arg-parser.d.ts

@@ -1,102 +0,0 @@
-/**
- * Shared argument parser for REPL commands
- *
- * Combines shell-like string splitting with oclif's Parser for consistent
- * flag and argument handling across REPL commands.
- */
-import { type Interfaces } from '@oclif/core';
-import { CommandFlag } from '../types.js';
-export { Args, Flags } from '@oclif/core';
-type ArgInput = Interfaces.ArgInput;
-type FlagInput = Interfaces.FlagInput;
-/**
- * Convert oclif flag definitions to CommandFlag[] for SlashCommand.flags
- *
- * This allows defining flags once using oclif format and auto-generating
- * the CommandFlag[] needed for help display.
- *
- * @example
- * const flags = {
- *   apiKey: Flags.string({char: 'k', description: 'API key'}),
- *   verbose: Flags.boolean({char: 'v', description: 'Verbose output'}),
- * }
- *
- * export const myCommand: SlashCommand = {
- *   action(context, args) {
- *     const parsed = await parseReplArgs(args, {flags})
- *   },
- *   flags: toCommandFlags(flags),
- * }
- */
-export declare function toCommandFlags(flags: FlagInput): CommandFlag[];
-/**
- * Result from splitArgs with file and folder references
- */
-export interface SplitArgsResult {
-    /** Regular arguments */
-    args: string[];
-    /** File references (tokens starting with @ that point to files) */
-    files: string[];
-    /** Folder references (tokens starting with @ that point to directories) */
-    folders: string[];
-}
-/**
- * Split a string into args array, respecting quoted strings
- * Handles both single and double quotes, and extracts @file and @folder references
- *
- * @example
- * splitArgs('"hello world" --force') // { args: ['hello world', '--force'], files: [], folders: [] }
- * splitArgs("'hello world' -f") // { args: ['hello world', '-f'], files: [], folders: [] }
- * splitArgs('query @src/file.ts') // { args: ['query'], files: ['src/file.ts'], folders: [] }
- * splitArgs('"context" @src/') // { args: ['context'], files: [], folders: ['src/'] }
- * splitArgs('text @src/ @README.md') // { args: ['text'], files: ['README.md'], folders: ['src/'] }
- */
-export declare function splitArgs(input: string): SplitArgsResult;
-/**
- * Parse result from parseReplArgs
- */
-export interface ParsedReplArgs<TFlags extends FlagInput, TArgs extends ArgInput> {
-    /** Parsed arguments */
-    args: {
-        [K in keyof TArgs]: TArgs[K] extends {
-            required: true;
-        } ? string : string | undefined;
-    };
-    /** Remaining unparsed arguments (when strict: false) */
-    argv: string[];
-    /** File references extracted from @filepath tokens (non-directory paths) */
-    files: string[];
-    /** Parsed flags */
-    flags: {
-        [K in keyof TFlags]: TFlags[K] extends {
-            type: 'boolean';
-        } ? boolean : string | undefined;
-    };
-    /** Folder references extracted from @folderpath tokens (directory paths) */
-    folders: string[];
-}
-/**
- * Parse REPL command arguments using oclif's Parser
- *
- * @param input - Raw input string from REPL (e.g., '"hello world" --force @src/file.ts')
- * @param options - Parser options
- * @param options.args - Argument definitions using Args from @oclif/core
- * @param options.flags - Flag definitions using Flags from @oclif/core
- * @param options.strict - Whether to error on unknown flags (default: false)
- * @returns Parsed flags, args, remaining argv, and file references
- *
- * @example
- * const result = await parseReplArgs('query text --verbose @src/auth.ts', {
- *   args: { query: Args.string({ required: true }) },
- *   flags: { verbose: Flags.boolean({ char: 'v' }) },
- * })
- * // result.args.query === 'query'
- * // result.flags.verbose === true
- * // result.argv === ['query', 'text']
- * // result.files === ['src/auth.ts']
- */
-export declare function parseReplArgs<TFlags extends FlagInput, TArgs extends ArgInput>(input: string, options: {
-    args?: TArgs;
-    flags?: TFlags;
-    strict?: boolean;
-}): Promise<ParsedReplArgs<TFlags, TArgs>>;

package/dist/tui/commands/connectors-command.d.ts

@@ -1,8 +0,0 @@
-import { SlashCommand } from '../types.js';
-/**
- * Connectors command
- *
- * Manages connectors (rules, hook) for integrating BRV with coding agents.
- * Lists connected agents and allows managing or adding new connections.
- */
-export declare const connectorsCommand: SlashCommand;

package/dist/tui/commands/connectors-command.js

@@ -1,49 +0,0 @@
-import { ConnectorManager } from '../../server/infra/connectors/connector-manager.js';
-import { RuleTemplateService } from '../../server/infra/connectors/shared/template-service.js';
-import { FsFileService } from '../../server/infra/file/fs-file-service.js';
-import { FileGlobalConfigStore } from '../../server/infra/storage/file-global-config-store.js';
-import { createTokenStore } from '../../server/infra/storage/token-store.js';
-import { FsTemplateLoader } from '../../server/infra/template/fs-template-loader.js';
-import { ReplTerminal } from '../../server/infra/terminal/repl-terminal.js';
-import { MixpanelTrackingService } from '../../server/infra/tracking/mixpanel-tracking-service.js';
-import { ConnectorsUseCase } from '../../server/infra/usecase/connectors-use-case.js';
-import { CommandKind } from '../types.js';
-/**
- * Connectors command
- *
- * Manages connectors (rules, hook) for integrating BRV with coding agents.
- * Lists connected agents and allows managing or adding new connections.
- */
-export const connectorsCommand = {
-    action: () => ({
-        async execute(onMessage, onPrompt) {
-            // Create ReplTerminal with callbacks
-            const terminal = new ReplTerminal({ onMessage, onPrompt });
-            // Create services
-            const fileService = new FsFileService();
-            const templateLoader = new FsTemplateLoader(fileService);
-            const templateService = new RuleTemplateService(templateLoader);
-            const globalConfigStore = new FileGlobalConfigStore();
-            const trackingService = new MixpanelTrackingService({ globalConfigStore, tokenStore: createTokenStore() });
-            // Create ConnectorManager
-            const connectorManager = new ConnectorManager({
-                fileService,
-                projectRoot: process.cwd(),
-                templateService,
-            });
-            // Create and run UseCase
-            const useCase = new ConnectorsUseCase({
-                connectorManager,
-                terminal,
-                trackingService,
-            });
-            await useCase.run();
-        },
-        type: 'streaming',
-    }),
-    aliases: ['connectors'],
-    autoExecute: true,
-    description: 'Manage agent connectors (rules, hook, mcp, or skill)',
-    kind: CommandKind.BUILT_IN,
-    name: 'connector',
-};

package/dist/tui/commands/curate-command.d.ts

@@ -1,9 +0,0 @@
-import { SlashCommand } from '../types.js';
-/**
- * Curate command - Curate context to the context tree
- *
- * Supports both modes:
- * - Autonomous mode: /curate "your context" @file1 @file2
- * - Interactive mode: /curate (no args) - navigates context tree
- */
-export declare const curateCommand: SlashCommand;

package/dist/tui/commands/curate-command.js

@@ -1,80 +0,0 @@
-import { isDevelopment } from '../../server/config/environment.js';
-import { FileGlobalConfigStore } from '../../server/infra/storage/file-global-config-store.js';
-import { createTokenStore } from '../../server/infra/storage/token-store.js';
-import { ReplTerminal } from '../../server/infra/terminal/repl-terminal.js';
-import { MixpanelTrackingService } from '../../server/infra/tracking/mixpanel-tracking-service.js';
-import { CurateUseCase } from '../../server/infra/usecase/curate-use-case.js';
-import { CommandKind } from '../types.js';
-import { Flags, parseReplArgs, toCommandFlags } from './arg-parser.js';
-// Dev-only flags - defined once, used for both parsing and help display
-const devFlags = {
-    apiKey: Flags.string({ char: 'k', description: 'OpenRouter API key [Dev only]' }),
-    model: Flags.string({ char: 'm', description: 'Model to use [Dev only]' }),
-    verbose: Flags.boolean({ char: 'v', description: 'Enable verbose debug output [Dev only]' }),
-};
-/**
- * Curate command - Curate context to the context tree
- *
- * Supports both modes:
- * - Autonomous mode: /curate "your context" @file1 @file2
- * - Interactive mode: /curate (no args) - navigates context tree
- */
-export const curateCommand = {
-    action(context, args) {
-        return {
-            async execute(onMessage, onPrompt) {
-                // Files and folders are pre-extracted by the command processor
-                const files = context.invocation?.files ?? [];
-                const folders = context.invocation?.folders ?? [];
-                // Parse flags and get context text
-                let contextText;
-                let flags = {};
-                if (isDevelopment()) {
-                    const parsed = await parseReplArgs(args, { flags: devFlags, strict: false });
-                    contextText = parsed.argv.join(' ') || undefined;
-                    flags = parsed.flags;
-                }
-                else {
-                    contextText = args || undefined;
-                }
-                const terminal = new ReplTerminal({ onMessage, onPrompt });
-                const tokenStore = createTokenStore();
-                const globalConfigStore = new FileGlobalConfigStore();
-                const useCase = new CurateUseCase({
-                    terminal,
-                    trackingService: new MixpanelTrackingService({ globalConfigStore, tokenStore }),
-                });
-                // Run the use case - mode determined by whether context is provided
-                // Folder takes precedence over files (triggers folder pack flow)
-                await useCase.run({
-                    context: contextText,
-                    files: files.length > 0 ? files : undefined,
-                    folders: folders.length > 0 ? folders : undefined,
-                    verbose: flags.verbose,
-                });
-            },
-            type: 'streaming',
-        };
-    },
-    aliases: [],
-    args: [
-        {
-            description: 'Knowledge context (optional, triggers autonomous mode)',
-            name: 'context',
-            required: false,
-        },
-    ],
-    autoExecute: true,
-    description: 'Curate context to the context tree.',
-    flags: [
-        {
-            char: '@',
-            description: 'Include files (type @ to browse, max 5)',
-            name: 'file',
-            type: 'file',
-        },
-        ...(isDevelopment() ? toCommandFlags(devFlags) : []),
-    ],
-    kind: CommandKind.BUILT_IN,
-    name: 'curate',
-};

package/dist/tui/commands/index.d.ts

@@ -1,8 +0,0 @@
-import { SlashCommand } from '../types.js';
-/**
- * Load all REPL slash commands.
- *
- * IMPORTANT: Order matters - commands are displayed in the UI suggestions
- * in the same order as defined here. Keep grouped by priority/category.
- */
-export declare const load: () => SlashCommand[];