Skip to content

Feat/telegram allowlist#41

Open
a348163124 wants to merge 5 commits into
0xranx:mainfrom
a348163124:feat/telegram-allowlist
Open

Feat/telegram allowlist#41
a348163124 wants to merge 5 commits into
0xranx:mainfrom
a348163124:feat/telegram-allowlist

Conversation

@a348163124

Copy link
Copy Markdown

What does this PR do?

Type of change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation update
  • Refactoring
  • Other (describe below)

Checklist

  • pnpm run build passes
  • pnpm run test passes
  • New code has tests (if applicable)
  • Updated documentation (if applicable)

Integrate the grok CLI via headless streaming-json, session resume,
skill/MCP injection, and wire it through createEngine, CLI, onboard,
doctor, dashboard, docs, and tests.

0xranx commented Jul 15, 2026

Copy link
Copy Markdown
Owner

Thanks for the contribution. I don't think we should merge this as-is yet:

  • This PR mixes two unrelated changes: Telegram allowlist and a full Grok engine integration. Please split them into separate PRs.
  • pnpm test currently fails in the new Telegram test because the mocked Bot is not constructable.
  • injectGrokSkills() removes an existing same-name skill directory before linking, which can delete user files.
  • writeGrokMcpConfig() overwrites the whole .grok/config.toml, which can remove existing project MCP/config entries.
  • For headless Grok, please use the documented --no-auto-update flag. XAI_API_BASE_URL also does not appear to be supported by the current Grok CLI, so custom providers need to use Grok's model config instead.

The Telegram allowlist itself looks reasonable and should be quick to merge once split out, tested, and documented. The Grok integration needs the config/skill preservation fixes plus a real CLI E2E result.

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