Bennett offered a number of suggestions for improving Claude Code, three stood out:
A markup tool: I wish I could easily point to things: screenshots, UI glitches, layout issues, or share a whiteboard with Claude. Currently, all of these must be described completely in text. Often twice. Sometimes three times. I’ve tried uploading a marked-up screenshot, but with mixed success. A markup tool would be enormously helpful.
We need a larger context window. In regular Claude, the current 200k is being upgraded, in beta test now, at the 1M mark! But I think Claude Code’s limits are much lower. I see errors like Error: File content (27931 tokens) exceeds maximum allowed tokens (25000); 25,000 is pretty small when dealing with entire source code files.
Unprompted Git commits (This is the worst surprise.) Claude Code sometimes commits to Git without being asked. And even worse: it may commit before the change is tested; I don’t like checking in obviously broken code.
Mark Bennett on Using Claude Code for Application Development
(skmurphy.com)2 points by skmurphy 20 hours ago | 1 comments
Comments
A markup tool: I wish I could easily point to things: screenshots, UI glitches, layout issues, or share a whiteboard with Claude. Currently, all of these must be described completely in text. Often twice. Sometimes three times. I’ve tried uploading a marked-up screenshot, but with mixed success. A markup tool would be enormously helpful.
We need a larger context window. In regular Claude, the current 200k is being upgraded, in beta test now, at the 1M mark! But I think Claude Code’s limits are much lower. I see errors like Error: File content (27931 tokens) exceeds maximum allowed tokens (25000); 25,000 is pretty small when dealing with entire source code files.
Unprompted Git commits (This is the worst surprise.) Claude Code sometimes commits to Git without being asked. And even worse: it may commit before the change is tested; I don’t like checking in obviously broken code.