Currently, when Claude Code disconnects from a monet session (e.g., when exiting the CLI), the session is automatically cleaned up. This removes the session and deletes the lockfile.
Use case
When working on a project within Emacs and a (separate) terminal, I often restart Claude Code sessions while keeping Emacs running. Having to manually restart the monet server each time before reconnecting adds friction to the workflow.
It would be useful to have an option to keep the monet server running after Claude disconnects, allowing a new Claude session to reconnect to the existing server.
Proposed solution
Add a customizable variable (e.g., monet-persist-sessions, default nil for backward compatibility) that, when enabled, keeps sessions alive after Claude Code disconnects.
Sessions would persist until manually stopped or Emacs exits.
Currently, when Claude Code disconnects from a
monetsession (e.g., when exiting the CLI), the session is automatically cleaned up. This removes the session and deletes the lockfile.Use case
When working on a project within Emacs and a (separate) terminal, I often restart Claude Code sessions while keeping Emacs running. Having to manually restart the
monetserver each time before reconnecting adds friction to the workflow.It would be useful to have an option to keep the
monetserver running after Claude disconnects, allowing a new Claude session to reconnect to the existing server.Proposed solution
Add a customizable variable (e.g.,
monet-persist-sessions, defaultnilfor backward compatibility) that, when enabled, keeps sessions alive after Claude Code disconnects.Sessions would persist until manually stopped or Emacs exits.