Integrated development environment

A coordinator that is always on, manages sub-agents, watches Slack for bug reports, follows your PRs to fix CI issues, runs scheduled tasks, and all agents inside a project share memory and generated artifacts that sync automatically across your device and the agent's computers.

The IDE just became an operating environment.

That's persistence.

Fundamentally different from what shipped last month.

The questions it asks users get written into a file called, and it expects users to go into that file to answer and record their responses.

But ever since I started using AI IDEs, I haven't touched traditional editors like VS Code in a long time.

I really don't want to open up a whole IDE just to answer a few questions.

That's way too much hassle.

But I thought the initial goal, I had kind of even forgotten about this.

Their goal was to basically build a web-based platform editor IDE, which like I'm like, I didn't really think of that as because I think that was back to like everyone was trying to do it.

And I never even think that was like that great a goal.

I don't know, Matt, like, do you even remember this coming up when it first got started? Because it was known as Morocco.

It was Monaco was the first thing that got created.

Yeah, not to be confused with the font.

Yeah, I mean, there was or maybe there still is that idea that you would have developer IDEs on the web and their sandboxes would be fully configured.

And, you know, just like Citrix has always been the dream for everyone.

And people were starting to use it and experiment.

And at that point, it was pretty tied to like the IDE.

You could kind of ask it questions or you get the kind of IntelliSense thing.

But people were pretty skeptical, mostly because they were being successful with the outcomes.

What you end up with.

Before you start, you need Kiro installed and signed in, and a project open, from the repo root, or open the folder in the IDE.

You need whatever test command your project already uses, because the rig wires it in without replacing it.

That is the whole prerequisite list.

Everything below lives in the repo and gets committed with it.

Kiro runs one agent across the IDE, the CLI, and the web, all reading the same config.

So the rig you set up here follows you to whichever surface you work in next.

1.

We did an interesting project for Meta, I want to say late last year and early this year when the Kotlin SDK came out for Horizon OS.

And I say, we really would love to have some people build some tutorials, help Kotlin developers develop for this platform and get familiar with the SDK and integrating the tools and the emulator in the IDE and everything.

So we did an interesting project for them, wrote a bunch of articles.

And I think that, to me, I would say was maybe a little of the wake-up moment to say, hey, this is really... becoming much more accessible for your, I'll say average run of the mill mobile developer.

Um, and I think, you know, eyeopening for a lot of people.

And I hope again, you know, one of our, one of the goals among other things is to, um, get the mobile developer community interested in this space and developing for this space.

Uh, and so those kinds of discussions I think are going to be important to have, not just like, okay, well here's how this looks, you know, on, on screening the code and here's, you know, at this SDK and here's what's going on in the emulator and the IDE.

I think it's a lot more, uh, these discussions I think that Thomas is going to have in his panel are going to be really, cool and relevant for the developer community to understand the background of where we've been and where we're headed

This one of those things though, if they refuse to use that tooling, the API, the XMLA endpoint, and they're only going to use the user interface and Power BI Desktop for what it is, Like I can only help so much.

I can explain to them that we're using the IDE.

We're using source control and Tyndall to edit a lot of those elements because the best practices, you know, and that's that developer role.

But again, there's a concern that they do not use