Earlier quoted context omitted.
The model is usually so confused after a /compact I also prefer a /clear. I set up my directives to maintain a work log for all work that I do. I instruct Claude Code to maintain a full log of the conversation, all commands executed including results, all failures as well as successes, all learnings and discoveries, as well as a plan/task list including details of what's next. When context is getting full, I do a /cl…
The trick is to parametrize the /compact. Something like "/compact focus on the XZY, the next steps will be FOOBAR, and keep a high level summary of BARFOO" That makes the compaction summary a lot more focused and useful. edit: But a work log/PRD is essential regardless!
Claude Code: Now in Beta in Zed
411–420 of 431 posts
Re: Claude Code: Now in Beta in Zed
#412Earlier quoted context omitted.
The model is usually so confused after a /compact I also prefer a /clear. I set up my directives to maintain a work log for all work that I do. I instruct Claude Code to maintain a full log of the conversation, all commands executed including results, all failures as well as successes, all learnings and discoveries, as well as a plan/task list including details of what's next. When context is getting full, I do a /cl…
The trick is to parametrize the /compact. Something like "/compact focus on the XZY, the next steps will be FOOBAR, and keep a high level summary of BARFOO" That makes the compaction summary a lot more focused and useful. edit: But a work log/PRD is essential regardless!
Re: Claude Code: Now in Beta in Zed
#413Earlier quoted context omitted.
I have recently been using Zed much more than cursor. However, the autocomplete is literally the only thing missing, and when dealing with refactors or code with tons of boilerplate, its just unbeatable. Eagerly awaiting a better autocomplete model and I can finally ditch Cursor.
Out of curiosity, why not just stick to Cursor instead?
That said, vscode's UX sucks ass to me. I believe it's the best UX for people that want a "good enough and just works" editor, but I'm an emacs/vim (yes both) guy and I don't like taking my hands off the keyboard ever. Vscode just doesn't have a good keyboard only workflow with vim bindings like emacs and nvim do.
Re: Claude Code: Now in Beta in Zed
#414Earlier quoted context omitted.
The trick is to parametrize the /compact. Something like "/compact focus on the XZY, the next steps will be FOOBAR, and keep a high level summary of BARFOO" That makes the compaction summary a lot more focused and useful. edit: But a work log/PRD is essential regardless!
I’ve been using PRD specs at kick things off, but curious about how to a “work log”. Are there examples of how to do this with CC?
Re: Claude Code: Now in Beta in Zed
#415Earlier quoted context omitted.
its a bad anti-pattern that trades developer convenience for performance, UX etc. Its fair to hate on it With the advent of coding agents, I really hope we see devs move away - back to the traditional approach of using native frameworks/languages as now, you can write for 1 platform and easily task AI to handle other platforms.
This will never happen and it's a bizarre, legacy fantasy, borne of a fixed imaginary ideal of what computing should be. Programming will continue to move in the direction of ease-of-use and every time I see an out-of-topic reference to Electron in this forum I feel insane, like I'm fighting upstream. You will not see this - you will see more Electron apps, because that is the modern way of building cross-platform ap…
> My experience in Atom always felt like bending over backwards to try to achieve something that in principle should have been simple. Lay out some lines and read the position of the cursor at this spot in between these two characters. That seems fundamentally doable and yet it always felt like the tools were not at our disposal. They were very far away from what we wanted to do.
> Nathan: It was a nightmare. I mean, the ironic thing is that we created Electron to create Atom, but I can't imagine a worse application for Electron than a code editor, I don't know. For something simpler, it's probably fine, the memory footprint sucks, but it's fine. But for a code editor you just don't have the level of control I think you need to do these things in a straightforward way at the very least. It's always some... backflip.
Re: Claude Code: Now in Beta in Zed
#416Also love Zed, but sigh, it's VC funded. We all know how this is going to end. Best VIM mode ever implemented in a (non vim) app. I use it as my 2nd editor (most of the time in Jetbrains products). I just hope I'm wrong about the medium term impact of the VC funding but rushing AI AI AI out seems to be a sign of that rather than fixing fundamental issues that remain such as the ugly font rendering.
- Zed: VC funded open source
- Sublime Text: indie closed source
None is ideal, but I guess we all know why.
Re: Claude Code: Now in Beta in Zed
#417I love Zed but this has all the hallmarks of something being totally rushed out the door. It works off the Claude Code SDK, which mean it doesn't support many of the built in slash commands - it doesn't support /compact, which is 100% necessary because when you use this implementation enough, you'll eventually get a "Prompt too long" error message with no ability to do anything about it. Since you can't see how far y…
I found the interface very nice but quickly ran up against limitations on prompt length (it wasn't that long) for example. I am used to being able to give detailed instructions, or even paste in errors/tracebacks.
I'll check back in in a few months.
Re: Claude Code: Now in Beta in Zed
#418Earlier quoted context omitted.
> I don't see why most editors should behave like hand crafted musical instruments when in reality they are much more akin to high quality knives in a kitchen (sure you have your favorite knife set and bring it from job to job, but at the end of the day you can be just as productive with a different knife when necessary). This is such a poor analogy. Yes, a good chef can make do with a different knife, but there is a…
As someone who is in the position to see what the next really disruptive innovation is, you're quite right that there exist much, much better ways to write and collaborate on code. Flying leaps of innovation to Zed's tiny shuffle-steps.
Re: Claude Code: Now in Beta in Zed
#419Earlier quoted context omitted.
The model is usually so confused after a /compact I also prefer a /clear. I set up my directives to maintain a work log for all work that I do. I instruct Claude Code to maintain a full log of the conversation, all commands executed including results, all failures as well as successes, all learnings and discoveries, as well as a plan/task list including details of what's next. When context is getting full, I do a /cl…
The trick is to parametrize the /compact. Something like "/compact focus on the XZY, the next steps will be FOOBAR, and keep a high level summary of BARFOO" That makes the compaction summary a lot more focused and useful. edit: But a work log/PRD is essential regardless!
I think both /compact and /clear are valuable / have their own use cases.
my small mental mode: - really quick fix / need to go over board with context -> just /compact + continue pushing - next phase -> ask for handover document or update worklog, and then send fresh one to new phase.
Re: Claude Code: Now in Beta in Zed
#420Earlier quoted context omitted.
I was somewhat surprised to find that Zed still doesn't have a way to add your own local autocomplete AI using something like Ollama. Something like Qwen 2.5 coder at a tiny 1.5b parameters will work just fine for the stuff that I want. It runs fast and works when I'm between internet connections too. I'd also like to see a company like Zed allow me to buy a license of their autocomplete AI model to run locally rathe…
> I'd also pay for something in the 10-15b parameter range that used more limited training data focused almost entirely on programming documentation and books along with professional business writing. Unfortunately, pretraining on a lot of data (~everything they can get their hands on) is needed to give current LLMs their "intelligence" (for whatever definition of intelligence). Using less training data doesn't work…
Maybe it also needs some amount of other training data for basic speech patterns, but I’d again show IBM Granite as an example that professional and to-the-point LLMs are possible.