forked from bots-garden/ori
| 🛟 Updated. | 1 | # Managed by IssueSpec. Hand edits are welcome; keep the schema valid. |
| 2 | id: 18 | |
| 3 | title: Add /btw command | |
| 4 | state: open | |
| 5 | author: | |
| 6 | name: k33g | |
| 7 | email: ph.charriere@gmail.com | |
| 8 | createdAt: 2026-09-18T00:00:00.000Z | |
| 9 | updatedAt: 2026-09-18T00:00:00.000Z | |
| 10 | labels: | |
| 11 | - feature | |
| 12 | - enhancement | |
| 13 | body: | | |
| 14 | 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. | |
| 15 | ||
| 16 | ## Use Cases | |
| 17 | ||
| 18 | - Provide background information: `/btw I prefer functional programming style` | |
| 19 | - Set preferences: `/btw use TypeScript instead of JavaScript when creating new files` | |
| 20 | - Add context: `/btw this is a legacy codebase, avoid breaking changes` | |
| 21 | - Share constraints: `/btw we're targeting Node 18, don't use newer APIs` | |
| 22 | - Note conventions: `/btw we use kebab-case for file names in this project` | |
| 23 | ||
| 24 | ## Requirements | |
| 25 | ||
| 26 | - Command syntax: `/btw <message>` | |
| 27 | - Should acknowledge receipt but not trigger full agent response | |
| 28 | - Store context in session memory for use in subsequent requests | |
| 29 | - Context should persist throughout the session | |
| 30 | - Minimal response (e.g., "Noted: <brief echo>") | |
| 31 | - Context should be accessible to agent when processing other requests | |
| 32 | ||
| 33 | ## Implementation Considerations | |
| 34 | ||
| 35 | ### Backend | |
| 36 | - New command handler in command processing logic | |
| 37 | - Session-scoped context store (in-memory per ACP session) | |
| 38 | - Context should be included in agent prompts or system messages | |
| 39 | - Consider max context size (tokens) | |
| 40 | ||
| 41 | ### Frontend | |
| 42 | - Command auto-complete suggestion for `/btw` | |
| 43 | - Visual indicator that context was stored (subtle confirmation) | |
| 44 | - Optional: Display stored context in UI (sidebar, status bar, or collapsible panel) | |
| 45 | - Optional: Command to list current context `/btw list` | |
| 46 | - Optional: Command to clear context `/btw clear` | |
| 47 | ||
| 48 | ## Behavior Details | |
| 49 | ||
| 50 | - `/btw` without message should show usage or list current context | |
| 51 | - Multiple `/btw` commands should accumulate (not replace) | |
| 52 | - Context should be prepended to subsequent agent requests | |
| 53 | - Agent should use context passively (consider but don't always mention it) | |
| 54 | ||
| 55 | ## Related Commands | |
| 56 | ||
| 57 | - `/claude <message>` - sends message to agent (full response) | |
| 58 | - `/system <message>` - system-level commands | |
| 59 | - `/help` - show available commands | |
| 60 | ||
| 61 | ## Open Questions | |
| 62 | ||
| 63 | - Should context persist across sessions (saved to file)? | |
| 64 | - Should there be a way to remove specific context items? | |
| 65 | - Character/token limit per `/btw` message? | |
| 66 | - Should `/btw` be specific to Ori or generalized for ACP? | |
| 67 | - Format for displaying accumulated context (list, prose, structured)? | |
| 68 | ||
| 69 | ## Example Interaction | |
| 70 | ||
| 71 | ``` | |
| 72 | User: /btw I prefer verbose variable names for clarity | |
| 73 | Ori: Noted: preference for verbose variable names | |
| 74 | ||
| 75 | User: /btw This project uses ESLint with Airbnb style guide | |
| 76 | Ori: Noted: ESLint + Airbnb style guide | |
| 77 | ||
| 78 | User: Add a function to calculate tax | |
| 79 | Agent: [creates function with verbose names, following Airbnb conventions] | |
| 80 | ``` | |
| 81 | ||
| 82 | ## Priority | |
| 83 | ||
| 84 | Medium - Nice to have for improved UX and context management | |
| 85 | tasks: [] | |
| 86 | comments: [] |