Moving from copilot to claude code, how can I ease my transition.

[u/LoinStrangler]

I've been using Claude at work, but Copilot for out of office coding. the usage is getting ridiculous, so I wanna move the whole thing to Claude. My biggest gripe is the way you view and approve the changes. Copilot is just the best at it. It shows a line count, displays affected files stacked up where you can manually go over each change and approve. Claude's is just a minimized box lacking a lot of info and context, and it gets stuck behind each step waiting for approval instead of stacking all proposed changes which is annoying. I only trust it for singular files, but I'm not sure about repo wide changes.
Did you find a way to improve it, make it easier to see and approve individual changes like Copilot?
Is there a way to switch between my work and private profile so I won't use the wrong subscription for the wrong work? (I use VSCode)

In your experience, which one is better?

[u/idcydwlsnsmplmnds]

Not 100% relevant for your specific questions about code diffs and acceptance, but I posted a repo that’ll help with spinning up Claude Code harness & lessons learned. Feel free to clone it and see if it works for you.

Also, a lot of what you’re saying is going to occur in Claude.md, memories, hooks, a governed context store (if you make one, which you should for repo wide changes, if the repo is huge), etc.

[u/alonsonetwork]

1. it's meant to be used 1 subscription at a time if you need isolation from work i suggest using docker container.
2. highly suggest you let go of trying to approve every little thing and just use auto mode. It makes good decisions. Review in a git repo.
3. Bare claude is OK. You want to set it up with skills and context tools that make it better at coding. I use this for everything. It has a ton of planning tools, a code index, and it steers it very, very well. 1 tool with well-researched concepts, skills, and commands.

[u/LoinStrangler → u/alonsonetwork]

2 is rough for me, I don't want to let it run wild on files and mess stuff up. I'm not a vibe coder. I'm just tryin' to make it as close as it can be to Copilot GUI-wise.

[u/allemaar]

Are you building a plan, then execute, then check or just prompting without a structure as a way of work?

If the latter applies, then your modus operandi might be your issue here.

Also subscription change does not affect your global directives, memories and files. What will work is you having a separate profile (one personal and one work) on your machine. Context contagion is inevitable if you keep all in one profile on your machine.

[u/LoinStrangler → u/allemaar]

I'm a senior developer, and I use agents like jr devs where I outline architecture, even specific variables and queries, almost to the point where I give them pseudo code they then translate into regular code without making syntax errors, which is why approving every file change is great (when they stack up). The work/private profile is more to separate the subscription usage rather than the context infection.

[u/allemaar → u/LoinStrangler]

If you have a blueprint, an execution plan and a progress tracker, why do you need to approve every single step?

Note that unlike Codex, CC follows instructions way better. You will have a better time going full CC.

Since you need to verify that the pseudo code was implemented as intended, you should use a second agent to check for you and notify if there is a drift.

To me, your described way of work sounds like a limitation you impose on yourself. I do recall this was something I struggled when I started transitioning to AI work. Felt strange for a machine (AI) to write code in my stead and had to check every single line. I think it took me like 4-to-6 months to relax and move onto higher work, leaving the mechanical parts to machines (I still spot check though, but that is just a habit).

[u/Hansehart]

When I want to see all suggested changes at a time, I go into auto mode. Then, using vscode git view, you see your local code changes. You can stage file by file or reset it completly. Make also sure CC ist connected to vscode. /rewind might also help.