[codex] fix linear issue listing#395
Merged
nicobistolfi merged 1 commit intoaliengiraffe:mainfrom Apr 6, 2026
Merged
Conversation
nicobistolfi
approved these changes
Apr 6, 2026
alangos
force-pushed
the
codex/fix-linear-cli-listing
branch
from
b753932 to
7d11b91
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
The Linear backend no longer calls
linear issue list --json, which is not supported by the Linear CLI. It now runslinear issue list, parses the issue ID column from the table output, and hydrates each item withlinear issue view <ID> --json.Why
The previous implementation depended on a CLI flag that the
linear issue listcommand does not accept, so listing open work items failed before Vigilante could evaluate any Linear issues.Impact
Vigilante can now enumerate Linear issues using the supported CLI workflow and still build the same
WorkItemdata shape expected by the rest of the app.Root cause
The integration assumed parity between
linear issue listand other Linear CLI commands that do support--json.Validation
I added focused tests for the list-table parsing and per-issue hydration flow.
I could not run
go testorgofmtin this environment because thegotoolchain is not installed.