Skip to content

Empty window when starting ECA from a non-project directory #115

Open

Description

@zikajk

Problem:
When I start ECA from some folder via C-u eca and selecting a different folder as a workspace then I end up with an empty ECA window:

  • I see only blank header on top.

Solution:`

  • Calling eca-chat-new from a workspace file.
  • Now i see it filled in, only model and behavior are empty, but they can be set and it works ok.

Activity

  1. added theissue type on Dec 15, 2025
  2. zikajk commented on Dec 16, 2025

    @zikajk
    MemberAuthor

    Now i see it filled in, only model and behavior are empty, but they can be set and it works ok.

    This is kind of random, yesterday it happened all the time, today behavior and model were set up.

  3. ericdallo commented on Dec 17, 2025

    @ericdallo
    Member

    Yeah I can't repro that, not sure I'm doing something wrong

  4. zikajk commented on Jan 2, 2026

    @zikajk
    MemberAuthor

    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

  5. zikajk commented on Jan 8, 2026

    @zikajk
    MemberAuthor

    Hm, i think it is more complicated.
    What happened to me just now:

    1. I had ECA session in PROJECT A
    2. Then i started another chat in a different project and when i tried to switch model there nothing happened
    3. 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.

  6. zikajk commented on Jan 8, 2026

    @zikajk
    MemberAuthor

    @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.

  7. ericdallo commented on Jan 16, 2026

    @ericdallo
    Member

    @zikajk ECA native binary is really fast to startup, I wonder if this problem would happen for real users 🤔

  8. zikajk commented on Jan 17, 2026

    @zikajk
    MemberAuthor

    I don't think it has anything to do with the speed of startup. Do you?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions