Dasha Adushkina activity https://gitlab.com/dashaadu 2026-03-19T21:19:58Z tag:gitlab.com,2026-03-18:5219603187 Dasha Adushkina opened epic #21412: Show credit consumption in agentic chat responses at GitLab.org 2026-03-18T21:47:43Z dashaadu Dasha Adushkina tag:gitlab.com,2026-03-18:5218861210 Dasha Adushkina commented on issue #593279 at GitLab.org / GitLab 2026-03-18T17:44:39Z dashaadu Dasha Adushkina

@shinya.maeda I'll answer these on the product side 🤝 and your interpretation is right on all points, confirming them here:

  • "Workspace-level" = project-level. Correct. In the Web UI there's no workspace concept, so AGENTS.md at the project root (or .gitlab/agents.md) applies to all conversations in that project.
  • Subdirectory-level: we can make it out of scope for this issue. Your examples for how subdirectory context would be determined from the URL make sense, but this adds meaningful complexity (tree-walking, caching, Gitaly calls). Let's scope this issue to project-level only and track subdirectory support as a follow-up.
  • User-level: skip in Web UI. No local filesystem in a browser, so this is IDE-only. We'll document it as a limitation.
  • One additional decision that came out of the related chat-rules.md discussion (#593392 (comment 3166099842)): AGENTS.md rules should be re-evaluated on each message based on the user's current project context, not locked at conversation start. If a user switches projects mid-conversation, the new project's AGENTS.md should apply. This keeps behavior consistent across both features.

/cc @juan-silva

tag:gitlab.com,2026-03-18:5218614409 Dasha Adushkina commented on issue #593279 at GitLab.org / GitLab 2026-03-18T16:47:02Z dashaadu Dasha Adushkina

@erran tagging you for visibility on the agents.md work Shinya is working on.