lonny-agent 0.1.9 → 0.2.2

package/src/web/public/app.js

@@ -14,6 +14,7 @@
   const tokenCalls = document.getElementById('token-calls')
   const balanceDisplay = document.getElementById('balance-display')
   const balanceSep = document.getElementById('balance-sep')
+  const cwdDisplay = document.getElementById('cwd-display')
   const connectionOverlay = document.getElementById('connection-overlay')
   const chatContainer = document.getElementById('chat-container')
 
@@ -591,6 +592,12 @@
           balanceDisplay.style.display = 'none'
           balanceSep.style.display = 'none'
         }
+        // Show working directory
+        if (msg.cwd) {
+          const maxLen = 35
+          cwdDisplay.textContent =
+            msg.cwd.length > maxLen ? '...' + msg.cwd.slice(-maxLen) : msg.cwd
+        }
         break
 
       case 'chunk':
@@ -677,6 +684,8 @@
 
       case 'session_history':
         renderSessionHistory(msg.messages)
+        // Scroll to bottom after all messages are rendered
+        setTimeout(scrollToBottom, 50)
         break
 
       case 'plan_data':

package/src/web/public/index.html

@@ -16,6 +16,8 @@
       <span id="status-indicator" class="status-idle">○ idle</span>
       <span class="separator">|</span>
       <span id="mode-display" class="mode-badge">code</span>
+      <span class="separator">|</span>
+      <span id="cwd-display" class="cwd-text"></span>
     </div>
     <div class="status-right">
       <span id="model-display" class="model-name">loading...</span>
@@ -51,6 +53,10 @@
               <div class="slash-hint-item" data-cmd="mode code|plan|ask">/mode <span class="hint-arg">code|plan|ask</span> <span class="hint-desc">Switch mode</span></div>
               <div class="slash-hint-item" data-cmd="model ">/model <span class="hint-arg">&lt;name&gt;</span> <span class="hint-desc">Switch model</span></div>
               <div class="slash-hint-item" data-cmd="new">/new <span class="hint-desc">Start a new session</span></div>
+              <div class="slash-hint-item" data-cmd="stop">/stop <span class="hint-desc">Stop the running agent</span></div>
+              <div class="slash-hint-item" data-cmd="skills">/skills <span class="hint-desc">List active skills</span></div>
+              <div class="slash-hint-item" data-cmd="prompts">/prompts <span class="hint-desc">List prompt templates</span></div>
+              <div class="slash-hint-item" data-cmd="init">/init <span class="hint-desc">Create .lonny/skills/ &amp; prompts/</span></div>
               <div class="slash-hint-item" data-cmd="help">/help <span class="hint-desc">Show this help</span></div>
             </div>
             <textarea id="chat-input" rows="3" placeholder="Type a message... (type / for commands)"></textarea>

package/src/web/public/style.css

@@ -89,6 +89,17 @@ html, body {
   gap: 2px;
 }
 
+.cwd-text {
+  color: var(--text-dim);
+  font-size: 12px;
+  max-width: 300px;
+  overflow: hidden;
+  text-overflow: ellipsis;
+  white-space: nowrap;
+  vertical-align: middle;
+  font-family: var(--font-mono);
+}
+
 /* ── Chat Container ──────────────────────────────────────────── */
 #chat-container {
   flex: 1;

package/.lonny/fix-new-command-session-cleanup.md

@@ -1,65 +0,0 @@
-# Plan: Fix /new Command Session Cleanup Issues
-
-## Analysis
-
-Reviewing `src/tui/index.ts` lines 485-496, the `/new` command has two issues:
-
-### Issue 1: No `session.stop()` when agent is running
-
-The slash command handler intentionally allows all commands even when `isRunning === true` (see comment on line 471: "Allow slash commands even when agent is running (critical for /stop)"). However, `/new` creates a **new** `Session` object while the **old** session's `session.chat()` promise may still be in-flight:
-
-- The old session continues consuming API tokens via its pending LLM stream
-- When the old `chat()` promise resolves, it writes to `chatContent` via the `output.write` closure — but `chatContent` was just cleared by `/new`, causing stale output to pollute the fresh chat display
-- The old promise's `.then()` callback sets `isRunning = false` and calls `updateFooter()` etc. (harmless but messy)
-
-### Issue 2: Editor internal state not fully reset
-
-`editor.setText('')` (called at line 468 before the slash command handler) resets the text, cursor, and `scrollOffset`. But it does NOT clear:
-
-- `undoStack` — pressing Ctrl+Z after `/new` could restore old session content
-- `history` (command history for up/down navigation) — old commands linger
-- `killRing` (Emacs kill/yank ring) — old killed text is still accessible
-
-The Editor class declares these as `private` (see `editor.d.ts` lines 57-59, 64), so we need `(editor as any)` casts to access them at runtime.
-
-## Fix
-
-Edit `src/tui/index.ts` lines 485-496, replacing the `/new` handler with:
-
-```typescript
-if (cmd === 'new') {
-  // If the agent is running, stop the old session gracefully first.
-  // Without this, the pending chat() promise would continue consuming
-  // tokens and write stale output into the freshly cleared chat display.
-  if (isRunning) {
-    session.stop()
-    isRunning = false
-    loader.setMessage('')
-    tui.setShowHardwareCursor(true)
-  }
-  Session.clearSavedSession(config.cwd)
-  resetTokenUsage(config.cwd)
-  resetGlobalEventBus()
-  session = new Session(config, output)
-  session.onPlanWritten = planCb
-  chatContent = ''
-  chatMarkdown.setText('')
-  plansList.clearFilter()
-  // Reset editor internal state that setText('') doesn't clear
-  ;(editor as any).undoStack.clear()
-  ;(editor as any).history = []
-  ;(editor as any).killRing = new (require('@earendil-works/pi-tui').KillRing)()
-  updateFooter()
-  return
-}
-```
-
-> **Note about `KillRing` import**: The `KillRing` class is internal to pi-tui and not exported in the public types. Using `require('@earendil-works/pi-tui').KillRing` at runtime works because the package exports it internally. An alternative is to just set `(editor as any).killRing = { length: 0, ring: [], push: () => {}, peek: () => null, rotate: () => {} }` as a mock.
-
-> **Actual implementation**: Used `(editor as any).killRing.ring = []` instead of replacing the whole KillRing instance — simpler and avoids ESM `require` issues.
-
-## Todo List
-
-- [x] Replace the `/new` command handler in `src/tui/index.ts` (around line 485) with the version above that calls `session.stop()` if running and resets editor internal state
-- [x] Run `npm run build` to verify compilation
-- [x] Test: start agent, let it run, type `/new`, verify no stale output appears and editor history/undo is clean

package/.lonny/tui-autocomplete-above.md

@@ -1,62 +0,0 @@
-# Plan: Adjust TUI Autocomplete to Render Above the Editor (Matching Web Style)
-
-## Problem
-
-The TUI's slash command autocomplete list currently renders **below** the editor input area (after the bottom border). The web version displays command hints **above** the input (`bottom: 100%` via CSS). The user wants the TUI behavior to match the web — "向上的" (upward/above).
-
-## Root Cause
-
-The `Editor` component from `@earendil-works/pi-tui` (`node_modules/@earendil-works/pi-tui/dist/components/editor.js`) appends the autocomplete `SelectList` lines **after** the editor's bottom border in its `render()` method (lines 418-426). To get the "above" behavior, these lines need to appear **before** the editor's top border instead.
-
-## Approach (Final: patch-package + direct node_modules edit)
-
-Instead of monkey-patching at runtime (which had clipping issues with `maxHeight`), we:
-
-1. **Directly edit** `node_modules/@earendil-works/pi-tui/dist/components/editor.js` to use `result.unshift(...acLines)` instead of `result.push(...)` — placing autocomplete BEFORE the top border
-2. **Increase `maxHeight`** from 6 to 12 in `src/tui/index.ts` to accommodate both autocomplete and editor content
-3. **Use `patch-package`** to persist the node_modules change across `npm install`
-
-This approach:
-- Renders autocomplete ABOVE the editor (matching web UI)
-- Eliminates the clipping bug (autocomplete no longer competes with editor content for the 6-line overlay)
-- Survives `npm install` via patch-package
-
-## Files Changed
-
-### 1. `node_modules/@earendil-works/pi-tui/dist/components/editor.js` (patched)
-
-Changed `result.push(...acLines)` to `result.unshift(...acLines)` so autocomplete renders BEFORE the top border.
-
-### 2. `src/tui/index.ts`
-
-- Increased `maxHeight` from 6 to 12 on both editor overlay instances
-- Removed `applyEditorPatch()` import and call (old monkey-patch approach)
-- Deleted `src/tui/editor-patch.ts`
-
-### 3. `package.json`
-
-- Added `"postinstall": "patch-package"` script
-- Added `patch-package` devDependency
-
-### 4. `patches/@earendil-works+pi-tui+0.75.5.patch` (new)
-
-Created by `patch-package` to persist both changes:
-- `editor.js`: autocomplete unshifted to before top border
-- `tui.js`: alternate screen buffer handling
-
-## Edge Cases Considered
-
-1. **No autocomplete active** → `unshift` on empty array is a no-op; render output is unchanged
-2. **Scrolled editor** → autocomplete still renders above the top border/indicator line
-3. **Multiple autocomplete lines** → all moved above correctly
-4. **Resize** → render is called again with new width, positioning stays correct
-5. **npm install** → patch-package automatically reapplies the node_modules change
-
-## Todo List
-
-- [x] Step 1: Edit `node_modules/@earendil-works/pi-tui/dist/components/editor.js` to use `unshift` instead of `push` for autocomplete lines
-- [x] Step 2: Increase `maxHeight` from 6 to 12 in `src/tui/index.ts`
-- [x] Step 3: Remove old monkey-patch (`editor-patch.ts`, `applyEditorPatch()` import/call)
-- [x] Step 4: Install `patch-package` and create patch file
-- [x] Step 5: Add `postinstall` script to `package.json`
-- [x] Step 6: Build and verify (`npm run build` succeeds)