Skip to content

feat(issues): add --status flag to issues update command#94

Merged
Palash Shah (Palashio) merged 2 commits into
mainfrom
feat/issues-reopen-status-flag
May 1, 2026
Merged

feat(issues): add --status flag to issues update command#94
Palash Shah (Palashio) merged 2 commits into
mainfrom
feat/issues-reopen-status-flag

Conversation

@Palashio
Copy link
Copy Markdown
Contributor

@Palashio Palash Shah (Palashio) commented May 1, 2026

Adds --status open|completed|ignored to langsmith project issues update so agents and users can explicitly change an issue's status from the CLI.

The primary use case is reopening a resolved issue when new trace evidence is found:

langsmith project issues update <id> --status open

This is the CLI half of the reopen feature. The backend companion PR (langchain-ai/langchainplus#23964) auto-reopens issues when a run is linked via issues runs add, but the explicit --status flag is needed for cases where the agent wants direct control over issue status.

Test Plan

  • langsmith project issues update <id> --status open reopens a completed issue
  • langsmith project issues update <id> --status completed resolves an open issue

Adds --status open|completed|ignored to `langsmith project issues update`
so agents and users can explicitly change an issue's status, including
reopening a resolved issue when new evidence is found.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Agents should only reopen issues, never close them. Tightens validation
to reject any value other than 'open' with a clear message directing
users to the UI for closing.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@Palashio Palash Shah (Palashio) merged commit b83a29d into main May 1, 2026
10 checks passed
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.

2 participants