Repository navigation
plat 620
| Field | Value |
|---|---|
| State | fixed on main |
| Priority | P2 |
| Product | app |
| Area | integrations |
| Summary | The Tools & secrets tabs said only Connected and Available, obscuring that both browse MCP integrations. |
User screenshot of Integrations → Tools & secrets: Connected, Available,
Secrets, Skills, Vault. The first two labels do not identify their content,
so the user asked to show MCP explicitly.
Rename the shared project tabs to Connected MCPs and Available MCPs, covering
Workflow, Crew, Code and Relay. Use the same labels in the standalone shared MCP
browser. Tab IDs, saved selection and connection actions stay compatible.
Update existing tab navigation checks to match the visible wording.
Validation: 35 existing checks passed across six integration, workspace and
workflow suites. The full frontend production build, TypeScript, release asset
validation and bundle budget passed. Targeted ESLint passes with the existing
Fast Refresh export-pattern rule excluded; its two diagnostics in
ProjectPluginsPanel.tsx are identical on unchanged origin/main.
Deployment is reserved for the user. On 2026-10-06 the user instructed the agent
not to deploy. Both pending deployment attempts were stopped while waiting for
active chats, and the deployment follow-up was deleted. Confida still runs
builder source 15cefc0a3af868bc34567be8cbe59ba5ee006f2c; this wording change
has not been activated there. The tested source is on main at
41639cff2f8171df125d06b8639e680cbb443722.
After the user deploys, verify the current public assets contain both labels.
Auto-synced from docs/ on main. Edit there, not here.