Peter Steinberger
490bbd10fc
feat(telegram): show user id in pairing
2026-01-09 00:01:23 +01:00
Shadow
9f8336c92b
Discord: harden gateway resilience
2026-01-08 16:52:44 -06:00
Peter Steinberger
769b76cd40
test(provider-activity): restore real timers
2026-01-08 23:52:07 +01:00
Peter Steinberger
69f8af530d
feat(providers): improve doctor + status probes
2026-01-08 23:48:37 +01:00
Peter Steinberger
41d484d239
test: cover browser and canvas verbose summaries
2026-01-08 23:48:37 +01:00
Peter Steinberger
2f1ce51b2c
test: stabilize doctor + bash tool tests
2026-01-08 23:44:54 +01:00
Peter Steinberger
cdfae0b9d3
fix(daemon): normalize audit paths
2026-01-08 22:28:51 +00:00
Peter Steinberger
ed80860c34
chore(format): apply biome fixes
2026-01-08 22:22:17 +00:00
Peter Steinberger
1f215848be
chore(test): align auth choice options formatting
2026-01-08 23:18:33 +01:00
Peter Steinberger
b01d7e39d5
fix(onboarding): preflight claude cli keychain
2026-01-08 23:18:33 +01:00
Peter Steinberger
36fa3c3cd3
fix: improve ws close diagnostics
2026-01-08 22:18:07 +00:00
Peter Steinberger
1cf8503017
fix(daemon): audit runtime best practices
2026-01-08 22:18:07 +00:00
Peter Steinberger
cd2f3bd355
feat(status): add Telegram/WhatsApp troubleshooting warnings
2026-01-08 23:14:11 +01:00
Peter Steinberger
a33271d374
refactor: share paren-aware chunk break scan
2026-01-08 23:09:34 +01:00
Peter Steinberger
7392387ec1
feat(status): warn on Discord message content intent
2026-01-08 23:07:34 +01:00
Peter Steinberger
b48ed56635
test: add DM elevated regression coverage
2026-01-08 22:58:15 +01:00
Peter Steinberger
014667e00b
fix: tighten group elevated targeting
2026-01-08 22:57:18 +01:00
Peter Steinberger
cda2025c49
fix: align env config schema
2026-01-08 22:57:18 +01:00
Peter Steinberger
59f89678b2
feat: allow inline env vars in config
2026-01-08 22:57:18 +01:00
Peter Steinberger
9a1267b530
fix(doctor): run legacy migrations in non-interactive
2026-01-08 21:37:22 +00:00
Peter Steinberger
5b46214379
refactor(cron): centralize telegram targets + delivery helpers
2026-01-08 21:36:53 +00:00
Peter Steinberger
5939dff092
fix: avoid synthesizing agent defaults
2026-01-08 22:26:29 +01:00
Luke
ab28eb5109
Merge branch 'main' into commands-list-clean
2026-01-08 16:25:56 -05:00
Peter Steinberger
2c7d64232e
feat: enable adaptive context pruning by default
2026-01-08 22:23:03 +01:00
Luke
5965708f1d
Merge branch 'main' into commands-list-clean
2026-01-08 16:22:25 -05:00
Peter Steinberger
d58cdf7c9f
fix: normalize gateway cli option strings
2026-01-08 22:18:06 +01:00
Peter Steinberger
35ba99c245
fix: honor non-interactive legacy migrations
2026-01-08 22:13:57 +01:00
Peter Steinberger
e75ca23e7d
test(cron): cover telegram topic delivery ( #478 ) (thanks @nachoiacovino)
2026-01-08 21:13:39 +00:00
Nacho Iacovino
5391f1141e
fix(cron): parse :topic: suffix for Telegram topic delivery
...
When cron jobs specify a Telegram topic in the 'to' field like
'-1003420657307:topic:60', the delivery code now correctly parses
this into separate chatId and messageThreadId values.
Previously, the entire string was passed as chatId, causing messages
to fail delivery to forum topics.
2026-01-08 21:12:15 +00:00
Peter Steinberger
699ba410fe
fix: resolve WhatsApp LID inbound mapping
2026-01-08 22:08:54 +01:00
Josh Palmer
2fae8eda66
🤖 codex: strip empty assistant blocks from history ( #210 )
2026-01-08 21:53:33 +01:00
Peter Steinberger
884e734809
feat(doctor): audit config + state permissions
2026-01-08 21:51:34 +01:00
Peter Steinberger
2d4ec35e1c
feat(doctor): add repair/force flows
2026-01-08 21:47:35 +01:00
Peter Steinberger
0373574f0b
refactor(telegram): centralize target parsing
2026-01-08 21:38:59 +01:00
Peter Steinberger
88039a69a2
style(cli): format daemon config warnings
2026-01-08 21:38:54 +01:00
Peter Steinberger
ea748f9440
fix(doctor): handle missing service readCommand
2026-01-08 21:38:51 +01:00
Luke
a574ae5415
Merge branch 'main' into commands-list-clean
2026-01-08 15:35:17 -05:00
Peter Steinberger
01641b34ea
feat(doctor): audit supervisor config + docs
2026-01-08 21:28:48 +01:00
Peter Steinberger
58a9e35233
style(cron): format telegram target tests
2026-01-08 21:23:07 +01:00
Peter Steinberger
5fea53d89c
fix(cron): parse telegram targets with prefixes (thanks @mitschabaude-bot)
2026-01-08 21:23:07 +01:00
Tobias Bischoff
7cffa65376
Merge branch 'main' into main
2026-01-08 21:16:47 +01:00
Azade
3a8d8bc6a4
fix(daemon): align systemd unit with documentation
...
Align generated systemd service file with docs:
https://docs.clawd.bot/gateway#supervision-systemd-user-unit
Adds:
- After=network-online.target
- Wants=network-online.target
- RestartSec=5
2026-01-08 21:16:19 +01:00
Tobias Bischoff
634f1389a4
Merge branch 'main' into main
2026-01-08 21:15:06 +01:00
Peter Steinberger
31fb5867e8
refactor(outbound): centralize telegram account defaults
2026-01-08 21:05:01 +01:00
Peter Steinberger
7905a27416
style: format gateway-cli log lines
2026-01-08 20:04:10 +00:00
Peter Steinberger
04e0e10411
fix: restore hidden gateway-daemon alias
2026-01-08 19:54:23 +00:00
Peter Steinberger
871c9e5286
fix(heartbeat): telegram accountId + cron jobId compat ( #516 , thanks @YuriNachos)
2026-01-08 20:47:22 +01:00
Yurii Chukhlib
9d42972b8a
fix(heartbeat): pass accountId for Telegram delivery
...
Heartbeat Telegram delivery was failing when the bot token was
configured only via telegram.botToken in config (without TELEGRAM_BOT_TOKEN
environment variable).
Root cause: deliverOutboundPayloads was called without accountId parameter,
so sendMessageTelegram couldn't determine which account to use and couldn't
find the token from config.
Fix: Resolve default Telegram accountId when provider is "telegram" and pass
it to deliverOutboundPayloads. This follows the same pattern used elsewhere in
the codebase (e.g., cron uses resolveTelegramToken).
Changes:
- Added import for resolveDefaultTelegramAccountId
- Added accountId resolution for telegram provider
- Updated deliverOutboundPayloads call to include accountId
Fixes #318
Co-Authored-By: Claude <noreply@anthropic.com >
2026-01-08 20:47:22 +01:00
Yurii Chukhlib
4dac298ae2
fix(cron): use jobId parameter instead of id for AI tool schema
...
Fixes parameter mismatch between AI tool schema and internal validation.
The TypeBox schema now uses `jobId` for update/remove/run/runs actions,
matching what users expect based on the returned job objects.
Changes:
- Changed parameter from `id` to `jobId` in TypeBox schema for update/remove/run/runs
- Updated execute function to read `jobId` parameter
- Updated tests to use `jobId` in input parameters
The gateway protocol still uses `id` internally - the tool now maps
`jobId` from the AI to `id` for the gateway call.
Fixes #185
Co-Authored-By: Claude <noreply@anthropic.com >
2026-01-08 20:47:22 +01:00
Peter Steinberger
4a918ccf47
fix: avoid splitting outbound chunks inside parentheses ( #499 ) — thanks @philipp-spiess
2026-01-08 20:39:28 +01:00
