I have a similar system. I keep my wip.md open in Neovim all the time and the difference is: everyday, I move the done items to a timestamped file. I have records going back to 2009.
It's my timelog and work journal as I expand on items and mark them off as I work on them.
Could you please share a little on why it's noticeably better than Claude Code on a sub (or 5? I mean, sometimes you can brute force a solution with agents)?
It's more akin to a compiled executable that optionally has state. The caller pays to make changes to the state. It's up to the programmer who wrote the smart contract to make it so that unwanted changes aren't performed (eg. simple if-elses to check that the caller is in a hardcoded list or ask another smart contract to validate).
Each external from outside the blockchain into the program's functions are atomic., so user wallet initials func1 which calls func2 which calls func3, no matter which smart contract func2 and func3 are in, the whole call stack is 1 atomic operation.
A token is basically a smart contract that has an associate array with the owners as the keys and the values as the balance: [alice: 1, bob: 20].
And then you can imagine how the rest like transfers, swaps etc works.
And then it's kind of a "contract" because of the atomic nature. Since X transfers $1 to Y and Y transfers 1 cat to X for it is 1 atomic transaction.
The plugin just opens a terminal whereas in Zed you get a more natively feeling experience. In JetBrains they do support it as one of their agents but now you have to buy into JetBrains AI credit system instead of just using your Claude subscription.
Theres two ways to use Claude Code in JetBrains and instead of helping them make their plugin better they opted to try and make money off of it. Which Zed could have done the same but instead lowered their monthly to let you use your own Claude Code subscription.
How does Claude Code use the browser in your script/tool? I've always wanted to control my existing Safari session windows rather than a Chrome or a separate/new Chrome instance.
Most browsers these days expose a control API (like ChromeDevtools Protocol MCP [1]) that open up a socket API and can take in json instructions for bidirectional communication. Chrome is the gold standard here but both Safari and Firefox have their own driver.
For you existing browser session you'd have to start it already with open socket connection as by default that's not enabled but once you do the server should able to find an open local socket and connect to it and execute controls.
worth nothing that this "control browser" hype is quite deceiving and it doesn't really work well imo because LLMs still suck at understanding the DOM so you need various tricks to optimize for that so I would take OP's claims with a giant bag of salt.
Also these automations are really easy to identify and block as they are not organic inputs so the actual use is very limited.
It's extremely handy too! If you try to use web automation tools like selenium or playwright on a website that blocks them, starting chrome browser with the debug port is a great way to get past Cloudflare's "human detector" before kicking off your automation. It's still a pain in the ass but at least it works and it's only once per session
Note that while --remote-debugging-port itself cannot be discovered by cloudflare once you attach a client to it that can be detected as Chrome itself changes it's runtime to accomodate the connection even if you don't issue any automation commands. You need to patch the entire browser to avoid these detection methods and that's why there are so many web scraping/automation SAAS out there with their own browser versions as that's the only way to automate the web these days. You can't just connect to a consumer browser and automate undetected.
True, it fails to get past the Cloudflare check if my playwright script is connected to the browser. But since these checks only happen on first visit to the site I'm ok with that.
It depends. If you allow running any of bash/ruby/python3/perl, etc. and also allow Claude to create and edit files without permission, then it won't protect against the pattern you describe.
I normally just use CLIs and a single Markdown file but I found Verdent useful as it helps to have a central place to refer back to the chats and coding tasks.
We strongly believe that the future will be orchestrated, and in that future harnessing the multi agent workflows will be crucial. But yes, sometimes simple solutions work.
reply