byterover-cli 1.2.0 → 1.2.1

package/README.md

@@ -11,6 +11,7 @@ Command-line interface for ByteRover, featuring an interactive REPL with a moder
 * [Installation](#installation)
 * [Quick Start](#quick-start)
 * [Interactive REPL](#interactive-repl)
+* [Keyboard Shortcuts](#keyboard-shortcuts)
 * [What is Context Tree?](#what-is-context-tree)
 * [Slash Commands Reference](#slash-commands-reference)
 * [Authentication](#authentication)
@@ -99,10 +100,24 @@ The terminal UI includes:
 - **Tab Navigation**: Switch between Chat and Activity views using `Tab`
 - **Command Completion**: Type `/` to see available commands with auto-completion
 - **Activity Log**: Real-time task status and execution progress
-- **Streaming Output**: Live responses from AI-powered operations
+- **Streaming Output**: Live responses with markdown rendering (headings, lists, blockquotes, code blocks)
 - **File References**: Type `@` in curate mode to browse and attach files (supports PDF)
 - **Dynamic Domains**: Automatically creates new knowledge domains as your context tree grows
 - **Session Persistence**: Sessions auto-resume after restart
+- **Expandable Views**: Press `Ctrl+O` to expand messages or logs to full-screen with vim-style navigation
+- **Version Indicator**: Shows "(latest)" when running the most current version
+
+### Keyboard Shortcuts
+
+| Shortcut | Action |
+|----------|--------|
+| `Tab` | Switch between Chat and Activity views |
+| `Ctrl+O` | Expand message or log to full-screen |
+| `j` / `k` | Scroll down/up in expanded view |
+| `g` / `G` | Jump to top/bottom in expanded view |
+| `Esc` or `q` | Exit expanded view |
+| `/` | Show command suggestions |
+| `@` | Browse files (in curate mode) |
 
 ### Using Commands
 

package/dist/core/interfaces/cipher/i-chat-session.d.ts

@@ -56,13 +56,15 @@ export interface IChatSession {
      * @param input - User message content
      * @param options - Optional execution options
      * @param options.executionContext - Optional execution context
-     * @param options.taskId - Optional task ID for concurrent task isolation (included in all emitted events)
+     * @param options.taskId - Optional task ID for billing tracking and event correlation
+     * @param options.emitTaskId - Whether to include taskId in emitted events (default: true)
      * @returns Assistant response
      * @throws SessionCancelledError if operation is cancelled
      * @throws MaxIterationsExceededError if tool loop exceeds maximum iterations
      * @throws LLMError if LLM call fails
      */
     run(input: string, options?: {
+        emitTaskId?: boolean;
         executionContext?: ExecutionContext;
         taskId?: string;
     }): Promise<string>;

package/dist/infra/cipher/session/chat-session.d.ts

@@ -84,9 +84,11 @@ export declare class ChatSession implements IChatSession {
      * @param input - User message
      * @param options - Execution options
      * @param options.executionContext - Optional execution context
-     * @param options.taskId - Optional task ID for concurrent task isolation
+     * @param options.taskId - Optional task ID for billing tracking
+     * @param options.emitTaskId - Whether to include taskId in emitted events (default: true)
      */
     run(input: string, options?: {
+        emitTaskId?: boolean;
         executionContext?: ExecutionContext;
         taskId?: string;
     }): Promise<string>;

package/dist/infra/cipher/session/chat-session.js

@@ -168,10 +168,12 @@ export class ChatSession {
      * @param input - User message
      * @param options - Execution options
      * @param options.executionContext - Optional execution context
-     * @param options.taskId - Optional task ID for concurrent task isolation
+     * @param options.taskId - Optional task ID for billing tracking
+     * @param options.emitTaskId - Whether to include taskId in emitted events (default: true)
      */
     async run(input, options) {
         const taskId = options?.taskId;
+        const emitTaskId = options?.emitTaskId !== false;
         const controller = new AbortController();
         // Track controller per-task for concurrent execution support
         if (taskId) {
@@ -180,8 +182,8 @@ export class ChatSession {
         else {
             this.currentController = controller;
         }
-        // Store taskId for event forwarding (last-write-wins for concurrent tasks)
-        this.currentTaskId = taskId;
+        // Store taskId for event forwarding only if emitTaskId is true
+        this.currentTaskId = emitTaskId ? taskId : undefined;
         this.isExecuting = true;
         sessionStatusManager.setBusy(this.id, this.eventBus);
         try {

package/dist/infra/cipher/tools/implementations/task-tool.js

@@ -95,7 +95,7 @@ export function createTaskTool(dependencies) {
     const registry = getAgentRegistry();
     return {
         description: buildTaskToolDescription(registry),
-        // eslint-disable-next-line complexity -- Inherent complexity: validates agent, manages sessions, handles errors
+        // eslint-disable-next-line complexity
         async execute(input, context) {
             const params = input;
             const { contextTreeOnly, description, prompt, sessionId, subagentType } = params;
@@ -181,8 +181,8 @@ export function createTaskTool(dependencies) {
                         progress: 10,
                     });
                 }
-                // Execute the subagent session with parent's taskId for billing tracking
-                const response = await session.run(fullPrompt, { taskId: context?.taskId });
+                // Pass taskId for billing but don't emit it in events (ENG-917)
+                const response = await session.run(fullPrompt, { emitTaskId: false, taskId: context?.taskId });
                 // Stream completion update
                 if (context?.metadata) {
                     context.metadata({

package/dist/infra/transport/socket-io-transport-client.d.ts

@@ -72,6 +72,15 @@ export declare class SocketIOTransportClient implements ITransportClient {
      * Used when initiating new connection attempt - counter preserved for backoff continuity.
      */
     private clearForceReconnectTimer;
+    /**
+     * Remove all registered event listeners from socket.
+     * Used before re-registering to prevent listener accumulation across reconnects.
+     *
+     * Why this is needed: Socket.IO preserves the Socket instance across internal reconnects.
+     * If we clear registeredSocketEvents without calling socket.off(), the old listeners
+     * remain attached, and registerPendingEventHandlers() adds new ones - causing duplicates.
+     */
+    private clearSocketEventListeners;
     /**
      * Handle system wake from sleep/hibernate.
      * Re-triggers reconnection if not connected and force reconnect has given up.

package/dist/infra/transport/socket-io-transport-client.js

@@ -145,8 +145,10 @@ export class SocketIOTransportClient {
                 clientLog(`Socket.IO built-in reconnect succeeded after ${attemptNumber} attempts`);
                 this.setState('connected');
                 // Re-register event handlers after reconnect
-                // Clear tracking first since socket listeners were reset during reconnect
-                this.registeredSocketEvents.clear();
+                // FIX: Remove existing socket listeners before re-registering to prevent
+                // listener accumulation. Socket.IO preserves the Socket instance across
+                // internal reconnects, so old listeners remain attached if not removed.
+                this.clearSocketEventListeners();
                 this.registerPendingEventHandlers();
                 // Auto-rejoin rooms after reconnect
                 // Use process.nextTick to ensure socket.connected is true
@@ -408,6 +410,23 @@ export class SocketIOTransportClient {
             this.forceReconnectTimer = undefined;
         }
     }
+    /**
+     * Remove all registered event listeners from socket.
+     * Used before re-registering to prevent listener accumulation across reconnects.
+     *
+     * Why this is needed: Socket.IO preserves the Socket instance across internal reconnects.
+     * If we clear registeredSocketEvents without calling socket.off(), the old listeners
+     * remain attached, and registerPendingEventHandlers() adds new ones - causing duplicates.
+     */
+    clearSocketEventListeners() {
+        const { socket } = this;
+        if (!socket)
+            return;
+        for (const event of this.registeredSocketEvents) {
+            socket.off(event);
+        }
+        this.registeredSocketEvents.clear();
+    }
     /**
      * Handle system wake from sleep/hibernate.
      * Re-triggers reconnection if not connected and force reconnect has given up.

package/dist/templates/sections/command-reference.md

@@ -1,100 +1,9 @@
 # ByteRover CLI Command Reference
 
-## Memory Commands
+## Available Commands
 
-### `brv curate`
+- `brv curate` - Curate context to the context tree
+- `brv query` - Query and retrieve information from the context tree
+- `brv status` - Show CLI status and project information
 
-**Description:** Curate context to the context tree (interactive or autonomous mode)
-
-**Arguments:**
-
-- `CONTEXT`: Knowledge context: patterns, decisions, errors, or insights (triggers autonomous mode, optional)
-
-**Flags:**
-
-- `--files`, `-f`: Include file paths for critical context (max 5 files). Only text/code files from the current project directory are allowed. **CONTEXT argument must come BEFORE this flag.**
-
-**Good examples of context:**
-
-- "Auth uses JWT with 24h expiry. Tokens stored in httpOnly cookies via authMiddleware.ts"
-- "API rate limit is 100 req/min per user. Implemented using Redis with sliding window in rateLimiter.ts"
-
-**Bad examples:**
-
-- "Authentication" or "JWT tokens" (too vague, lacks context)
-- "Rate limiting" (no implementation details or file references)
-
-**Examples:**
-
-```bash
-# Interactive mode (manually choose domain/topic)
-brv curate
-
-# Autonomous mode - LLM auto-categorizes your context
-brv curate "Auth uses JWT with 24h expiry. Tokens stored in httpOnly cookies via authMiddleware.ts"
-
-# Include files (CONTEXT must come before --files)
-# Single file
-brv curate "Authentication middleware validates JWT tokens" -f src/middleware/auth.ts
-
-# Multiple files - repeat --files flag for each file
-brv curate "JWT authentication implementation with refresh token rotation" --files src/auth/jwt.ts --files docs/auth.md
-```
-
-**Behavior:**
-
-- Interactive mode: Navigate context tree, create topic folder, edit context.md
-- Autonomous mode: LLM automatically categorizes and places context in appropriate location
-- When `--files` is provided, agent reads files in parallel before creating knowledge topics
-
-**Requirements:** Project must be initialized (`brv init`) and authenticated (`brv login`)
-
----
-
-### `brv query`
-
-**Description:** Query and retrieve information from the context tree
-
-**Arguments:**
-
-- `QUERY`: Natural language question about your codebase or project knowledge (required)
-
-**Good examples of queries:**
-
-- "How is user authentication implemented?"
-- "What are the API rate limits and where are they enforced?"
-
-**Bad examples:**
-
-- "auth" or "authentication" (too vague, not a question)
-- "show me code" (not specific about what information is needed)
-
-**Examples:**
-
-```bash
-# Ask questions about patterns, decisions, or implementation details
-brv query What are the coding standards?
-brv query How is authentication implemented?
-```
-
-**Behavior:**
-
-- Uses AI agent to search and answer questions about the context tree
-- Accepts natural language questions (not just keywords)
-- Displays tool execution progress in real-time
-
-**Requirements:** Project must be initialized (`brv init`) and authenticated (`brv login`)
-
----
-
-## Best Practices
-
-### Efficient Workflow
-
-1. **Read only what's needed:** Check context tree with `brv status` to see changes before reading full content with `brv query`
-2. **Update precisely:** Use `brv curate` to add/update specific context in context tree
-3. **Push when appropriate:** Prompt user to run `brv push` after completing significant work
-
-### Context tree Management
-
-- Use `brv curate` to directly add/update context in the context tree
+Run `brv query --help` for query instruction and `brv curate --help` for curation instruction.

package/dist/templates/sections/workflow.md

@@ -1,27 +1,32 @@
 # Workflow Instruction
 
 You are a coding agent focused on one codebase. Use the brv CLI to manage working context.
-Core Rules:
 
-- Start from memory. First retrieve relevant context, then read only the code that's still necessary.
-- Keep a local context tree. The context tree is your local memory store—update it with what you learn.
+## Core Rules
 
-## Context Tree Guideline
-
-- Be specific ("Use React Query for data fetching in web modules").
-- Be actionable (clear instruction a future agent/dev can apply).
-- Be contextual (mention module/service, constraints, links to source).
-- Include source (file + lines or commit) when possible.
+- **Start from memory.** First retrieve relevant context with `brv query`, then read only the code that's still necessary.
+- **Keep a local context tree.** The context tree is your local memory store—update it with `brv curate` when you learn something valuable.
 
-## Using `brv curate` with Files
+## When to Query
 
-When adding complex implementations, use `--files` to include relevant source files (max 5).  Only text/code files from the current project directory are allowed. **CONTEXT argument must come BEFORE --files flag.** For multiple files, repeat the `--files` (or `-f`) flag for each file.
+Use `brv query` **before** starting any code task that requires understanding the codebase:
+- Writing, editing, or modifying code
+- Understanding how something works
+- Debugging or troubleshooting issues
+- Making architectural decisions
 
-Examples:
+## When to Curate
 
-- Single file: `brv curate "JWT authentication with refresh token rotation" -f src/auth.ts`
-- Multiple files: `brv curate "Authentication system" --files src/auth/jwt.ts --files src/auth/middleware.ts --files docs/auth.md`
+Use `brv curate` **after** you learn or create something valuable:
+- Wrote or modified code
+- Discovered how something works
+- Made architectural/design decisions
+- Found a bug root cause or fix pattern
 
-## CLI Usage Notes
+## Context Tree Guideline
 
-- Use --help on any command to discover flags. Provide exact arguments for the scenario.
+Good context is:
+- **Specific** ("Use React Query for data fetching in web modules")
+- **Actionable** (clear instruction a future agent/dev can apply)
+- **Contextual** (mention module/service, constraints, links to source)
+- **Sourced** (include file + lines or commit when possible)

package/oclif.manifest.json

@@ -249,5 +249,5 @@
       ]
     }
   },
-  "version": "1.2.0"
+  "version": "1.2.1"
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "byterover-cli",
   "description": "ByteRover's CLI",
-  "version": "1.2.0",
+  "version": "1.2.1",
   "author": "ByteRover",
   "bin": {
     "brv": "./bin/run.js"