HenriNext

Having 4 separate limits that all are opaque and can suddenly interrupt work is not ok.

We don't know what the limits are, what conditions change the limits dynamically, and we cannot monitor our usage towards the limits.

1. 5 hour limit

2. Overall weekly limit

3. Opus weekly limit

4. Monthly limit on number of 5 hour sessions

Claude Code can already show diffs in JetBrains IDEs and VSCode ('/ide' command connects the CLI/TUI to plugin/extension running in the IDE-side).

It can also access the IDEs' real-time errors and warnings, not just compile output ('ideDiagnostics' tool), see your active editor selection, cursor position, etc.

Thanks, one more clarification please. The heading of point #3 seems to mention Google Workspace: "3. Login with Google (for Workspace or Licensed Code Assist users)". But the text content only talks about Code Assist: "For users of Standard or Enterprise edition of Gemini Code Assist" ... Could you clarify whether point #3 applies with login via Google Workspace Business accounts?

It has fine grained permissions configuration file. And every permission question has three answer options: "yes", "yes and don't ask again", "no". And it has option '--dangerously-skip-permissions'. Out of all 20+ AI code tools I've tried/used, Claude Code has the best permission options.

AI Studio uses your API account behind the scenes, and it is subject to normal API limits. When you signup for AI Studio, it creates a Google Cloud free tier project with "gen-lang-client-" prefix behind the scenes. You can link a billing account at the bottom of the "get an api key page".

Also note that AI studio via default free tier API access doesn't seem to fall within "commercial use" in Google's terms of service, which would mean that your prompts can be reviewed by humans and used for training. All info AFAIK.

Interesting idea. But LLMs are trained on vast amount of "code as text" and tiny fraction of "code as AST"; wouldn't that significantly hurt the result quality?

Same experience. Especially the "step" comments about the performed changes are super annoying. Here is my prompt-rule to prevent them:

"5. You must never output any comments about the progress or type of changes of your refactoring or generation. Example: you must NOT add comments like: 'Added dependency' or 'Changed to new style' or worst of all 'Keeping existing implementation'."

> I know half a dozen startups that let you pass in some set of keys and "build a multi-agent system"

Could you give names of those startups?

And yeah, Hugging Face is very much venture funded -- they had a modest 4.5b valuation in the last round.. (I just didn't know they had some competing product).

Thanks. Do you have a source/reference for the venture funding? (Perplexity searched 101 sites and concluded that it didn't find any public information about funding)

Curious.. which 'bring your own keys' -style competitors have venture funding?

"The need to direct boot shouldn't really be a concern", says the same man who said that the lack of expansion slots on the trashcan Mac Pro 2013 shouldn't really be a concern because you have a lot of Thunderbolt ports.

Funny that GTK was originally created for GIMP (GTK was acronym of "Gimp ToolKit"), and now they are 10 years behind the latest version of their own toolkit.