You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Empty window when starting ECA from a non-project directory #115
I was also able to reproduce it like this:
A) Start ECA in project A
B) Visit any folder (non-versioned in my case) and call eca-restart
C) The new buffer is broken
Hm, i think it is more complicated.
What happened to me just now:
I had ECA session in PROJECT A
Then i started another chat in a different project and when i tried to switch model there nothing happened
So I did eca-stop and it killed both chats (PANIC!)
I have a feeling that something bad happens if ECA is starting and i jump between buffers / projects.
I guess that eca-stop should close only the process for one project.
@ericdallo Maybe the second point can help to find the problem?
EDIT: I noticed this! The ECA started in PROJECT B is associated to project A (based on the default chat name in modeline). And when I try to call ECA in the project B again it just jump to that wrongly associated chat.
I can't do eca-stop because it would kill other chats for PROJECT A (it would explain the third point).
So there must be some problem with ECA startup and a workspace association. And I have a feeling that this is related to the first reported issue.
EDIT2: And after I did eca-stop on the original chat of PROJECT A. Then I can't do the same for the wrongly assigned chat started in PROJECT B and when i try to kill the buffer then i get Wrong type argument: eca--session, nil when I agree with deleting chat from server.
Activity
zikajk commentedon Dec 16, 2025
This is kind of random, yesterday it happened all the time, today behavior and model were set up.
ericdallo commentedon Dec 17, 2025
Yeah I can't repro that, not sure I'm doing something wrong
zikajk commentedon Jan 2, 2026
I was also able to reproduce it like this:
A) Start ECA in project A
B) Visit any folder (non-versioned in my case) and call
eca-restartC) The new buffer is broken
zikajk commentedon Jan 8, 2026
Hm, i think it is more complicated.
What happened to me just now:
eca-stopand it killed both chats (PANIC!)I have a feeling that something bad happens if ECA is starting and i jump between buffers / projects.
I guess that eca-stop should close only the process for one project.
zikajk commentedon Jan 8, 2026
@ericdallo Maybe the second point can help to find the problem?
EDIT: I noticed this! The ECA started in PROJECT B is associated to project A (based on the default chat name in modeline). And when I try to call ECA in the project B again it just jump to that wrongly associated chat.
I can't do
eca-stopbecause it would kill other chats for PROJECT A (it would explain the third point).So there must be some problem with ECA startup and a workspace association. And I have a feeling that this is related to the first reported issue.
EDIT2: And after I did
eca-stopon the original chat of PROJECT A. Then I can't do the same for the wrongly assigned chat started in PROJECT B and when i try to kill the buffer then i getWrong type argument: eca--session, nilwhen I agree with deleting chat from server.ericdallo commentedon Jan 16, 2026
@zikajk ECA native binary is really fast to startup, I wonder if this problem would happen for real users 🤔
zikajk commentedon Jan 17, 2026
I don't think it has anything to do with the speed of startup. Do you?