# Improve Agent UI organization or documentation

**URL:** <https://forum.cursor.com/t/improve-agent-ui-organization-or-documentation/176892>\
**Category:** Feedback\
**Tags:** projects, origin, cloud-agents\
**Created:** [October 31, 2026, 5:26pm UTC](https://forum.cursor.com/t/improve-agent-ui-organization-or-documentation/176892 "2026-10-31T17:26:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![BryanZ](https://avatars.discourse-cdn.com/v4/letter/b/5f9b8f/32.png) [@BryanZ](https://forum.cursor.com/u/BryanZ)\
**Post date:** [October 31, 2026, 5:26pm UTC](https://forum.cursor.com/t/improve-agent-ui-organization-or-documentation/176892/1 "2026-10-31T17:26:57Z")

</div>

I have run into a significant amount of difficulty figuring out the difference between the different chat/agents. I’m starting chats and running into unexpected permission/access walls, not being able to move chats, create Origin repos etc.

- ‘start-from-scratch’ is only available from ‘New Chat’
- Origin repo’s can only be created by agent with ‘start-from-scratch’
- New Projects and No Repo chats start in vm’s without access to Origin or other remote

Documentation seems to state that Projects need a remote to for checkouts to run actions against, so it doesn’t make sense that starting a Project chat, instead of New Chat start-from-scratch, does not create an origin repo or given access to Origin to be able to create an Origin repo.

I think agents should just be able to be started as local or cloud workers. Any agent should be able to be reassigned as a local or cloud worker and any agent should be able to create an Origin repo or connect to another remote and select the local workspaces needing to be associated for the task.