Hey! The weakest part of Claude Code I think is that it's closed source and locked to Claude models only. If you are looking for inspiration, Roo is the the best tool atm. It offers far more interesting capabilities. Just to name some - user defines modes, the built in debug mode is great for debugging, architecture mode. You can, for example, ask it to summarize some part of the running task and start a new task with fresh context. And, unlike in Claude Code, in Roo the LLM will actually follow your custom instructions (seriously, guys, that Claude.md is absolutely useless)! The only drawback of Roo, in my opinion, is that it is NOT a cli.
I dunno what you would consider non trivial. I am building a diffing plugin for neovim. The experience is.. mixed. The fast progression at the start was impressive, but now as the code base have grown the issues show up. The code is a mess. Adding one feature breaks another and so on.
I have no problem in using the agent on code that I know very well, because I can stir it in the exact direction I want. But vibe coding something I don't fully understand is a pain.
Hi! Looks like a very interesting tool, as a stubborn cli-only user, I was pleased that there is cli version of this alongside the GUI verison. However, trying to look into the documentation of the cli has left me with a 404 page.
https://docs.xpipe.io/cli/man
Whoops, it seems like some links were not updated yet. That should be just https://docs.xpipe.io/cli
To preface that, the CLI is only very basic. The only real thing you can do with it is launch shell connections. For more advanced usage without the GUI, there is for example the Python API: https://docs.xpipe.io/guide/python-api
They should write a typescript-to-go transpiler (in typescript) , so that they can write their compiler in typescript and use typescript to transpile it to go.
> I'm excited to understand more about how aider creates a map of the repository and effectively compresses the information in ways similar to how I keep track of high level ideas.
Ok, I meant to say, I know about /map, but there is so much to explore here with an open source coding tool and LSP. It feels like you could build some very powerful ways to represent connections using a lot of cool tools that are in use inside our editors. More structured and more relevant that the poor representations I can keep inside my crappy head.
I do not disagree with your point, except, given the current state of US, it is hard to describe it as not repressive. I understand it's a spectrum. I checked on Wikipedia - abortion is legal in China. That's one right that many US women don't have. Which does not mean that China is a free country, but just to gain some perspective. The notion of some place being a dictatorship was many times weaponized to launch invasions and economic sanctions that left that place broken and impoverished.
This is a false equivalence. Whatever you or I personally feel about abortion, its legality in the United States is set through approximately democratic processes. Not perfect by any means, but it very roughly reflects the will of the people - sharply divided, with many geographic concentrations.
The will of the people in China is unknown. There is only the will of the CCP, and increasingly, one person.
It seems like you could use aider in architecture mode. Basically, it will suggest the solution to your problem fist, and prompt you to start editing, you can say no to refine the solution and only start editing when you are satisfied with it.
Citation? I think this is not true. The EU law seems to just require explicit consent. So websites and apps can ask whether user wants to share data to keep using them for free or pay a subscription fee.
A "consent or pay" model is sadly widely used, but it's at least very controversial and probably illegal. No data protection agency has gone on record to say it's definitely illegal and no fines have been given out IIRC, but the EDPB had some tactfully negative things to say about it [0], and the Czech DPA has ordered at least one company to cease the practice in a preliminary ruling [1]. (Which the company seems to be completely ignoring, as is sadly common.)
