Skip to content

[Enhancement] One-click import: pick a Linear workspace / project / issue and pull context into OpenLoomi long-term memory #414

Description

@Peefy

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":

  1. After Linear OAuth succeeds, surface an "Import project context" entry point in /connectors and as a quick-action in the chat composer.
  2. 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.
    • System drafts a structured project memory and offers the preview → confirm → save flow (see feat: remove Discord integration completely #5, feat: enhance file previews with CSV support and drawer components #6).
    • 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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agentAlloomi agentarea/connectorsIssues in the openloomi Connectors surface (native 7 platforms + composio bridge)enhancementNew feature or requesthigh-priorityAlloomi high-priority

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions