Operating System
Remote Linux server (via SSH)
Kiro Version
0.1.6
Bug Description
I tried using grep, find, tail ssh commands.
I also tried lsof -iTCP -sTCP:LISTEN -nP to find node active process. And then using ssh -L to resend the port to my macOS. But none of the above was a success.
I think the problem is that the active session in the kiro dev in my macos is not traspassing the session to the remote SSH like Cursor, Windsurf or Vscode. So I think this has to be worked, because the workaround didn't work for me.
Sheers,
Steps to Reproduce
Just install Kiro Dev → install Open Remote - SSH (and have you ssh-config file ready) and connect to your ssh server.
Kiro Dev initiates the OAuth login and starts a local Node server (e.g. http://localhost:11106) on the remote host.
The browser on the local machine successfully authenticates via GitHub and is redirected to:
http://localhost:11106/oauth/callback?code=...&state=...
However, since this callback URL points to localhost on the local machine, it does not reach the remote .kiro-server instance.
Manual port forwarding (e.g. ssh -L 11106:localhost:11106 user@host) and then accessing the callback via browser or curl sometimes results
{
"data": null,
"error": {
"status": 404,
"name": "NotFoundError",
"message": "Not Found",
"details": {}
}
}This makes the GitHub login unusable unless a workaround (e.g. manual CLI gh auth login, or using VSCode) is applied.
Expected Behavior
Extend de active local session to the remote SSH like other Forks or Vscode are doing it.
Conversation ID
The login flow should either:
Use a device code flow (like GitHub CLI: https://github.com/login/device), or
Offer a way to authenticate externally and relay the result to the server, or expose the port forwarding hint to the user.
Additional Context
No response
Operating System
Remote Linux server (via SSH)
Kiro Version
0.1.6
Bug Description
I tried using grep, find, tail ssh commands.
I also tried lsof -iTCP -sTCP:LISTEN -nP to find node active process. And then using ssh -L to resend the port to my macOS. But none of the above was a success.
I think the problem is that the active session in the kiro dev in my macos is not traspassing the session to the remote SSH like Cursor, Windsurf or Vscode. So I think this has to be worked, because the workaround didn't work for me.
Sheers,
Steps to Reproduce
Just install Kiro Dev → install Open Remote - SSH (and have you ssh-config file ready) and connect to your ssh server.
Kiro Dev initiates the OAuth login and starts a local Node server (e.g. http://localhost:11106) on the remote host.
The browser on the local machine successfully authenticates via GitHub and is redirected to:
http://localhost:11106/oauth/callback?code=...&state=...
However, since this callback URL points to localhost on the local machine, it does not reach the remote .kiro-server instance.
Manual port forwarding (e.g. ssh -L 11106:localhost:11106 user@host) and then accessing the callback via browser or curl sometimes results
{ "data": null, "error": { "status": 404, "name": "NotFoundError", "message": "Not Found", "details": {} } }This makes the GitHub login unusable unless a workaround (e.g. manual CLI gh auth login, or using VSCode) is applied.
Expected Behavior
Extend de active local session to the remote SSH like other Forks or Vscode are doing it.
Conversation ID
The login flow should either:
Use a device code flow (like GitHub CLI: https://github.com/login/device), or
Offer a way to authenticate externally and relay the result to the server, or expose the port forwarding hint to the user.
Additional Context
No response