Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix Deliver owner-only 1:1 LINE reply loop

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

What to build

Deliver the first end-to-end conversational tracer bullet for L: Leo sends a 1:1 LINE message, the bridge verifies the source as the owner, records the interaction, and sends a safe reply back through LINE. Unknown users and group messages must be denied or ignored according to the bridge policy.

Acceptance criteria

  • A LINE 1:1 message from Leo's allowlisted user id receives a reply from L.
  • Messages from unknown users are rejected or ignored without leaking private context.
  • Group chat events are rejected by default in v0.1.
  • The reply path is covered by a unit or integration test using fixture payloads.

Blocked by

  • #23836

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#model loading#dependency error#configuration error#environment variable#network issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix Deliver owner-only 1:1 LINE reply loop