Skip to content

feat(agents): enforce run tokens for investigate again - #2099

Merged
mashkovd merged 1 commit into
mainfrom
feat/investigate-run-token-enforce
Oct 23, 2026
Merged

mashkovd merged 1 commit into
mainfrom
feat/investigate-run-token-enforce

Conversation

@mashkovd

Copy link
Copy Markdown
Member

Re-enables enforce for investigate after the rollback in #2086. Owner OK given 2026-10-23.

Why it is safe now

Rollback

Set MCTL_RUN_TOKEN_MODE back to observe, as in #2086.

🤖 Generated with Claude Code

mctl-api 4.117.0 binds investigate runs submitted without an
execution_id, which is what failed the first enforce attempt. Observe
then showed a run without an execution exchange successfully.
@claude

claude Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Claude finished @mashkovd's task in 16s —— View job


Review of PR #2099

  • Read the diff
  • Submit verdict

The change is a single env var flip in cwft-mctl-agents-investigate.yaml: MCTL_RUN_TOKEN_MODE goes from observe to enforce. The PR description gives live evidence and a one-line rollback, so I approved it. There were no P1, P2 or P3 findings.

I only read the diff. I did not run any checks.

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Single env var flip (MCTL_RUN_TOKEN_MODE observe->enforce) with live evidence and a documented one-line rollback.

@github-actions

Copy link
Copy Markdown
Contributor

Antigravity (agy) review — informational

Model: gemini-3.8-flash-high · commit c74a938.

No significant issues found.

@mashkovd
mashkovd merged commit e860141 into main Oct 23, 2026
25 checks passed
@mashkovd
mashkovd deleted the feat/investigate-run-token-enforce branch October 23, 2026 16:05
mashkovd added a commit that referenced this pull request Oct 24, 2026
Option (c) on mctlhq/mctl-agents#717: the investigator's MCP connection
(enforce since #2099) and, from mctl-agents 1.98.0, its own work-item REST
calls use the scoped investigate run token. With MCTL_TOKEN gone from the
container, the agent's tool subprocesses can reach only what that scope
admits, so investigate-bash moves from bypass-open to no-mctl-token.

The coverage check now accepts a no-mctl-token transport entry when its
surface maps no MCTL_TOKEN and runs at least the entry's
min_image_version, so this cannot go live on an image that still reads
MCTL_TOKEN for REST.

Refs mctlhq/mctl-agents#717, #1980
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant