Several times the agent created fj issues without reporting that it had done so

coilysiren commented

2026-08-13 02:53:58 +00:00

Owner

^ this issue creation was not mentioned in chat

Example => https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/231#issue-8115 ^ this issue creation was not mentioned in chat

coilyco-ops referenced this issue

2026-08-13 03:24:39 +00:00

The Agent responded with a Forgejo issue reference in short form #234

coilyco-ops referenced this issue

2026-08-13 03:34:20 +00:00

The Agent responded with a Forgejo issue reference in short form #234

coilyco-ops commented

2026-08-13 03:34:33 +00:00

Member

DELIVERED — Angie (ENG)

Fixed on main as 6dc94ef. An issue the turn filed is now appended to the reply as a canonical URL whether or not the model mentioned filing it, so a silent filing can no longer happen. Full write-up and the prerequisite fix are on #234

Live verification pending rollout. Reopen if the live behavior does not match.

**DELIVERED — Angie (ENG)** Fixed on main as `6dc94ef`. An issue the turn filed is now appended to the reply as a canonical URL whether or not the model mentioned filing it, so a silent filing can no longer happen. Full write-up and the prerequisite fix are on https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/234 Live verification pending rollout. Reopen if the live behavior does not match.

coilyco-ops closed this issue

2026-08-13 03:34:43 +00:00

coilyco-ops referenced this issue

2026-08-13 03:45:11 +00:00

Grounding: active third-person and subjectless action claims still escape passiveActionClaim #241

coilyco-ops referenced this issue

2026-08-13 03:49:00 +00:00

passiveActionClaim fires on correct replies, including negations — "No issue has been filed" fails the turn #243

coilyco-ops referenced this issue

2026-08-13 03:51:08 +00:00

agents should be encouraged to file fj issues about problems, confusion, gaps, feedback, ... #208

coilyco-ops commented

2026-08-13 03:51:21 +00:00

Member

Design decision — reporting is mandatory and inline

Recorded by Delphi (design seat). Kai's decision, 2026-08-12.

Decided. Every issue Echo files is announced in-channel, in the same turn, with its fully-qualified canonical URL. Kai explicitly rejected batched/digest reporting because it loses the immediate in-context link — which is exactly what this issue is about.

Full filing policy, including the triggers: #208

Framing for the implementer

Silent filing and phantom filing are the same defect from opposite ends. This issue is a receipt with no announcement; #206 is an announcement with no receipt. One invariant covers both:

A filing tool call and its in-channel announcement-with-URL either both happen, or neither does.

Build it as one rule in the output-review stage, not as two separate patches.

The example in this issue body — #231, created without any mention in chat — is a ready-made regression case.

## Design decision — reporting is mandatory and inline Recorded by Delphi (design seat). Kai's decision, 2026-08-12. **Decided.** Every issue Echo files is announced **in-channel, in the same turn**, with its fully-qualified canonical URL. Kai explicitly rejected batched/digest reporting because it loses the immediate in-context link — which is exactly what this issue is about. Full filing policy, including the triggers: https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/208 ### Framing for the implementer Silent filing and phantom filing are the **same defect from opposite ends**. This issue is a receipt with no announcement; https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/206 is an announcement with no receipt. One invariant covers both: > A filing tool call and its in-channel announcement-with-URL either both happen, or neither does. Build it as one rule in the output-review stage, not as two separate patches. The example in this issue body — https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/231, created without any mention in chat — is a ready-made regression case.

coilyco-ops referenced this issue

2026-08-13 03:52:02 +00:00

acknowledge hallucination capability in future evaluations #231

coilyco-ops referenced this issue

2026-08-13 03:52:46 +00:00

test(grounding): pin both halves of the action-claim property #244

coilyco-ops commented

2026-08-13 03:54:26 +00:00

Member

Verified addressed on main — Quail (QA). internal/community/issueref.go handles precisely this case, and handles it in the way that survives the model staying silent.

AppendIssueReferences has a dedicated branch for it, commented "An issue this turn filed belongs in the reply even when the model said nothing about it." I probed the exact shape you reported — a create_issue tool ran, the reply mentioned nothing:

Noted.

Referenced issues:
https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/233

The URL is appended from the tool result regardless of what the model wrote, so a silent filing is no longer invisible to the member. That is the right layer for this — prompting the model to always report its filings would be one more instruction to drift from, whereas this cannot drift.

Note the direction of this issue is the opposite of the ungrounded-claim cluster in #241 and #243. There the tool did not run and the reply claimed it did; here the tool ran and the reply said nothing. Different defect, different fix, and this one is done.

Verified in code at a0d944d, not against the deployed pod.

**Verified addressed on `main` — Quail (QA).** `internal/community/issueref.go` handles precisely this case, and handles it in the way that survives the model staying silent. `AppendIssueReferences` has a dedicated branch for it, commented *"An issue this turn filed belongs in the reply even when the model said nothing about it."* I probed the exact shape you reported — a `create_issue` tool ran, the reply mentioned nothing: ``` Noted. Referenced issues: https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/233 ``` The URL is appended from the tool result regardless of what the model wrote, so a silent filing is no longer invisible to the member. That is the right layer for this — prompting the model to always report its filings would be one more instruction to drift from, whereas this cannot drift. Note the direction of this issue is the **opposite** of the ungrounded-claim cluster in https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/241 and https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/243. There the tool did not run and the reply claimed it did; here the tool ran and the reply said nothing. Different defect, different fix, and this one is done. **Verified in code at `a0d944d`, not against the deployed pod.**

coilyco-ops referenced this issue

2026-08-13 06:15:50 +00:00

The agent stated a correct has been filed, but did not link the correction #209

coilyco-ops referenced this issue

2026-08-13 06:51:27 +00:00

The agent is not proactive enough about filing fj issues around its knowledge gaps #235

coilyco-ops referenced this issue

2026-08-13 06:55:24 +00:00

The agent is not proactive enough about filing fj issues around its knowledge gaps #235

coilyco-ops referenced this issue

2026-08-13 07:07:36 +00:00

The agent is not proactive enough about filing fj issues around its knowledge gaps #235