Skip to content

feat: wire IM channel runtime#341

Merged
warren618 merged 1 commit into
mainfrom
feat/im-channels
Jun 30, 2026
Merged

feat: wire IM channel runtime#341
warren618 merged 1 commit into
mainfrom
feat/im-channels

Conversation

@warren618

Copy link
Copy Markdown
Collaborator

Summary

  • add shared IM channel discovery, dependency-gated status, manager, message bus, pairing store, and SessionService runtime wiring
  • expose channel controls through REST, CLI, and Settings UI with i18n coverage
  • declare channel dependency extras and add focused backend/frontend regression tests
  • remove legacy-name references from the committed tree

Verification

  • PYTHONPATH=agent pytest agent/tests/test_channels_runtime.py agent/tests/test_channels_api.py agent/tests/test_cli_channels.py agent/tests/test_packaging_dependencies.py -q
  • python -m compileall -q agent/src/channels agent/src/channelsui agent/src/security/workspace_access.py agent/src/security/network.py agent/src/security/workspace_policy.py agent/src/session/goal_state.py agent/src/session/webui_turns.py agent/src/utils/media_decode.py agent/api_server.py agent/cli/_legacy.py
  • cd frontend && npm test -- SettingsChannels --run && npm test -- i18n --run
  • cd frontend && npm run build
  • final committed tree legacy-name scan returned no matches

@warren618
warren618 merged commit 681360f into main Jun 30, 2026
2 checks passed
@warren618
warren618 deleted the feat/im-channels branch June 30, 2026 06:31
@Penn-Live

Copy link
Copy Markdown

How to configure this in Docker?

@warren618

Copy link
Copy Markdown
Collaborator Author

Good question. In Docker, channel config lives in the same ~/.vibe-trading/agent.json, which the container mounts at /home/vibe/.vibe-trading (the vibe-home volume in docker-compose.yml). So:

  1. Make sure the image includes the channel extra (build with vibe-trading-ai[telegram] / [channels]) — SDK-backed adapters are optional.
  2. Put agent.json in that volume — bind-mount your local one, or write it into the vibe-home volume — with the channels block enabled:
    { "channels": { "telegram": { "enabled": true, "token": "..." } } }
  3. docker compose exec vibe-trading vibe-trading channels status --local to verify config + SDK presence, then ... channels start.

The README "IM channels" section has the full reference. Tell me which adapter you're setting up and I'll give the exact keys.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants