Noodle 0.7.6: okay, this is getting serious
TL;DR: Noodle has changed a lot since the last Reddit post at v0.5.7. v0.7.6 adds built-in agent skill installation/update support, and the roadmap to v1 is now focused on assertions, chaining, scripting, testing, runner/CI, and stabilizing the execution model. After v1: streaming, OpenAPI sync, Bruno import, advanced automation, GraphQL/WebSockets/gRPC, and more.
The last time I posted Noodle here it was on v0.5.7. I ended that post saying it was still a small project. It still is, but I don't think it feels like a toy anymore. I've been working on it pretty much nonstop since then.
For anyone who hasn't seen it before, Noodle is a keyboard-first REST client for the terminal. The main idea is still the same: requests are simple YAML files that live in your repo, so you can edit them with anything, commit them to Git, share them with the code they belong to, and use the same collection from the TUI, CLI, CI, or a coding agent.
Since 0.5.7, quite a lot has changed
- Import/export is now available directly from the TUI, with OpenAPI, Swagger, Postman and Insomnia support. There is a proper Settings workspace, collection configuration, proxies, TLS and mTLS, OS-backed secret storage, much stricter redirect/security handling, and a persistent cookie jar with its own TUI.
- Authentication has also grown a lot. Noodle now supports Basic, Bearer, API keys, NTLMv2, AWS SigV4, OAuth 1.0a and OAuth 2.0, including browser authorization, PKCE, refresh tokens and secure token storage.
- XML is now a first-class body type alongside JSON, multipart, urlencoded and binary. Invalid collection YAML can be repaired without leaving the TUI. External-editor workflows are better, updates can install automatically, and there have been a lot of smaller UI and keyboard improvements along the way.
0.7.6 adds something I'm particularly excited about: better support for coding agents.
Noodle already has a noodle-use skill that teaches coding agents how Noodle collections work: how to create requests, organize collections, work with environments, audit requests, import other formats, run requests, etc.
With 0.7.6 you'll be able to install it directly with:
noodle agent install
And if the skill is installed, updating Noodle will update the skill too.
I wanted this to be part of Noodle itself instead of asking people to know about another package manager command and manually keep a skill in sync.
The nice part about agent support in Noodle is that there isn't really a special "AI workspace". The agent works with the same YAML files you do. If it creates or changes a request, you can open the file, review the diff and commit it like anything else in the repo.
So what happens now?
Before v1, the focus is no longer adding random HTTP features. I want to finish the execution side of Noodle:
- declarative assertions
- response capture and request chaining
- run-scoped variables
- pre-request and post-response JavaScript
- advanced tests
- a sandboxed scripting runtime
- proper script editors in the TUI with syntax highlighting, diagnostics and autocomplete for the Noodle scripting API
- a real collection runner
- CI-friendly results, stable exit codes and reporters
The goal is that the same collection can go from:
explore → debug → chain → test → automate → CI
That is where I want to call it v1.0.
For me, 1.0 isn't "Noodle has every feature Postman/Bruno/Yaak has". It means the YAML format, execution lifecycle, scripting API and CLI contracts are stable enough that I can commit to keeping them compatible.
After v1 and on the way to v2, there is still plenty I want to do: SSE and streaming responses, OpenAPI 3.1 and OpenAPI sync, direct Bruno/OpenCollection migration, multiple cookie sessions, JWT auth, external secret providers, better network timing/debugging, more advanced automation, and eventually GraphQL, WebSockets and gRPC.
I'm trying pretty hard not to turn Noodle into a giant workspace that happens to run in a terminal. I still want the repository to be the workspace.
I wrote a more complete summary of everything that changed between 0.5.7 and 0.7.6. And I've published the roadmap, including the detailed scope I'm currently thinking about for every version.
GitHub: https://github.com/wilfredinni/noodle
Install:
curl -LsSf https://noodlerest.dev/install.sh | sh
As always, feedback is very welcome. A bunch of what has ended up in Noodle came from people pointing out things that annoyed them or were missing, so if you use Bruno, Yaak, Posting, Postman, Insomnia, curl, or anything else for API work, I'm especially interested in what would still stop you from using Noodle.
