- Add isValidToolType() type guard to replace unsafe `as ToolType` casts
- Make `raw` field optional in ParsedEvent interface since never read
- Fix MockParser in tests to implement missing error detection methods
- Add @internal JSDoc to test-only exports (hasOutputParser, getAllOutputParsers, clearParserRegistry)
- Update AGENT_SUPPORT.md to reference canonical ParsedEvent source instead of duplicating type definition
- Add tests for new isValidToolType function
- Added user-configurable context window settings for agents 🎯
- Improved error detection to only parse JSON events, not text 🛡️
- Fixed stderr routing for AI processes to correct tabs 🔧
- Added context window support for Codex with model detection 🧮
- Hide context usage widget when window size is zero 👻
- Added number input type for agent configuration options 🔢
- Strip ANSI codes from stderr for cleaner output 🧹
- Added hint for enabling loop mode with documents 💡
- Display correct provider name in input placeholder text ✏️
- Improved network error patterns to reduce false positives 🎯
Research confirmed OpenCode's batch mode auto-approves all tool operations:
- No explicit --dangerously-skip-permissions flag needed
- opencode run subcommand inherently enables auto-approval
- Permission system configurable via opencode.json if needed
- Read-only operations never require approval
Sources: OpenCode official docs (permissions, CLI) and GitHub README
- CLAUDE.md: Added agent capabilities section, updated architecture diagram
with parsers/ and storage/ directories, added agentSessions and agentError
APIs, updated key files table, added error fields to Session interface
- AGENT_SUPPORT.md: Added multi-provider architecture status section showing
all 7 completed components, updated supported agents reference with
implementation status and detailed checklist for planned agents
- CONTRIBUTING.md: Updated supported agents reference table with status
column and link to detailed guide
Found expired OAuth token, attempting refresh...
Token refresh successful
I'd be happy to help you create a clean update summary for a GitHub project! However, I don't see any input provided after "INPUT:" in your message.
Could you please share the changelog, commit history, or release notes that you'd like me to summarize? Once you provide that information, I'll create an exciting CHANGES section with 10-word bullets and relevant emojis as requested.
