Show HN: Code Claude Code
17 comments
·May 10, 2025justanotheratom
Is "Code Claude Code" a play on "Bob Loblaw"?
fny
I’d guess Run Forest Run.
frank_nitti
Or for the younger generation Go Diego Go
mmoustafa
Ha! I prefer this one
conception
I was on Go Dogs Go!
sean_
I never heard of Bob Loblaw, so no.
It's more a play on the phrase 'Code the thing that Codes the thing'
edmundsauto
If anyone else was curious to see the source, it’s hard to find due to the name collision on Google.
Here it is - https://github.com/RVCA212/codesys
divan
Is it the same lines of RooCode task orchestrator [1] or claude-task-master[2] ?
[1] https://www.reddit.com/r/ChatGPTCoding/comments/1k8641f/roo_...
[2] https://github.com/eyaltoledano/claude-task-master
Seems like this task orchestration is the next must-have thing for every agentic AI solution and it makes perfect sense.
sean_
same idea, yes
this seems simpler and more straight forward though
tarboreus
I was thinking about doing something like this. I write a lot of boilerplate about "ok we need to discuss before you implement, ask clarifying questions" so it doesn't go rushing ahead.
sean_
yea this boilerplate is super simple and effective. It's essentially mimicing how I use claude code and cursor, but with low level control.
A very cool thing I'm working on in this space is having an llm code with the codesys sdk, then run the code.
So imagine cursor coding a codesys file instead of doing the task directly so that it instead scripts claude code to do a sequence of actions and allows cursor/the user to simply analyze the results.
this also enables parralel claude code sessions which is super cool!
null
rvz
Great project. But I won't be using it as there aren't any tests to determine if it even works or if the SDK would make unexpected actions if the LLM goes wrong.
Probably "vibe-coded" in an hour and would likely have hundreds of bugs to be untrusted to use on my machine and doesn't remotely comply with 'clean code' architecture and test-driven development.
In the age of AI, it is even more important to have these tests for software that interacts with something that claims to reason and just adds unnecessary additional risk.
sean_
But yes, the LLM could go wrong because it's simply a wrapper around scripting claude code in non-interactive mode.
the immediate use cases are more towards automatically creating tests and documentation, as well as other non-destructive actions
such as read-only mode: https://github.com/RVCA212/codesys/blob/main/examples/exampl...
sean_
The source code is 155 lines.
You can vibe through asking cursor if it has any bugs and let me know or create a PR!
But by having 155 lines of source code and through continuous use of the sdk, I haven't experienced any problems
Actually this comment just gave me the idea of creating a file of codesys doing just this in its own repo!
rvz
> But by having 155 lines of source code and through continuous use of the sdk, I haven't experienced any problems
The number of lines of code being 155 lines is not an excuse to have zero tests, especially in an SDK and it doesn't mean it works.
It only means you know it 'works' on your machine and it may not work on someone else's or in another scenario.
> Actually this comment just gave me the idea of creating a file of codesys doing just this in its own repo!
Well, you've just proven my point.
The tests should be written first before you write the actual code and to just write them after the fact defeats the entire purpose of knowing what to test for and then assuming that it 'works'.
null
In the nature of Open Source, I am releasing something I'm actively working on but is insanely simple and will likely be made anyways.
It is an SDK for scripting Claude Code.
It's a lightweight (155 lines) and free wrapper around claude code
This is a big deal because it seems that using claude code and cursor has become largly repitive. My workflow typically goes like this:
Plan out my task into a file, then have claude code implement the plan into my code.
I'm actively building a product with this, but still wanted to make it OSS!
Use it now with `pip install codesys`