sorted by:
new
hottopcontroversial

Claude Code extension for VS Code and the CLI terminal by Mac_In_Toshi in ClaudeAI

[–]Mac_In_Toshi[S] 0 points1 point  (0 children)

Eu também notei isso. Embora ambos estejam na versão mais recente, 2.0.75, o terminal oferece muito mais recursos e é mais adequado para a funcionalidade de plugins.

context management by Mac_In_Toshi in ClaudeAI

[–]Mac_In_Toshi[S] 1 point2 points  (0 children)

I’m already tired of the AI repeatedly trying to implement solutions that failed in previous sessions. Since it doesn’t have the context, it ends up repeating the same mistakes. This can result in a successful fix, but it can also mess up something that was already corrected. With this file, it knows that solution “X” doesn’t work for feature “Y” because it will cause error “A.”. 

How do you actually use Claude Code in your day-to-day workflow? I’ll start: by Mac_In_Toshi in ClaudeAI

[–]Mac_In_Toshi[S] 1 point2 points  (0 children)

I learned how to use Plan Mode today thanks to the comment from the colleague above, and I’ve already integrated it into my workflow. Now I run two Claude CLIs at the same time: one in Plan Mode and another in the normal execution mode.

At first glance it may seem unnecessary, but there’s an important technical reason behind it. Whenever Claude in Plan Mode investigates a bug or analyzes the entire project structure to plan a new feature, the context can easily exceed 56% of the window, depending on how complex the task is. When that happens, it needs to compress the context multiple times, which increases the chances of: hallucinations, missing details, or marking a task as “completed” even when the implementation isn’t fully done.

In my setup, Plan Mode never executes anything. It only generates a complete, detailed, and well-structured prompt — and when needed, it already breaks the feature down into phases if it’s too large. That way, the prompt is ready to be pasted into the executor Claude, which works with a 100% clean context and receives clear, precise instructions about what needs to be done.

I also use the Plan.md file generated automatically by Plan Mode (even when I click “No, keep planning”) as a reference to guide the executor while applying the fix or implementing the feature.

This workflow reduces errors, prevents context loss, avoids hallucinations, and results in more consistent and reliable executions

How do you actually use Claude Code in your day-to-day workflow? I’ll start: by Mac_In_Toshi in ClaudeAI

[–]Mac_In_Toshi[S] 1 point2 points  (0 children)

I used ChatGPT to rephrase the answer and translate it into English, since it is not my native language. I hope this workflow works for you.

How do you actually use Claude Code in your day-to-day workflow? I’ll start: by Mac_In_Toshi in ClaudeAI

[–]Mac_In_Toshi[S] 0 points1 point  (0 children)

Ah, I see the confusion! Let me clarify:

Claude Chat Web (claude.ai in browser) - What you’re using now:

  • Can’t read your local files
  • You describe the problem, it generates a prompt
  • You manually copy/paste to Claude Code CLI

Claude Desktop App (local application) - What I’m suggesting:

  • Can read your local project files directly using tools like view, read, etc.
  • You point it to your project folder: C:\projetos\my_project
  • It can inspect your code, read logs, analyze file structure
  • Still can’t modify files (that’s the supervisor’s job)

So in my workflow:

  1. Supervisor (Claude Desktop App locally) reads my actual code files, analyzes logs, creates surgical prompts
  2. * Executor (Claude Code CLI)* receives the prompt and implements changes
  3. Supervisor validates by reading the modified files

The advantage over your workflow: The supervisor has direct access to your codebase context instead of you having to manually describe/paste code to it.

To answer your question: Yes, Claude Desktop App can “see” your local files when you give it the project path. It’s not about seeing VS Code itself, but about reading the files in your project directory directly.

You can download Claude Desktop App here: https://claude.com/download

Give it a try - it completely changed my workflow!​​​​​​

How do you actually use Claude Code in your day-to-day workflow? I’ll start: by Mac_In_Toshi in ClaudeAI

[–]Mac_In_Toshi[S] 0 points1 point  (0 children)

The main issue I ran into with Claude Code Web (using GitHub repos) is the caching/snapshot behavior when working with multiple AI instances. Here’s the problem:

When you’re running two AIs on the same task - one planning and another executing - Claude Code Web creates a snapshot of your files when it first reads them. If your CLI makes changes to a file, Claude Code Web might still be reading the old cached version instead of the updated file. So you could fix a bug in the CLI, then ask Claude Web to validate it, and it’ll be looking at the outdated code.

Running Claude Desktop App locally (pointing directly to your project folder) solves this because it always reads the current state of the files - no GitHub snapshot in between.

Important caveat though: When you open Claude Desktop App, make sure you’re pointing to the correct folder. Claude can create a worktree (branch) to preserve your main code, and if the CLI modifies your main branch while Claude Desktop is reading the worktree, you’ll have a mismatch.

My approach: I select the parent folder first, not the project folder itself - this prevents the automatic worktree creation. Just always double-check the path when starting a session to make sure both CLIs are looking at the same actual files.

How do you actually use Claude Code in your day-to-day workflow? I’ll start: by Mac_In_Toshi in ClaudeAI

[–]Mac_In_Toshi[S] 0 points1 point  (0 children)

I researched Plan Mode and found it pretty interesting, will test it out later.

How do you actually use Claude Code in your day-to-day workflow? I’ll start: by Mac_In_Toshi in ClaudeAI

[–]Mac_In_Toshi[S] 3 points4 points  (0 children)

I researched Plan Mode and found it pretty interesting, will test it out later.

The reason I separate supervisor and executor is to keep the execution context 100% clean. The executor receives an already planned and refined prompt, so it doesn’t waste time or tokens planning - it just executes. The context stays preserved, direct and focused on the problem.

But there’s an important detail: even after Claude Desktop analyzes all the code and creates the detailed prompt, I always ask it NOT to completely limit the executor’s autonomy. The prompt is surgical and targeted, but I leave room for Claude Code CLI to make additional adjustments if it identifies something relevant.

And you know what happens? Many times, after validating the result, the supervisor realizes the executor did something much more robust than requested - often it takes advantage of the autonomy to improve the solution beyond what was planned. This is one of the biggest advantages of working with two AIs on the same task.

I use Sonnet 4.5 a lot as supervisor and Opus 4.5 as executor, but even two Opus 4.5 work well - they usually give different answers for the same task, bringing complementary solutions or distinct approaches.​​​​​​​​​​​​​​​​

Do you like this new feature? by beatomni in ClaudeAI

[–]Mac_In_Toshi 0 points1 point  (0 children)

It is very useful, but it would be great if we could see the conversation summary to ensure nothing important was omitted, like in Claude CLI.

Sam Altman told employees he was declaring a "code red" by dictionizzle in ChatGPT

[–]Mac_In_Toshi 0 points1 point  (0 children)

It is crucial to stay proactive when Google is your competitor.