Issues with re-triggering workflows and rapid token consumption in gemini-cli on GitHub Actions

Description

I’ve been using gemini-cli locally and I’m very satisfied with the results – it works quickly and efficiently.
I wanted to test it in a GitHub Actions environment, so I added the integration to my private repository using /setup-github.

The first run worked perfectly:
I mentioned @gemini-cli in a PR comment, and the workflow was successfully triggered. It implemented the changes I requested without any issues.

The problem occurs when I try to request changes again in the same PR.
When I mention @gemini-cli a second time, I get the message:

@tatarysh I've received your request and I'm working on it now! 🤖

…but the workflow completes without making any changes to the code.
I tried again, with the same result.

Interestingly, if I post a request in a comment inside an existing issue, it sometimes works.
However, on the next request in the same issue, nothing happens again – the workflow runs for a few minutes and then finishes without any changes.

This forces me to jump back and forth between PRs and issues just to get updates applied.

---

Steps to Reproduce

1. Create a PR and mention @gemini-cli in a comment → works as expected.
2. In the same PR, mention @gemini-cli again and request additional changes.
3. Observe that the workflow runs but no code changes are made.
4. Post a request as a comment inside an existing issue → sometimes works, sometimes does not.
5. If it works the first time in that issue, repeat the request in another comment → again, no changes are made.

---

Expected Behavior

• Ability to trigger @gemini-cli multiple times in the same PR or issue to apply iterative changes.
• Consistent behavior across both PRs and issues.

---

Actual Behavior

• The first trigger in a PR or issue works as expected.
• Subsequent triggers in the same PR or issue complete without making any changes, despite the bot message confirming that it’s "working on it".

---

Additional Notes

• I am currently using the free version of gemini-cli.

• Token consumption on GitHub Actions seems unusually high.

  • Locally, I can process ~1M tokens in a whole day.
  • In GitHub Actions, just a few simple requests consume 5M tokens.

• Sometimes the workflow generates a response.md file with a summary of what was added and commits it to the repository — but this does not always happen.

No source file or test is named. Start by reproducing the /setup-github integration and repeated @gemini-cli comments in the same PR and issue, then inspect the resulting GitHub Actions workflow runs and token usage. Done means subsequent requests consistently apply changes in both contexts without unexplained token consumption.