Repository navigation
Manage project service connections in the dashboard - #854
Conversation
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
|
|
||
| {activeTab === 'connections' && project ? ( | ||
| <div className="space-y-5"> | ||
| <ManagedProjectServiceConnections projectId={project.project.id} /> |
There was a problem hiding this comment.
🟡 Empty projects cannot manage service connections
When a project has no agents, ProjectDetail returns an empty state instead of rendering the new connections panel. Owners cannot attach a shared account until the project has an agent.
Learn more
The project route decides whether to render the detail page. With no agents, ProjectDetail renders only Settings or an empty state. This project-wide panel never mounts for an empty project.
Example: Create an empty project and open /projects/prj_1/connections. The page shows an initialization message instead of the shared service connections panel, although an OAuth account is already available.
Recommended fix: Permit the project Connections tab to render without an agent in ProjectDetail, and gate only the agent-specific panels in ManagedAgentDetail.
Was this helpful? React with 👍 or 👎 to provide feedback.
1 participant
Adds explicit project-wide OAuth attachment controls to Project → Connections.
Decisions and risks:
Review map:
ProjectServiceConnections.tsx: panel and mutationsapi.ts: validated list/attach/detach clientlinear-setup.ts: single-environment row derivationVerification:
Design: diggerhq/serverless-agents-ws#39