Repository navigation
Releases
Releases · vivaxy/remote-agents
v0.3.10
v0.3.9
v0.3.8
v0.3.7
Features
- cli: add --version and --help flags
- config: remove configurable working-dir and remote-agents-dir CLI flags
- input: handle non-destructive slash commands live during agent execution
- permissions: allow-always writes to state, settings.local.json, and remote-agents.json
- release: add uninstall script
v0.3.6
v0.3.5
v0.3.4
v0.3.3
Features
- state: align all state display outputs to full user-facing field set
Bug Fixes
- events: suppress MaxListenersExceededWarning on shared event bus
- release: strip commit links from release notes instead of removing whole lines
- startup: align log config items to current AppConfig keys
- wechat: capture STATE_LOADED unconditionally so startup notification fires after restart
v0.3.2
v0.2.0
⚠ BREAKING CHANGES
- channel: remove redundant wechatAllowedUsers config
- channel: rename the JSON key channelProxyScript -> channelNetworkScript
and update the script's return statement to wrap the URL in an object:
return 'http://...'becomesreturn { proxy: 'http://...' }. - channel: make channelProxyScript loader strict on malformed input
- channel: the
telegramProxyconfig field is removed. Users on a
proxy must add achannelProxyScriptpointing to a TS file that returns
the proxy URL for'telegram'(and optionally'wechat'). See
docs/requirements.md § 3.6 for the contract. - Chat log format now uses emoji headers instead of Obsidian-style callouts
Replace > [!type] label timestamp format with simpler {emoji} label timestamp format:
- 💬 for input messages
- ✅ for successful output
- ❌ for errors
⚠️ for warnings/permission denials- 📝 for notes/state info
Changes:
- Update buildCalloutHeader() to use emoji prefix instead of Obsidian syntax
- Update formatPermissionDenials() to use emoji (📝) instead of > [!NOTE]
- Remove duplicate calloutEmoji() implementation from messaging.ts
- Update Telegram HTML converters to match emoji format using string matching
- Update all test assertions to expect emoji format
- Update documentation (requirements.md, CLAUDE.md) with new format examples
The new format is more universally readable and matches what Telegram users already see.
Old chat files with > [!type] format will not be automatically converted.