Skip to content

[FEATURE] Update context when moving Cowork task into project #53197

Description

@mischacoster

Preflight Checklist

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

Problem Statement

I find myself often starting a Cowork task, only later realizing it actually belongs in a Cowork project. So I move the task into the project. But I noticed that when continuing the task, the task context is restricted to the initial task context (outside of the project), even though from that point outputs WILL be placed in the project output folder. I couldn't find any documentation on this. There is some documentation on moving a chat OUTSIDE of a project, but not vice versa.

Proposed Solution

Would be great to have the chat/task context 'resetted' when the task is moved into a project, and re-initialized with the first follow-up interaction inside the project.

Alternative Solutions

I guess an alternative would be to 'copy' the taks into a project, but only transferring the initial message so that the entire conversation can be re-started with project context, tools and mounts available. But that feels like a 'workaround', because you'll end up with two chats about the same project, one half underway but without relevant context and instruction, and one starting over with the project context.

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

No response

Additional Context

No response

Activity

  1. mischacoster commented on Apr 25, 2026

    @mischacoster
    Author

    Cross-link: #43528 addresses the same underlying problem from a different angle (convert a task into a new project, instead of moving it into an existing one).

    Both stem from the same workflow — a task grows beyond its initial scope and needs project-level context (working dir, instructions, mounts, MCP, skills, project memory). #43528 is the "no project yet" branch; this issue is the "project already exists" branch. Worth triaging together.

  2. github-actions commented on May 29, 2026

    @github-actions

    Closing for now — inactive for too long. Please open a new issue if this is still relevant.

  3. github-actions commented on Jul 29, 2026

    @github-actions

    This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

  4. locked as resolved and limited conversation to collaborators on Jul 29, 2026
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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions