Skip to content

[FEATURE] reload config on SIGUSR1 #18813

Description

@Morriz

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

It is now impossible to reload settings of a running cloud code instance.

Proposed Solution

We have integrated CC in a framework with tmux and would like to reload with SIGUSR1 the theme configuration (and any other setting that is suitable) that we have changed with our tooling so that the running process picks up the new settings.json

Alternative Solutions

No response

Priority

Low - Nice to have

Feature Category

Interactive mode (TUI)

Use Case Example

When changing dark mode a script is run to send SIGUser1 to running cloud code instances, making them pick up settings that can be reloaded on the fly.

Additional Context

No response

Activity

  1. github-actions commented on Jan 17, 2026

    @github-actions

    Found 3 possible duplicate issues:

    1. Feature Request: Add /reloadSettings command to reload configuration without restart #5513
    2. Feature Request: Change theme on running instance from CLI #6236
    3. Feature Request: Hot reload configuration (/reload command) #17306

    This issue will be automatically closed as a duplicate in 3 days.

    • If your issue is a duplicate, please close it and 👍 the existing issue instead
    • To prevent auto-closure, add a comment or 👎 this comment

    🤖 Generated with Claude Code

  2. github-actions commented on Jan 21, 2026

    @github-actions

    This issue has been automatically closed as a duplicate of #5513.

    If this is incorrect, please re-open this issue or create a new one.

    🤖 Generated with Claude Code

  3. marcindulak commented on Jan 21, 2026

    @marcindulak

    Why was that marked as duplicate? The bot comment was downvoted in time.

  4. github-actions commented on Jan 28, 2026

    @github-actions

    This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

  5. locked as resolved and limited conversation to collaborators on Jan 28, 2026
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

    duplicateThis issue or pull request already exists

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions