mirror of https://github.com/getpaseo/paseo.git synced 2026-07-29 12:01:31 +00:00

Files

Xisheng Parker Zhao 4e28b0941b fix(server): surface Kiro CLI slash commands and skills over ACP (#1792 )

* fix(server): surface Kiro CLI slash commands and skills over ACP

Kiro CLI advertises its slash commands and skills through the
`_kiro.dev/commands/available` ACP extension notification rather than the
standard `available_commands_update` session update. ACPAgentSession only
trace-logged extension notifications and dropped the payload, so the
composer never showed any Kiro commands or skills.

- Map the extension payload onto the shared slash-command cache:
  `commands` (built-in, names arrive with a leading "/") and `prompts`
  (skills/prompts, tagged with a `skill:` serverName) are normalized to
  Paseo's AgentSlashCommand shape, stripping the leading slash and pulling
  the argument hint from `meta.hint`.
- Add KiroACPAgentClient (mirrors CursorACPAgentClient) so the provider
  waits for the first async command batch before listCommands() resolves,
  since Kiro emits the notification shortly after session/new.

* fix(server): settle on empty Kiro batch; inject Kiro commands via constructor option

Addresses review feedback on #1792.

Keep vendor-specific providers out of the generic acp-agent.ts, following
the same pattern as Cursor/Copilot: provider behavior is injected through
ACPAgentClient constructor options rather than special-cased in the base
class. Adds an optional extensionCommandsParser option on the generic ACP
client/session; the base extNotification() invokes it and routes any parsed
commands through a generic applyResolvedCommands() helper. Kiro supplies
parseKiroExtensionCommands (recognizes _kiro.dev/commands/available); the
base class no longer references any Kiro method string or payload shape.

Also fixes an empty-batch hang: applyResolvedCommands() always settles the
initial-commands gate, so a Kiro user with no slash commands no longer
blocks listCommands() for the full 10s timeout. Adds a regression test.

2026-06-30 09:36:48 +02:00

scripts

Make daemon shutdowns easier to diagnose (#1790 )

2026-06-29 23:31:11 +08:00

src

fix(server): surface Kiro CLI slash commands and skills over ACP (#1792 )

2026-06-30 09:36:48 +02:00

.env.example

Gate Claude SDK stream trace logs behind PASEO_CLAUDE_DEBUG

2026-04-10 10:05:13 +07:00

.gitignore

server(codex): normalize file paths, truncate large diffs, and drop turn/diff/updated telemetry

2026-02-06 11:51:59 +07:00

AGENTS.md

refactor(agent): add wait_for_agent tool and simplify prompt sending API

2025-11-03 11:47:15 +01:00

CLAUDE.md

Extract client SDK package (#1052 )

2026-05-28 01:58:18 +08:00

package.json

chore(release): cut 0.1.102-beta.2

2026-06-30 00:02:06 +02:00

README.md

chore: reformat codebase with oxfmt

2026-04-23 21:44:48 +07:00

tsconfig.scripts.json

Align script TypeScript lib with server build

2026-05-05 18:54:29 +07:00

tsconfig.server.json

Move terminal sessions to worker process

2026-04-30 22:35:22 +07:00

tsconfig.server.typecheck.json

Fix repo typecheck failures

2025-11-15 20:17:47 +01:00

vitest.config.ts

Key workspace status and ownership by ID, not directory

2026-06-16 13:37:58 +07:00

README.md

Voice Assistant

A voice-controlled terminal assistant that runs as a single local service.

Quick Start

# Install dependencies
npm install

# Copy environment variables
cp .env.example .env
# Edit .env and add your API keys (OpenAI, Deepgram)

# Run development servers
npm run dev

# Open browser to http://localhost:5173

Architecture

Express Server (port 3000) - Serves API and built UI in production
Vite Dev Server (port 5173) - Hot-reload React UI in development
WebSocket (/ws) - Real-time bidirectional communication
Agent - STT → LLM → TTS pipeline with terminal control
Daemon - tmux-based terminal management (in-process)

Development

# Run both servers (recommended)
npm run dev

# Or run separately:
npm run dev:server  # Express on port 3000
npm run dev:ui      # Vite on port 5173

# Type checking
npm run typecheck

# Build for production
npm run build

# Start production server
npm start

Project Status

✅ Completed (Phases 1-2):

Package setup and configuration
Express server with WebSocket
React UI with Vite
WebSocket client with ping/pong testing

⏳ In Progress (Phase 3):

Terminal control (tmux integration)

📋 Planned (Phases 4-9):

LLM integration (OpenAI GPT-4)
Agent orchestrator
Speech-to-Text (Deepgram)
Text-to-Speech (OpenAI)
Audio streaming
UI polish

See IMPLEMENTATION_PLAN.md for complete details.

Environment Variables

OPENAI_API_KEY=your-openai-key-here      # GPT-4 and TTS
DEEPGRAM_API_KEY=your-deepgram-key-here  # Streaming STT
STT_MODEL=whisper-1        # Optional: override to gpt-4o-transcribe, etc.
STT_CONFIDENCE_THRESHOLD=-3.0  # Optional: reject low-confidence clips
STT_DEBUG_AUDIO_DIR=.stt-debug # Optional: persist raw dictation audio for debugging
PASEO_HOME=~/.paseo        # Runtime state directory (agents/, etc.)
PASEO_LISTEN=127.0.0.1:6767  # Listen address (host:port or /path/to/socket)

PASEO_HOME defaults to ~/.paseo and isolates runtime artifacts like agents/. PASEO_LISTEN controls the daemon listen address. For blue/green testing you can run a parallel server without touching production state:

PASEO_HOME=~/.paseo-blue PASEO_LISTEN=127.0.0.1:7777 npm run dev

Tech Stack

Server: Express, TypeScript, ws (WebSocket)
Client: React 18, Vite, TypeScript
Terminal: tmux (via child_process)
AI: OpenAI (LLM + TTS), Deepgram (STT)

Testing

Currently manual testing via:

Start servers: npm run dev
Open http://localhost:5173
Test WebSocket connection (green status indicator)
Click "Send Ping" button to test communication

More testing guidance as features are implemented.

License

MIT