10 Commits

• refactor(hooks): split session events into individual typed events

  Major changes:
  - Replace monolithic SessionEvent with reason discriminator with individual
    event types: session_start, session_before_switch, session_switch,
    session_before_new, session_new, session_before_branch, session_branch,
    session_before_compact, session_compact, session_shutdown
  - Each event has dedicated result type (SessionBeforeSwitchResult, etc.)
  - HookHandler type now allows bare return statements (void in return type)
  - HookAPI.on() has proper overloads for each event with correct typing
  
  Additional fixes:
  - AgentSession now always subscribes to agent in constructor (was only
    subscribing when external subscribe() called, breaking internal handlers)
  - Standardize on undefined over null throughout codebase
  - HookUIContext methods return undefined instead of null
  - SessionManager methods return undefined instead of null
  - Simplify hook exports to 'export type * from types.js'
  - Add detailed JSDoc for skipConversationRestore vs cancel
  - Fix createBranchedSession to rebuild index in persist mode
  - newSession() now returns the session file path
  
  Updated all example hooks, tests, and emission sites to use new event types.

  Mario Zechner · 2025-12-30 22:42:22 +01:00
  d6283f99dc
• Use exhaustive switch on message.role throughout coding-agent

  - addMessageToChat: exhaustive switch for all AgentMessage roles
  - renderSessionContext: delegates to addMessageToChat, special handling for assistant tool calls and tool results
  - export-html formatMessage: exhaustive switch for all AgentMessage roles
  - Removed isHookMessage, isBashExecutionMessage type guards in favor of role checks
  - Fixed imports and removed unused getLatestCompactionEntry

  Mario Zechner · 2025-12-30 22:42:21 +01:00
  b921298af7
• 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

  Mario Zechner · 2025-12-30 22:42:20 +01:00
  6ddc7418da
• 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

  Mario Zechner · 2025-12-30 22:42:20 +01:00
  a055fd4481
• 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.

  Mario Zechner · 2025-12-30 22:42:20 +01:00
  574f1cba3d
• 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

  Mario Zechner · 2025-12-30 22:42:20 +01:00
  204d27581b
• 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

  Mario Zechner · 2025-12-30 22:42:19 +01:00
  a6322fda59
• 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.

  Mario Zechner · 2025-12-30 22:42:19 +01:00
  75a9c3c714
• Enable more biome lints and fix things
  Mario Zechner · 2025-12-21 22:56:20 +01:00
  d5fd685901
• Reorganize file structure: core/, utils/, modes/interactive/components/, modes/interactive/theme/
  Mario Zechner · 2025-12-09 00:51:33 +01:00
  83a6c26969