Was able to login with one of the previous commits on this PR about an hour ago, will try to find to play with the latest later. Good stuff @Vuks69 🚀

I don't think this package can be merged into nixpkgs considering it seemingly abuses an oversight by the copyright holders and bypasses the waitlist. If this gets patched, then we have a source invalidation.

In my opinion, you're better off closing this PR and submitting this to somewhere like https://github.com/nix-community/NUR or asking the copyright holders to create a flake or equivalent for their users.

I don't think this package can be merged into nixpkgs considering it seemingly abuses an oversight by the copyright holders and bypasses the waitlist. If this gets patched, then we have a source invalidation.

Given the issue on their GitHub issues was triaged as a feature and there was no waitlist when this PR was opened yesterday, I'm inclined to believe the authors do want their software distributed.

Are we sure this bypasses the waitlist? Did you try it? I can't test it because I registered yesterday before there was a wait list, when opening the app it required me to complete an oauth registration prior to using it, that's actually where my PR broke (wouldn't call browser). If the authors aren't blocking new registrations at the OAuth registration step, the waitlist will be bypassed by anyone determined in very short order.

required me to complete an oauth registration prior to using it

Oh I understand this better now, I'm guessing the license agreement/copy protection mechanism happens on startup. I don't have any objections then on that front.

I still think this is better served by the Kiro upstream having their own flake (possibly here https://github.com/kirodotdev/Kiro)

better served by the Kiro upstream having their own flake (possibly here https://github.com/kirodotdev/Kiro)

NixOS maybe represents 0.1% of Linux's 4% of global installations, if the authors don't already use Nix/NixOS asking them to familiarize themselves with Nix to support it is going to fall below the bottom of everything else they're working on by priority...

One of the things that drew me to NixOS initially was its ability to magically package new stuff (BambuStudio in that case) seamlessly while my old distro (Ubuntu) was stuck waiting for backports, resolving dependency conflicts and using Docker images as a workaround. Having the bleeding edge available on day 1 (Nix being first to market because of dep isolation) is a huge strength that'll helps us grow to 0.2%+ and the eventual "Year of Nix"!❄️🤣

I added most of the changes suggested, but honestly this'll have to be put on the backburner until Kiro devs give us a simple/reasonable way to get the tarballs/dmg files with matching versions. Until then, right now I have a 0.1.0 version for x64 linux, and 0.1.9 for x64/arm darwin. I don't see a way to manually figure out the download links as they include the build timestamp, I'm not going to abuse the endpoint by bruteforcing that.

I whipped up a small script that utilizes dmg2img and apfs-fuse to read the .dmg's, resulting in this:

❯ /home/vuks/src/nixpkgs/pkgs/by-name/ki/kiro/update.sh

File: 202507140012-distro-linux-x64.tar.gz
Version: 0.1.0
Hash: sha256-6bbc/HndiN/HUoZyYo9r6Olih2n4/NMyRpxD59z9SH0=

File: 202507162010-Kiro-dmg-darwin-x64.dmg
Version: 0.1.9
Hash: sha256-qpLIZC93AeyBVnEZM8Jf4EOioS/deCJjPS2cCk2q5jo=

File: 202507161958-Kiro-dmg-darwin-arm64.dmg
Version: 0.1.9
Hash: sha256-+QfvhZ+VRnylR0Pj9Vjc43cqcR8lzh0oqAEW9FNTdCk=

Actually I think I managed to find the link they're using for their internal update process, in the package.json file. This might allow me to grab the latest artifacts, including the ARM one for linux. Stay tuned.

Edit: Works for linux, but not for darwin. The darwin artifact has a completely different filesystem tree and update system, it seems to involve some awfully weird .js/.mjs files, and I'm not finding anything useful with find/grep related to updating.

Unless I can find download links for anything else than x86_64-linux that are on version 0.1.0, I'm giving up on including anything other than that for now. (or just all 4 links that point to the same version)
While I can find the update links for linux, they seem to still be marked as 0.1.0 (despite latest as of now is 0.1.15), the links would point to a version that I'm unable to determine the version of, and whether they're the full tarball or some sort of diff/incremental tarball. pkgdiff is unhelpful because the structures of direct and update downloads are different.
I'm entirely unable to figure out the update links for darwin as mentioned earlier. At this point I'd rather just have a working MVP out there and wait until Kiro devs give packagers a way to properly determine the download sources.

There is a site that has a list of links to the releases...

https://kirohistory.dev/

It includes this which is supposed to be 0.1.15:
https://prod.download.desktop.kiro.dev/releases/202507180237--distro-linux-x64-tar-gz/202507180237-distro-linux-x64.tar.gz

(I'm on my phone so can't test it)

Confirmed it's the newer build:
Version: 0.1.15
VSCode Version: 1.94.0
Commit: 3bc33dd4c5eafbd5052855ecbf5c622c75d33ab8
Date: 2025-07-18T01:48:26.344Z
Electron: 30.5.1
ElectronBuildId: undefined
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Linux x64 6.12.35

Here's the patch to your branch @Vuks69

diff --git a/pkgs/by-name/ki/kiro/package.nix b/pkgs/by-name/ki/kiro/package.nix
index 50adaaa71..c9f20a6ce 100644
--- a/pkgs/by-name/ki/kiro/package.nix
+++ b/pkgs/by-name/ki/kiro/package.nix
@@ -10,11 +10,11 @@

 let
   inherit (stdenv) hostPlatform;
-  version = "0.1.0";
+  version = "0.1.15";
   sources = {
     x86_64-linux = fetchurl {
-      url = "https://prod.download.desktop.kiro.dev/releases/202507140012--distro-linux-x64-tar-gz/202507140012-distro-linux-x64.tar.gz";
-      hash = "sha256-6bbc/HndiN/HUoZyYo9r6Olih2n4/NMyRpxD59z9SH0=";
+      url = "https://prod.download.desktop.kiro.dev/releases/202507180237--distro-linux-x64-tar-gz/202507180237-distro-linux-x64.tar.gz";
+      hash = "sha256-cXDG0WBKEZR3e7hrTqVKRy3diTvwicy5RPi+qTkPbwc=";
     };
   };
   src = sources.${hostPlatform.system} or (throw "Unsupported platform for Kiro");

oh that is super useful and clean, in browser when hovering over the download buttons I can see they just link straight to the official download links. that lets me put the other archs and darwin in the package too <3

That's unfortunate - Kiro distributes the linux tarball as a "universal" package, which I assumed meant it's for all architectures. Turns out they most likely meant it's for all distributions (given the other linux package is a .deb file). The darwin packages should work correctly, as they're explicitly for x64 and Apple ARM.
I'll remove the linux arm package and ask on their discord about linux arm support.

An issue asking for linux ARM builds is on Kiro's repository: kirodotdev/Kiro#263

0.1.42 is out, I also had kiro make itself an updater script, not sure the best way to share though.

--- pkgs/by-name/ki/kiro/package.nix.backup     2025-08-05 12:23:59.475847100 -0400
+++ pkgs/by-name/ki/kiro/package.nix    2025-08-05 12:28:15.840931943 -0400
@@ -10,20 +10,20 @@
 
 let
   inherit (stdenv) hostPlatform;
-  version = "0.1.25";
+  version = "0.1.42";
   sources = {
     x86_64-linux = fetchurl {
-      url = "https://prod.download.desktop.kiro.dev/releases/202507232027--distro-linux-x64-tar-gz/202507232027-distro-linux-x64.tar.gz";
-      hash = "sha256-XxtJS7hLUKHJG0HhiA2Fyt7wNh5YebOOYadvNvXCKzc=";
+      url = "https://prod.download.desktop.kiro.dev/releases/202508020245--distro-linux-x64-tar-gz/202508020245-distro-linux-x64.tar.gz";
+      hash = "sha256-2kUx4PEqVcLF2/gk1+bxjeVrfX6wOxfRpLeMevNNsR8=";
     };
     aarch64-linux = sources.x86_64-linux; # "universal" package
     x86_64-darwin = fetchurl {
-      url = "https://prod.download.desktop.kiro.dev/releases/202507232041-Kiro-dmg-darwin-x64.dmg";
-      hash = "sha256-dH+aQ8IKqGC0TLMlOQFk7UYhL5/dWSOwLXD417bBpWk=";
+      url = "https://prod.download.desktop.kiro.dev/releases/202508020251-Kiro-dmg-darwin-x64.dmg";
+      hash = "sha256-8P562N6b4PyNYgNICyrlVxphkQjXdv80VEXtk71iabE=";
     };
     aarch64-darwin = fetchurl {
-      url = "https://prod.download.desktop.kiro.dev/releases/202507232015-Kiro-dmg-darwin-arm64.dmg";
-      hash = "sha256-GQ40ZirD+MEHcS6B7i7xl0wYCPspvokRrMuD3eqZQM4=";
+      url = "https://prod.download.desktop.kiro.dev/releases/202508020230-Kiro-dmg-darwin-arm64.dmg";
+      hash = "sha256-YBHnFmoVfrl4chEkj9YBP2aUZ4g9UY9AixgCFKV5FVU=";
     };
   };
   src = sources.${hostPlatform.system} or (throw "Unsupported platform for Kiro");

It works standalone, but I wasn't able to test it with nixpkgs-update (I think because kiro doesn't exist in master, but not certain).

update.sh.txt

--- a/pkgs/by-name/ki/kiro/package.nix
+++ b/pkgs/by-name/ki/kiro/package.nix
@@ -49,7 +49,7 @@ in
   patchVSCodePath = true;

   tests = { };
-  updateScript = null;
+  updateScript = ./update.sh;

   meta = {
     description = "IDE for Agentic AI workflows based on VS Code";

issue: trivial use of inherit (line 12)

Remove inherit usage here since we should avoid refactoring derivation code for consistency.

    inherit (stdenv) hostPlatform;

issue: Unneeded logic in sources attrset

  src = sources.${hostPlatform.system} or (throw "Unsupported platform for Kiro");

This throw is not needed as Nix will error out automatically and this is already guarded by meta.platforms I see this is used in pkgs/applications/editors/vscode/vscode.nix but I argue it's not really needed.

Reference error:

     error: attribute 'aarch64-linux' missing
       at /home/user/Projects/Forge/nixpkgs/pkgs/by-name/ki/kiro/package.nix:28:9:
           27|   };
           28|   src = sources.${hostPlatform.system};
             |         ^
           29| in

suggestion: updateScript and sources

One strategy I would suggest is to separate out the sources from the derivation package.nix and use a sources.json instead, and use the lib.importJSON to import it within the derivation.

@deftdawg - thanks for the heads up and the update script - I let myself beautify it a little.
@normalcea - I think I've addressed all of your concerns now, let me know if anything's still off.

Tested the update script and building/running Kiro on x64 linux.

aaand of course I forgor to format it.

Review 2

issue (blocking): updateScript fails due to non-portable shebang.

Using nix-shell maintainers/scripts/update.nix --argstr skip-prompt true --argstr package kiro throws an error as dependencies are not handled in a nix portable way. We need to use a nix-shell instead.

Note: The command above is how your update scripts should be tested as it's what is used for both maintainers and CI.

Diff for resolving (you can look at other update.sh scripts in-tree for more examples)

diff --git a/pkgs/by-name/ki/kiro/update.sh b/pkgs/by-name/ki/kiro/update.sh
index b99a0bb284ee..3d35aefdb071 100755
--- a/pkgs/by-name/ki/kiro/update.sh
+++ b/pkgs/by-name/ki/kiro/update.sh
@@ -1,4 +1,5 @@
-#!/usr/bin/env bash
+#!/usr/bin/env nix-shell
+#!nix-shell -i bash -p curl gnugrep gnused jq

 set -euo pipefail

@@ -25,16 +26,6 @@ error_exit() {
     exit 1
 }

-# Check dependencies
-check_dependencies() {
-    local deps=("curl" "jq" "nix")
-    for dep in "${deps[@]}"; do
-        if ! command -v "$dep" >/dev/null 2>&1; then
-            error_exit "Required dependency '$dep' not found"
-        fi
-    done
-}
-
 # Fetch metadata for a platform
 fetch_platform_info() {
     local url="$1"
@@ -121,9 +112,6 @@ generate_sources_json() {
 main() {
     echo "Starting Kiro update process..."

-    # Check dependencies
-    check_dependencies
-
     # Fetch metadata for all platforms
     echo "Fetching platform information..."
     for platform in "${!PLATFORM_URLS[@]}"; do

Damn, thanks for pointing that out. Cursor's update script does it the correct way but I didn't look there. My bad.

Let me know when this is ready, I'll take a final look and merge.

I updated the version using the update script, rebased on top of master and checked that kiro still builds and works on x64 linux.

Right now I'm fairly certain this is ready to go.