Failed to create workspace: Command execution failed with exit code 1

[lcarva]

Bug description

Installed via Flatpak

Operating system

Linux fedora 6.19.14-108.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 21 18:06:59 UTC 2026 x86_64 GNU/Linux

Installation Method

Installer from website/GitHub releases

Version

0.2.x

Steps to reproduce

Create a workspace.

Relevant log output

C3: -> org.freedesktop.DBus call org.freedesktop.DBus.AddMatch at /org/freedesktop/DBus
C4: -> org.freedesktop.Flatpak call org.freedesktop.Flatpak.Development.HostCommand at /org/freedesktop/Flatpak/Development
B-1: <- org.freedesktop.DBus return from C2
B-1: <- org.freedesktop.DBus return from C3
B66: <- :1.159 return error org.freedesktop.DBus.Error.FileNotFound from C4
kdn failed: kdn init /home/lucarval/workspaces/kaiden/check-source-origin --runtime podman --agent claude --start --output json --name check-source-origin — Command execution failed with exit code 1
C43: -> :1.58 call org.freedesktop.IBus.InputContext.Reset at /org/freedesktop/IBus/InputContext_5

Additional context

No response

[lcarva]

The directory /home/lucarval/workspaces/kaiden/check-source-origin exists.

[jeffmaury]

can you run:

kdn init /home/lucarval/workspaces/kaiden/check-source-origin --runtime podman --agent claude --start --output json --name check-source-origin --show-logs ?

[lcarva]

@jeffmaury, where's the kdn binary? I installed via flatpak.

[jeffmaury]

@jeffmaury, where's the kdn binary? I installed via flatpak.

Should be in the kaiden.app resources folder

[lcarva]

Hmm with a Flatpak installation, the kdn binary will not be available on my system. Instead, it is likely included in the Flatpak image. I don't know what "kaiden.app resources folder" is for Flatpaks but it sounds specific to macOS applications.

[jeffmaury]

Hmm with a Flatpak installation, the kdn binary will not be available on my system. Instead, it is likely included in the Flatpak image. I don't know what "kaiden.app resources folder" is for Flatpaks but it sounds specific to macOS applications.

So you could get the path if you got to Resources -> CLI Tools and if you hover on the version it should give you the path. Not sure you'll be able to access it

[lcarva]