Error exit status 128 when attempting to use cli

[TheMindExpansionNetwork]

Describe the bug
Hello I am trying to get setup for windows 10 CLI to be able to develop fast

I really enjoy the setup but I get this error

I am using a drive on my Z:

Z:\GIT\AG3NTZ>lk app create
Using url, api-key, api-secret from environment
Cloning template...
exit status 128

I am not sure what I am doing wrong I installed with winget

Just when I use this it does not save

[rektdeckard]

This is us swallowing the message git would have printed to stdout, which in this case is probably that the file already exists. This is fixed in #441 and will produce human-readable errors in the next release.

In the mean time, can you try providing an alternate name when you create a new app from template:

lk app create <my_app_name>

[TheMindExpansionNetwork]

Thank you very much that helped me out and solved the cli issue but I am getting this

2024-11-11 17:04:13,405 - DEBUG asyncio - Using proactor: IocpProactor
2024-11-11 17:04:13,409 - DEV livekit.agents - Watching Z:\GIT\DIGITAL-ENTITY\M1NDG3N-AGENTZ\M1NDG3N\DaemonCore-AI\3XP3R1M3NTZ\M1NDZB0T
2024-11-11 17:04:15,650 - DEBUG asyncio - Using proactor: IocpProactor
2024-11-11 17:04:15,656 - INFO livekit.agents - starting worker {"version": "0.11.1", "rtc-version": "0.18.0"}
2024-11-11 17:04:15,890 - WARNING livekit.agents - failed to connect to livekit, retrying in 0s: 401, message='Invalid response status', url='wss://m1ndb0t-2045-rdatpaav.livekit.cloud/agent'
2024-11-11 17:04:16,002 - WARNING livekit.agents - failed to connect to livekit, retrying in 2s: 401, message='Invalid response status', url='wss://m1ndb0t-2045-rdatpaav.livekit.cloud/agent

Not sure what the issue is I will change it after solved but yeah is it suppose to have the agent

or is this just saying the front end is not setup

[rektdeckard]

The agents framework won't warn if there is no frontend to connect to, it will simply wait for rooms to be created and attempt to join them. It could be that your project details are incorrect, but this appears to be an issue with your agent and not with the CLI. If you're continuing to have problems, try asking a question over on https://github.com/livekit/agents/ or on our community Slack channel!