Skip to content

fix: port PR #51 Discord fixes to rc (+ Telegram gistUrl follow-up) - #65

Merged
chr1syy merged 2 commits into
rcfrom
fix/pr51-port-to-rc
Jul 20, 2026
Merged

fix: port PR #51 Discord fixes to rc (+ Telegram gistUrl follow-up)#65
chr1syy merged 2 commits into
rcfrom
fix/pr51-port-to-rc

Conversation

@chr1syy

@chr1syy chr1syy commented Jul 20, 2026

Copy link
Copy Markdown
Collaborator

Ports the four fixes from #51 (merged to main as 77245d2) onto rc, where active development actually happens. Without this they'd be silently missing from every rc-channel release.

Commits

  1. 2b90162 — clean cherry-pick of 77245d2, no conflicts. rc had only touched these files via the console.*KernelLogger refactor on non-overlapping lines, and never touched gist code at all. Attribution to @scriptease preserved.
  2. Telegram gistUrl fixup — see below.

The Telegram issue this surfaced

The cherry-pick renames GistResult.urlgistUrl. rc has a Telegram provider that main does not, and its /gist handler read result.url.

This does not fail tscGistResult has an [key: string]: unknown index signature, so result.url resolves to unknown rather than erroring. I confirmed npx tsc --noEmit passes clean with the stale field in place. The break would have been runtime-only: Telegram posting undefined as the gist URL.

Worth flagging as a general hazard — that index signature means any future field rename on GistResult will pass typecheck and fail in production.

Tests

498/498 passing on rc.

Out of scope / follow-ups

🤖 Generated with Claude Code

scriptease and others added 2 commits July 20, 2026 21:24
Bundles four independent Discord provider fixes from the PR (the title
only covered the first):

1. Ignore Discord system messages (thread renames, pin notices, joins)
   so they no longer reach the agent as user input.
   src/providers/discord/messageCreate.ts

2. Resolve agent binding from the parent channel when a message arrives
   in a thread, so threads inherit their channel's agent instead of
   coming back unbound.
   src/providers/discord/channelsDb.ts, commands/auto-run.ts

3. Use the gistUrl returned by `maestro-cli gist create` instead of
   reconstructing the URL locally.
   src/core/maestro.ts, providers/discord/commands/gist.ts

4. Sort the /agents list output for stable, readable ordering.
   src/providers/discord/commands/agents.ts

Thanks to @scriptease for the contribution.

Co-authored-by: Florian Agsteiner <florian.agsteiner@gmail.com>
The cherry-pick of 77245d2 renames GistResult.url to gistUrl. rc has a
Telegram provider that main does not, and its /gist handler still read
result.url.

This does NOT fail typecheck: GistResult carries an
[key: string]: unknown index signature, so result.url resolves to
unknown instead of erroring. The break is runtime-only — Telegram would
have posted 'undefined' as the gist URL.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 1b6a26e9-82bd-4ed8-b5b7-27f211a94c1b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/pr51-port-to-rc

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@chr1syy
chr1syy merged commit 65c25cc into rc Jul 20, 2026
1 check passed
@chr1syy
chr1syy deleted the fix/pr51-port-to-rc branch July 20, 2026 19:52
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