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`
It's more a play on the phrase 'Code the thing that Codes the thing'
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.
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!
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'.
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...
Here it is - https://github.com/RVCA212/codesys
[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.
this seems simpler and more straight forward though
Aider has had support for scripting [0] in python or via the command line for a long time.
I made a screencast [1] recently that included ad-hoc bash scripting aider as part of the effort to add support for 130 new programming languages. It may give a flavor for how powerful this approach can be.
[0] https://aider.chat/docs/scripting.html
[1] https://aider.chat/docs/recordings/tree-sitter-language-pack...
I first made a scripting tool of aider that I didn't open source: (https://cloudcoding.ai)
Scripting with aider gives lower level control but this is also its shortcoming to why I prefer scripting Claude code.
Claude code is like a better architect mode and people want higher and higher levels of abstraction away from the coding and more towards the vibing.
tarboreus•4h ago
sean_•4h ago
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!