Hey HN - over the past few months, we’ve been working on Hatchet, which lets you write and manage workflows as code (previous HN post [1]).
Today we’re launching Hatchet's prompt engineering features, which lets developers create internal playgrounds from existing code. Unlike other platforms, Hatchet is backed by our low-latency workflow engine which lets you run any function within your codebase, not just managed or third-party LLM templates. This is useful for a number of reasons:
- Your prompt engineering playground is directly in sync with your codebase. We also support creating pull requests to your codebase from our UI when you’ve made changes to prompt parameters.
- You can view how changes to an LLM call impact the rest of your function calls downstream
- When deployed in production, you get full observability into inputs/outputs to each of your function calls so you can trace and capture user-facing errors
We built this because we got tired of using prompt engineering tools that don’t integrate well with your existing codebase - and we felt our workflow engine was a good fit for solving this.
Looking forward to hearing your thoughts and feedback on our tool.
Today we’re launching Hatchet's prompt engineering features, which lets developers create internal playgrounds from existing code. Unlike other platforms, Hatchet is backed by our low-latency workflow engine which lets you run any function within your codebase, not just managed or third-party LLM templates. This is useful for a number of reasons:
- Your prompt engineering playground is directly in sync with your codebase. We also support creating pull requests to your codebase from our UI when you’ve made changes to prompt parameters.
- You can view how changes to an LLM call impact the rest of your function calls downstream
- When deployed in production, you get full observability into inputs/outputs to each of your function calls so you can trace and capture user-facing errors
We built this because we got tired of using prompt engineering tools that don’t integrate well with your existing codebase - and we felt our workflow engine was a good fit for solving this.
Looking forward to hearing your thoughts and feedback on our tool.
[1] https://news.ycombinator.com/item?id=38970038