[FEATURE] Bridge Claude Projects and Claude Code (search, linking, GitHub parity)

Status Open
Maintainer reply None cached
Activity 0 comments · opened Sep 12, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Feature request: Bridge Claude Projects and Claude Code (search, linking, GitHub parity)

Submitted by: Chandra Shekhar Sengupta, Technicise (Kolkata, India) — B2B healthcare IT & training
Plan: Max · Platforms: Claude Desktop (Windows), claude.ai web, Android app

The workflow gap

I run long-lived business workstreams (conference research, vendor evaluations, product planning) in Claude Projects because Projects give me: organized context, project memory, and — critically — search over past chats in the mobile app, which is where I work while travelling.

But my workstreams live in private GitHub repos (issues as a field-notes knowledge base — 600+ issues across trade fairs; markdown research docs). For GitHub, Claude Code is far more fluent. So I'm forced to choose between organization (Projects) and repo fluency (Code), and I currently bridge them with a self-built MCP connector — workable, but this should be native.

Three concrete requests

1. Search in Claude Code on mobile

The mobile app has search for regular chats/Projects, but I cannot search my Claude Code sessions from mobile. This single gap pushes me back into Projects for anything I'll need to find later. Parity request: session search (titles + content) for Code sessions in the iOS/Android apps.

2. Link Claude Code sessions to a Claude Project

Let a Code session be attached to a Project so that:

  • The Project's context/knowledge and memory are available inside the Code session
  • Code sessions appear in (and are searchable from) the Project's history
  • Artifacts/files move between the two without manual export

Today these are two silos; my repo work in Code has no awareness of months of Project context about the same workstream, and vice versa.

3. First-class GitHub integration in Projects (or Project-aware Code)

Projects can attach a repo for context, but working on the repo (issues, labels, milestones, commits) from a Project conversation requires custom MCP connectors. Either bring Code-grade GitHub tooling into Projects, or make #2 seamless enough that the distinction stops mattering.

Why it matters

Small businesses run real operational systems on Claude + GitHub (in my case: event/CRM-style issue tracking, research docs, travel planning). The Projects/Code split forces workflow contortions that a linking layer would eliminate.

Proposed Solution

Three concrete requests

1. Search in Claude Code on mobile

The mobile app has search for regular chats/Projects, but I cannot search my Claude Code sessions from mobile. This single gap pushes me back into Projects for anything I'll need to find later. Parity request: session search (titles + content) for Code sessions in the iOS/Android apps.

2. Link Claude Code sessions to a Claude Project

Let a Code session be attached to a Project so that:

  • The Project's context/knowledge and memory are available inside the Code session
  • Code sessions appear in (and are searchable from) the Project's history
  • Artifacts/files move between the two without manual export

Today these are two silos; my repo work in Code has no awareness of months of Project context about the same workstream, and vice versa.

3. First-class GitHub integration in Projects (or Project-aware Code)

Projects can attach a repo for context, but working on the repo (issues, labels, milestones, commits) from a Project conversation requires custom MCP connectors. Either bring Code-grade GitHub tooling into Projects, or make #2 seamless enough that the distinction stops mattering.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗