Issue #92: agent comments report token usage but not which model produced them. The MODEL env var was already wired into the build-activity-log step (agent.yml:202) but never rendered. Now the run-report details dropdown line includes the model name, so every agent comment shows its model alongside tool calls and token usage.
Changes
.gitea/workflows/scripts/build-activity-log.sh: append · model <MODEL> to the details summary line (defaults to ? if MODEL is unset).
## Summary
Issue #92: agent comments report token usage but not which model produced them. The `MODEL` env var was already wired into the build-activity-log step (agent.yml:202) but never rendered. Now the run-report `details` dropdown line includes the model name, so every agent comment shows its model alongside tool calls and token usage.
## Changes
- `.gitea/workflows/scripts/build-activity-log.sh`: append `· model <MODEL>` to the details summary line (defaults to `?` if `MODEL` is unset).
---
Resolves #92
Diff is exactly the intended minimal change: appended · model %s and a 5th positional arg ${MODEL:-?} to the printf. The MODEL env var is already exported by the workflow step at agent.yml:202 (the build-activity-log job's env), so the script will see it.
Let me verify the full picture:
agent.yml:202 already passes MODEL env into build-activity-log.sh ✓
the model name now appears in the details dropdown's summary line alongside tool calls, in/out tokens and cost ✓
defaults to ? if MODEL is unset (defensive) ✓
single-file change, no other code paths affected ✓
This is a small, correct, minimal change that resolves issue #92. No behavior to drive in a browser — pure CI-side rendering. Approving.
details
🔧 14 tool calls · in 293832 · out 1237 tokens · subscription
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Issue #92: agent comments report token usage but not which model produced them. The
MODELenv var was already wired into the build-activity-log step (agent.yml:202) but never rendered. Now the run-reportdetailsdropdown line includes the model name, so every agent comment shows its model alongside tool calls and token usage.Changes
.gitea/workflows/scripts/build-activity-log.sh: append· model <MODEL>to the details summary line (defaults to?ifMODELis unset).Resolves #92
Opened PR #93 for review.
details
🔧 9 tool calls · in 146906 · out 785 tokens · subscription
🔧 read:
AGENTS.md🔧 bash:
ls -la /workspace/gitea/agents/ && git -C /workspace/gitea/agents branch --show-current && git -C /workspace/gitea/agents log --oneline -5🔧 bash:
ls -la /workspace/gitea/agents/.gitea/workflows/ /workspace/gitea/agents/.agents-workflow/🔧 grep:
token|model|usage|details|subscription🔧 read:
.gitea/workflows/scripts/build-activity-log.sh🔧 grep:
MODEL|build-activity-log|model🔧 read:
.gitea/workflows/agent.yml🔧 edit:
.gitea/workflows/scripts/build-activity-log.sh🔧 bash:
cd /workspace/gitea/agents && git diff && git add -A && git commit -m "report: include model name in the run-report details line" && git push origin ai/issue-92 2>&1 | tail -5tokens — input 146906 (fresh 146906 · cache 0w / 0r) · output 785 · reasoning 0 · subscription
Diff is exactly the intended minimal change: appended
· model %sand a 5th positional arg${MODEL:-?}to the printf. TheMODELenv var is already exported by the workflow step at agent.yml:202 (the build-activity-log job's env), so the script will see it.Let me verify the full picture:
MODELenv into build-activity-log.sh ✓?if MODEL is unset (defensive) ✓This is a small, correct, minimal change that resolves issue #92. No behavior to drive in a browser — pure CI-side rendering. Approving.
details
🔧 14 tool calls · in 293832 · out 1237 tokens · subscription
🔧 skill:
Loaded skill: gitea-api🔧 bash:
API="${GITHUB_SERVER_URL}/api/v1"; REPO="${GITHUB_REPOSITORY}"; echo "Repo: $REPO"; curl -sS -H "Authorization: token $SELF_TOKEN" "$API/repos/$REPO/pulls/93" | jq '{title,state,body,user:.user.login,head:.head.ref,base:.base.ref}'🔧 bash:
API="${GITHUB_SERVER_URL}/api/v1"; REPO="${GITHUB_REPOSITORY}"; curl -sS -H "Authorization: token $SELF_TOKEN" "$API/repos/$REPO/pulls/93/files" | jq '.[] | {path, status, additions, deletions, sha}'🔧 bash:
API="${GITHUB_SERVER_URL}/api/v1"; REPO="${GITHUB_REPOSITORY}"; curl -sS -H "Authorization: token $SELF_TOKEN" "$API/repos/$REPO/pulls/93/files?limit=50" | jq '.[]'🔧 bash:
API="${GITHUB_SERVER_URL}/api/v1"; REPO="${GITHUB_REPOSITORY}"; curl -sS -H "Authorization: token $SELF_TOKEN" "$API/repos/$REPO/pulls/93" | jq -r '.diff'🔧 bash:
API="${GITHUB_SERVER_URL}/api/v1"; REPO="${GITHUB_REPOSITORY}"; curl -sS -H "Authorization: token $SELF_TOKEN" -H "Accept: application/vnd.github.v3.diff" "$API/repos/$REPO/pulls/93"🔧 bash:
curl -sS "https://git.ffaerber.duckdns.org/gitea/agents/pulls/93.diff"🔧 bash:
curl -sS "https://git.ffaerber.duckdns.org/gitea/agents/raw/commit/fa3005b7b5a613537bc6c2130c4af7c554aefe79/.gitea/workflows/scripts/build-activity-log.sh"🔧 read:
.gitea/workflows/agent.yml🔧 bash:
git log --oneline -20🔧 bash:
git show fa3005b --stat🔧 bash:
git show fa3005b --no-color🔧 bash:
git show fa3005b:.gitea/workflows/scripts/build-activity-log.sh | cat -A | sed -n '48,58p'🔧 bash:
git show 1db36d4:.gitea/workflows/scripts/build-activity-log.sh | cat -A | sed -n '48,58p'tokens — input 293832 (fresh 293832 · cache 0w / 0r) · output 1237 · reasoning 0 · subscription