Skip to main content
Konduktor isn’t just a thing I threw together over a weekend to be yet another agent orchestrator just because everyone’s building them. Everyone’s building orchestrators because we’ve clearly not completely figured out how to build great products together with agents yet. Konduktor is my best attempt at understanding where we might be going, and building for the future that’s coming, while still being useful today. In today’s age, I might be called slow, but Konduktor is actually the product of a couple months of planning, thinking, and building (admittedly not full-time). Someone might say: “I can prompt this a weekend”, and while I don’t doubt someone could build out Konduktor’s core functionality really fast, I think there are two things that they would be missing:
  1. Konduktor’s polish: You’ll of course find bugs, but I’ve been using and testing Konduktor extensively and staying attentive to the minute details of the experience, like how buttons align with the nav, keyboard navigation, having fully hand-written docs, consistent styling, etc. AI let’s me build faster which gives me more time to spend on building a delightful experience.
  2. All the thinking behind it: You can take Konduktor’s ideas and build a replica very fast, but Konduktor is not finished software. And the level of thought that’s been involved in getting it to this point can’t be replicated and will continue to feed into where Konduktor goes from here.
As far as what Konduktor is today, it’s an attempt. It’s an attempt at understanding how products will be built going forward. Some things I’m more certain of, others I believe will soon change. If you have opinions, do share them. It’s inevitable that building the feature must be a collaborative effort.