A fallback credential is a fact on the call, not a row in the feed - #143
Merged
Conversation
czpython
force-pushed
the
credential-fallback-noise
branch
from
July 28, 2026 17:39
8f7c13b to
2bde56e
Compare
czpython
enabled auto-merge (squash)
July 28, 2026 17:40
Every agent call emitted credential.fallback when its login came from the fallback account, so a run put one identical row in the feed per call, with no renderer behind the type. The charged account is already stamped on the agent call it paid for, and reads there.
czpython
force-pushed
the
credential-fallback-noise
branch
from
July 28, 2026 17:43
2bde56e to
d4bd3a8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every agent call emitted a
credential.fallbackevent when its login camefrom the fallback account rather than the run's own. A run makes one such
call per agent, so a single run wrote a column of identical rows into the
feed — same subject, same harness, same run id — and the feed had no
renderer for the type, so each row read as the raw dotted identifier.
The fact those rows carried is already recorded:
agent_calls.account_idholds the subscription actually charged, on the row that paid it, and it is
already on the wire. The event is dropped; the account snapshot that stamps
the call stays.
The feed test that used this type as its fixture keeps it — logged rows from
before this change still carry the kind, and rendering an unrecognised kind
as itself is what keeps them readable.