You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
After connecting Linear via Composio, the user expects the system to know about their projects. Today it doesn't: even with a healthy Linear connection, the agent falls back to asking the user to manually describe the project (current status, owners, deployment, branches) — defeating the purpose of connecting Linear in the first place.
Describe the solution you'd like
A guided import flow that closes the loop from "Linear is connected" to "OpenLoomi knows my project":
After Linear OAuth succeeds, surface an "Import project context" entry point in /connectors and as a quick-action in the chat composer.
UI flow:
Pick a workspace (auto-detected from the OAuth account by default).
Pick a project (or issue set, e.g. MET-17, MET-19) from a paginated list.
System pulls: project name/description, current cycle/iteration, in-progress issues with assignees + states, recent decisions (PR descriptions, comments), branches that mention the project, and any deployment/environment hints from issue templates.
Memory is written to data/memory/projects/<slug>.md (long-term, cross-session).
Describe alternatives you've considered
Auto-import on first connect without preview. Rejected: too aggressive — users may have multiple workspaces and want to scope explicitly.
A free-form chat prompt to "tell me about your project". Already supported today and is exactly the workaround we want to eliminate.
Additional context
Linear is already a canonical Loop source (SignalType.linear_issue in apps/web/lib/loop/types.ts:267) and #360 already handles multi-account. The signal-pull infrastructure is in place; what's missing is the UI to bootstrap a project memory from it.
Is your feature request related to a problem? Please describe.
After connecting Linear via Composio, the user expects the system to know about their projects. Today it doesn't: even with a healthy Linear connection, the agent falls back to asking the user to manually describe the project (current status, owners, deployment, branches) — defeating the purpose of connecting Linear in the first place.
Describe the solution you'd like
A guided import flow that closes the loop from "Linear is connected" to "OpenLoomi knows my project":
/connectorsand as a quick-action in the chat composer.data/memory/projects/<slug>.md(long-term, cross-session).Describe alternatives you've considered
Additional context
Linear is already a canonical Loop source (
SignalType.linear_issueinapps/web/lib/loop/types.ts:267) and#360already handles multi-account. The signal-pull infrastructure is in place; what's missing is the UI to bootstrap a project memory from it.