Found while auditing the harness against the capability list.
State
$ curl -s localhost:8790/api/v1/settings/mcp-servers | jq '.data[]|{name,auth_status}'
editai -> not_required
exa -> not_required
bright-data -> authenticated
linear -> auth_required <-- never completed
And the agent manifest doesn't reference it:
mcp_servers: ['editai', 'exa', 'bright-data']
Why it exists
linear was attached in #3 to prove the OAuth path works: the harness registers itself as a client via dynamic client registration, the turn pauses with an authorize URL, and the editor renders a Connect button. That demo succeeded and the connector was left behind.
The problem
It's in an in-between state that reads as broken rather than as a demo. A reader querying the settings sees a connector stuck at auth_required, with nothing indicating that's expected. And since it isn't on the agent, it does nothing regardless of whether it's authorized.
Options
- Remove it.
setup.ts only attaches what EDITAI_CONNECTORS names, so dropping it from the default list is a one-line change. The OAuth path stays documented in the README and reproducible with EDITAI_CONNECTORS=exa,linear.
- Keep and document it as a deliberate demo of the unauthorized state, so
auth_required reads as intended rather than as breakage.
Preference is (1): the capability is proven by being reproducible, not by leaving a half-connected connector in the settings.
Co-Authored-By: qodo-code-review[bot] <151058649+qodo-code-review[bot]@users.noreply.github.com>
Found while auditing the harness against the capability list.
State
And the agent manifest doesn't reference it:
Why it exists
linearwas attached in #3 to prove the OAuth path works: the harness registers itself as a client via dynamic client registration, the turn pauses with an authorize URL, and the editor renders a Connect button. That demo succeeded and the connector was left behind.The problem
It's in an in-between state that reads as broken rather than as a demo. A reader querying the settings sees a connector stuck at
auth_required, with nothing indicating that's expected. And since it isn't on the agent, it does nothing regardless of whether it's authorized.Options
setup.tsonly attaches whatEDITAI_CONNECTORSnames, so dropping it from the default list is a one-line change. The OAuth path stays documented in the README and reproducible withEDITAI_CONNECTORS=exa,linear.auth_requiredreads as intended rather than as breakage.Preference is (1): the capability is proven by being reproducible, not by leaving a half-connected connector in the settings.
Co-Authored-By: qodo-code-review[bot] <151058649+qodo-code-review[bot]@users.noreply.github.com>