# Managed by IssueSpec. Hand edits are welcome; keep the schema valid.
id: 18
title: Add /btw command
state: open
author:
  name: k33g
  email: ph.charriere@gmail.com
createdAt: 2026-09-18T00:00:00.000Z
updatedAt: 2026-09-18T00:00:00.000Z
labels:
  - feature
  - enhancement
body: |
  Add a `/btw` (by the way) command to allow users to provide contextual information or side notes to the agent without triggering a full response or workflow.

  ## Use Cases
  
  - Provide background information: `/btw I prefer functional programming style`
  - Set preferences: `/btw use TypeScript instead of JavaScript when creating new files`
  - Add context: `/btw this is a legacy codebase, avoid breaking changes`
  - Share constraints: `/btw we're targeting Node 18, don't use newer APIs`
  - Note conventions: `/btw we use kebab-case for file names in this project`

  ## Requirements

  - Command syntax: `/btw <message>`
  - Should acknowledge receipt but not trigger full agent response
  - Store context in session memory for use in subsequent requests
  - Context should persist throughout the session
  - Minimal response (e.g., "Noted: <brief echo>")
  - Context should be accessible to agent when processing other requests

  ## Implementation Considerations

  ### Backend
  - New command handler in command processing logic
  - Session-scoped context store (in-memory per ACP session)
  - Context should be included in agent prompts or system messages
  - Consider max context size (tokens)

  ### Frontend
  - Command auto-complete suggestion for `/btw`
  - Visual indicator that context was stored (subtle confirmation)
  - Optional: Display stored context in UI (sidebar, status bar, or collapsible panel)
  - Optional: Command to list current context `/btw list`
  - Optional: Command to clear context `/btw clear`

  ## Behavior Details

  - `/btw` without message should show usage or list current context
  - Multiple `/btw` commands should accumulate (not replace)
  - Context should be prepended to subsequent agent requests
  - Agent should use context passively (consider but don't always mention it)

  ## Related Commands

  - `/claude <message>` - sends message to agent (full response)
  - `/system <message>` - system-level commands
  - `/help` - show available commands

  ## Open Questions

  - Should context persist across sessions (saved to file)?
  - Should there be a way to remove specific context items?
  - Character/token limit per `/btw` message?
  - Should `/btw` be specific to Ori or generalized for ACP?
  - Format for displaying accumulated context (list, prose, structured)?

  ## Example Interaction

  ```
  User: /btw I prefer verbose variable names for clarity
  Ori: Noted: preference for verbose variable names

  User: /btw This project uses ESLint with Airbnb style guide
  Ori: Noted: ESLint + Airbnb style guide

  User: Add a function to calculate tax
  Agent: [creates function with verbose names, following Airbnb conventions]
  ```

  ## Priority

  Medium - Nice to have for improved UX and context management
tasks: []
comments: []