Make your computer a home for your AI partner. Avibe is the local-first Agent OS: Vibey, its built-in AI partner, works out of the box, and Claude Code, Codex & OpenCode run unchanged beside it — reach them from your browser, phone, or any chat app.
Python agentagent-osaiai-agentsai-partnerchatopsclaudeclaude-codecodexdevtoolsdiscord-botlark-botllmlocal-firstlong-term-memoryopencodeslack-botvibe-codingvibeywechat
Plan: Unify IM Proxy Configuration
Background
Per-platform proxy support is fragmented:
| Platform | Current state |
|---|---|
| Telegram | TelegramConfig.proxy_url (PR #251), threaded through aiohttp |
WeChatConfig.proxy_url, threaded through aiohttp |
|
| Discord | system SOCKS auto-detect via vibe.proxy.get_system_socks_proxy() |
| Slack | none (slack_sdk supports proxy= but unused) |
| Lark/Feishu | none (lark-oapi has no proxy hook) |
Two configs already have proxy_url, but in different places; UI has it only on the
Telegram wizard. Users in restricted regions have to figure this out per platform.
Goal
Single canonical proxy_url field at the base config level. Every adapter that
can honor it does so; the one that can't (Lark) surfaces a clear warning.
UI exposes the same field on every platform's setup wizard.
Solution shape
- Base config — lift
proxy_url: Optional[str] = Nonetomodules/im/base.py:BaseIMConfig. Drop the duplicate field onTelegramConfig/WeChatConfig. - Resolution helper — add
vibe.proxy.resolve_proxy(config_proxy)returning explicit config first, thenget_system_socks_proxy(), elseNone. Keeps Discord's existing system-detect behavior, extends it to all platforms. - Adapter wiring:
- Telegram, WeChat — already wired; switch to
resolve_proxy()for fallback. - Discord — replace
get_system_socks_proxy()call withresolve_proxy(). - Slack — pass
proxy=resolve_proxy(config.proxy_url)toAsyncWebClient. - Lark — log a clear warning if
proxy_urlis set; accept the gap untillark-oapiexposes a proxy hook.
- Telegram, WeChat — already wired; switch to
- Backend API — add
proxy_urlparameter toslack_auth_test,discord_auth_test,lark_auth_test(the Telegram one already has it). - UI:
- Add a "Proxy URL (optional)" input to
SlackConfig.tsx,DiscordConfig.tsx,LarkConfig.tsx,WeChatConfig.tsx. Reuse Telegram's pattern. - Lark wizard shows an extra hint that proxy is not yet wired through.
- Thread the value through corresponding
*AuthTestcalls.
- Add a "Proxy URL (optional)" input to
- Tests — add unit tests for the lifted base field and
resolve_proxy().
Out of scope
- Refactoring the wizard into a shared
<ProxyUrlField>component (follow-up). - A separate global "system-proxy mode" toggle.
- Lark proxy implementation (blocked on upstream
lark-oapi).
Todo
- Lift
proxy_urltoBaseIMConfig; remove duplicates - Add
resolve_proxy()tovibe/proxy.py - Wire Discord, Slack, Telegram, WeChat through
resolve_proxy() - Lark adapter: warn when
proxy_urlset - Backend
*_auth_testfunctions acceptproxy_url - UI: add proxy field to Slack/Discord/Lark/WeChat wizards
- Tests: base config field +
resolve_proxy() - Open PR