Commit Graph

1263 Commits

  • Fix AgentInterface to requestUpdate on all message lifecycle events
    Was only handling message_update, now also handles message_start,
    message_end, turn_start, turn_end, agent_start, agent_end.
  • Add getApiKey to web-ui example Agent config
    Provides API keys from the provider keys store, matching old ProviderTransport behavior.
  • Use dynamic import for http module in OAuth files
    Prevents browser bundles from failing on import.
    The http module is only loaded when login functions are actually called.
  • Use Web Crypto API for OAuth PKCE, remove Node.js crypto dependency
    - Add pkce.ts with generatePKCE() using Web Crypto API
    - Update anthropic.ts, google-gemini-cli.ts, google-antigravity.ts
    - Replace Buffer.from() with atob() for base64 decoding
    - Works in both Node.js 20+ and browsers
    
    The OAuth modules still use Node.js http.createServer for callbacks,
    so they only work in CLI environments, but they no longer crash on
    import in browser bundles.
  • Add defaultConvertToLlm to web-ui, simplify example
    - web-ui exports: defaultConvertToLlm, convertAttachments, isUserMessageWithAttachments, isArtifactMessage
    - defaultConvertToLlm handles UserMessageWithAttachments and filters ArtifactMessage
    - Example's customMessageTransformer now extends defaultConvertToLlm
    - Removes duplicated attachment conversion logic from example
  • Fix web-ui and example for new agent API
    - AgentInterface composes UserMessageWithAttachments for attachments
    - Updated example to use convertToLlm instead of transport/messageTransformer
    - Fixed declaration merging: target pi-agent-core, add path to example tsconfig
    - Fixed typo in CustomAgentMessages key (user-with-attachment -> user-with-attachments)
    - customMessageTransformer properly converts UserMessageWithAttachments to content blocks
  • WIP: Major cleanup - move Attachment to consumers, simplify agent API
    - Removed Attachment from agent package (now in web-ui/coding-agent)
    - Agent.prompt now takes (text, images?: ImageContent[])
    - Removed transports from web-ui (duplicate of agent package)
    - Updated coding-agent to use local message types
    - Updated mom package for new agent API
    
    Remaining: Fix AgentInterface.ts to compose UserMessageWithAttachments
  • Expand README with AgentMessage/LLM conversion, event semantics, partial messages
    - Explain AgentMessage vs LLM Message separation and why it's needed
    - Document conversion flow: AgentMessage -> transformContext -> convertToLlm -> LLM
    - Clarify that prompt/queueMessage/continue must convert to user or toolResult
    - Document message_start/end events for prompt() and queued messages
    - Explain message_update is assistant-only with partial content
    - Add pattern for handling partial messages in reactive UIs
    - Document agent.state.streamMessage for accessing current partial
  • Update READMEs: remove agent section from pi-ai, rewrite pi-agent-core
    - Removed Agent API section from pi-ai README (moved to agent package)
    - Rewrote agent package README for new architecture:
      - No more transports (ProviderTransport, AppTransport removed)
      - Uses streamFn directly with streamProxy for proxy usage
      - Documents convertToLlm and transformContext
      - Documents low-level agentLoop/agentLoopContinue API
      - Updated custom message types documentation
  • WIP: Refactor agent package - not compiling
    - Renamed AppMessage to AgentMessage throughout
    - New agent-loop.ts with AgentLoopContext, AgentLoopConfig
    - Removed transport abstraction, Agent now takes streamFn directly
    - Extracted streamProxy to proxy.ts utility
    - Removed agent-loop from pi-ai (now in agent package)
    - Updated consumers (coding-agent, mom) for AgentMessage rename
    - Tests updated but some consumers still need migration
    
    Known issues:
    - AgentTool, AgentToolResult not exported from pi-ai
    - Attachment not exported from pi-agent-core
    - ProviderTransport removed but still referenced
    - messageTransformer -> convertToLlm migration incomplete
    - CustomMessages declaration merging not working properly
  • Fix: transform userMessage in _runAgentLoop before passing to transport
    HookMessage (role: hookMessage) was being passed directly to transport
    without transformation. Now it's transformed via messageTransformer
    which converts it to a proper user message for the LLM.
  • Fix messageTransformer to normalize HookMessage string content to array
    HookMessage.content can be string or array, but LLM Message.content
    must be an array. This was causing 'messages: at least one message
    is required' errors when hooks sent string content.
  • Cleanup: unify HookMessage naming and simplify SessionContext
    - Rename HookAppMessage to HookMessage, isHookAppMessage to isHookMessage
    - Remove entries array from SessionContext (use isHookMessage type guard instead)
    - HookMessage.content now accepts string directly (not just array)
    - Fix streamMessage type in AgentState (AppMessage, not Message)
    - Rename CustomMessageComponent to HookMessageComponent
    - Fix test hook to use pi.sendMessage
  • Wire context event to preprocessor for per-LLM-call execution
    - Change from contextTransform (runs once at agent start) to preprocessor
    - preprocessor runs before EACH LLM call inside the agent loop
    - ContextEvent now uses Message[] (pi-ai format) instead of AppMessage[]
    - Deep copy handled by pi-ai preprocessor, not Agent
    
    This enables:
    - Pruning rules applied on every turn (not just agent start)
    - /prune during long agent loop takes effect immediately
    - Compaction can use same transforms (future work)
  • Add context event for non-destructive message modification before LLM calls
    - Add contextTransform option to Agent (runs before messageTransformer)
    - Deep copy messages before passing to contextTransform (modifications are ephemeral)
    - Add ContextEvent and ContextEventResult types
    - Add emitContext() to HookRunner (chains multiple handlers)
    - Wire up in sdk.ts when creating Agent with hooks
    
    Enables dynamic context pruning: hooks can modify messages sent to LLM
    without changing session data. See discussion #330.
  • Snake: add full border frame and pause/resume with session persistence
    - Full box border around title, game area, and instructions
    - ESC pauses and saves state to session via pi.appendEntry()
    - Resume shows 'PAUSED - press any key to continue'
    - Q quits and clears saved state
    - High score persists across games
  • Fix snake velocity: render cells as 2 chars wide for square aspect
    Terminal cells are ~2:1 aspect ratio, so movement appeared faster
    vertically. Now each game cell is 2 characters wide.
  • Improve snake game visuals
    - Rounded box corners (╭╮╰╯)
    - Better characters: ● head, ○ body, ◆ food, · empty
    - Colored title with emoji
    - Dimmed borders and help text
    - Bold highlights for score and controls
  • Add immediate flag to hook commands for non-queued execution
    Commands with immediate: true run right away even during streaming.
    Used for UI-only commands like /snake that don't interact with LLM.
  • Add ui.custom() for custom hook components with keyboard focus
    - Add custom() to HookUIContext: returns { close, requestRender }
    - Component receives keyboard input via handleInput()
    - CustomMessageComponent default rendering now limits to 5 lines when collapsed
    - Add snake.ts example hook with /snake command
  • Refactor: shared exec utility, rename CustomMessageRenderer to HookMessageRenderer
    - Extract execCommand to src/core/exec.ts, shared by hooks and custom-tools
    - Rename CustomMessageRenderer -> HookMessageRenderer
    - Rename registerCustomMessageRenderer -> registerMessageRenderer
    - Renderer now receives HookMessage instead of CustomMessageEntry
    - CustomMessageComponent now has setExpanded() and responds to Ctrl+E toggle
    - Re-export ExecOptions/ExecResult from exec.ts for backward compatibility
  • Fix tests for sessionManager/modelRegistry on context
    - compaction-hooks-example.test.ts: get sessionManager/modelRegistry from ctx
    - compaction-hooks.test.ts:
      - Pass sessionManager/modelRegistry to HookRunner constructor
      - Remove setSessionFile call
      - Update tests to use session.sessionManager instead of event.sessionManager
  • Move exec to HookAPI, sessionManager/modelRegistry to HookEventContext
    Breaking changes:
    - HookEventContext now has sessionManager and modelRegistry (moved from SessionEventBase)
    - HookAPI now has exec() method (moved from HookEventContext/HookCommandContext)
    - HookRunner constructor takes sessionManager and modelRegistry as required params
    - Session events no longer include sessionManager/modelRegistry fields
    
    Hook code migration:
    - event.sessionManager -> ctx.sessionManager
    - event.modelRegistry -> ctx.modelRegistry
    - ctx.exec() -> pi.exec()
    
    Updated:
    - src/core/hooks/types.ts - type changes
    - src/core/hooks/runner.ts - constructor, createContext
    - src/core/hooks/loader.ts - add exec to HookAPI
    - src/core/sdk.ts - pass sessionManager/modelRegistry to HookRunner
    - src/core/agent-session.ts - remove sessionManager/modelRegistry from events
    - src/modes/* - remove setSessionFile calls, update events
    - examples/hooks/* - update to new API
  • Update plan: move exec to HookAPI, sessionManager/modelRegistry to contexts
    - exec() moves from HookEventContext/HookCommandContext to HookAPI
    - sessionManager/modelRegistry move from SessionEventBase to HookEventContext
    - HookCommandContext keeps sessionManager/modelRegistry (command handlers need them)
    - Both sendMessage and exec accessed via pi closure in command handlers
  • Remove emitLastMessage from continue(), use prompt(AppMessage) instead
    Cleans up the temporary emitLastMessage plumbing since we now use
    Agent.prompt(AppMessage) for hook messages instead of appendMessage+continue.
    
    - Remove emitLastMessage parameter from Agent.continue()
    - Remove from transport interface and implementations
    - Remove from agentLoopContinue()
  • Add Agent.prompt(AppMessage) overload for custom message types
    Instead of using continue() which validates roles, prompt() now accepts
    an AppMessage directly. This allows hook messages with role: 'hookMessage'
    to trigger proper agent loop with message events.
    
    - Add overloads: prompt(AppMessage) and prompt(string, attachments?)
    - sendHookMessage uses prompt(appMessage) instead of appendMessage+continue
  • Use proper HookAppMessage type instead of _hookData marker
    Following the same pattern as BashExecutionMessage:
    - HookAppMessage has role: 'hookMessage' with customType, content, display, details
    - isHookAppMessage() type guard for checking message type
    - messageTransformer converts to user message for LLM context
    - TUI checks isHookAppMessage() for rendering as CustomMessageComponent
    
    This makes the API clean for anyone building on AgentSession - they can
    use the type guard instead of knowing about internal marker fields.
  • Add emitLastMessage flag to agent.continue()
    When calling continue() with emitLastMessage=true, the agent loop
    emits message_start/message_end events for the last message in context.
    This allows messages added outside the loop (e.g., hook messages via
    sendHookMessage) to trigger proper TUI rendering.
    
    Changes across packages:
    - packages/ai: agentLoopContinue() accepts emitLastMessage parameter
    - packages/agent: Agent.continue(), transports updated to pass flag
    - packages/coding-agent: sendHookMessage passes true when triggerTurn
  • Hook commands: remove string return, use sendMessage() for prompting
    - Command handler now returns Promise<void> instead of Promise<string | undefined>
    - To trigger LLM response, use sendMessage() with triggerTurn: true
    - Simplify _tryExecuteHookCommand to return boolean
    
    Added example hook and slash command in .pi/:
    - .pi/hooks/test-command.ts - /greet command using sendMessage
    - .pi/commands/review.md - file-based /review command
  • Move hook command execution to AgentSession.prompt()
    Hook commands registered via pi.registerCommand() are now handled in
    AgentSession.prompt() alongside file-based slash commands. This:
    
    - Removes duplicate tryHandleHookCommand from interactive-mode and rpc-mode
    - All modes (interactive, RPC, print) share the same command handling logic
    - AgentSession._tryExecuteHookCommand() builds CommandContext using:
      - UI context from hookRunner (set by mode)
      - sessionManager, modelRegistry from AgentSession
      - sendMessage via sendHookMessage
      - exec via exported execCommand
    - Handler returning string uses it as prompt, undefined returns early
    
    Also:
    - Export execCommand from hooks/runner.ts
    - Add getUIContext() and getHasUI() to HookRunner
    - Make HookRunner.emitError() public for error reporting
  • Hook API: replace send() with sendMessage(), add appendEntry() and registerCommand()
    Breaking changes to Hook API:
    - pi.send(text, attachments?) replaced with pi.sendMessage(message, triggerTurn?)
      - Creates CustomMessageEntry instead of user messages
      - Properly handles queuing during streaming via agent loop
      - Supports optional turn triggering when idle
    - New pi.appendEntry(customType, data?) for hook state persistence
    - New pi.registerCommand(name, options) for custom slash commands
    - Handler types renamed: SendHandler -> SendMessageHandler, new AppendEntryHandler
    
    Implementation:
    - AgentSession.sendHookMessage() handles all three cases:
      - Streaming: queues message with _hookData marker, agent loop processes it
      - Not streaming + triggerTurn: appends to state/session, calls agent.continue()
      - Not streaming + no trigger: appends to state/session only
    - message_end handler routes based on _hookData presence to correct persistence
    - HookRunner gains getRegisteredCommands() and getCommand() methods
    
    New types: HookMessage<T>, RegisteredCommand, CommandContext
  • Wire up hook custom message renderers to TUI
    - CustomMessageComponent accepts optional CustomMessageRenderer
    - If hook provides a renderer, call it and use returned Component inside Box
    - Falls back to default rendering (label + Markdown) if no renderer or null returned
    - renderSessionContext gets renderer from hookRunner and passes to component
  • Add TUI rendering for CustomMessageEntry
    - Add CustomMessageComponent with purple-tinted styling
    - Add theme colors: customMessageBg, customMessageText, customMessageLabel
    - Rename renderMessages to renderSessionContext taking SessionContext directly
    - renderInitialMessages now gets context from sessionManager
    - Skip rendering for display: false entries