I've been experimenting with local models via Ollama for a long time now, but one thing kept frustrating me:

Smaller local models are actually a LOT more capable than people think, but they struggle with reliability.

They lose focus, drift over long sessions, stop halfway through problems, and aren't great at breaking apart larger tasks.

So, to try and fix that, I built Coyote.

Loki is a local-first command line tool and runtime for building and running LLM workflows locally. It's model agnostic, works well with Ollama, and includes things like:

• Agents and delegation
• Workflow scripting
• MCP servers
• RAG
• Roles/personas
• Custom tools
• Macros

A lot of the architecture is specifically designed around improving the reliability of smaller models. So for example:

• Auto-continuation to push models towards completion and prevent them from stopping halfway through a problem
• Parallel agent delegation to reduce context overload and keep scope small
• Workflow-based execution for more deterministic automations
• Scoped agents to reduce context drift

My long term goal with this project is basically:

Get as close as possible to Claude Code-style reliability using fully local models.

I'd love feedback from other Ollama users experimenting in this space and any tips/pointers/ideas of other things to add to make it function even better!

Repo: https://github.com/Dark-Alex-17/coyote

Managarr - A TUI and CLI to help you manage your Servarrs.

Thanks to everyone who contributed to this release, be that in code, issues, or enhancement suggestions! You all help fuel my passion for working on this and it doesn't go unappreciated! 😄

As always, you can try out the changes yourself via the Managarr Demo Site

Breaking Changes

• Managarr now supports multiple instances of the same Servarr with custom names and ordering. (See Features below) To accommodate this, configuration files must be updated so that all Servarrs listed beneath radarr, sonarr, etc., be updated to be lists, not individual Servarrs. For example: to migrate from the following config:

  radarr:
    host: 192.168.0.78
    port: 7878
    api_token: someApiToken1234
  sonarr:
    host: 192.168.0.89
    port: 8989
    api_token: someApiToken1234
  

  You would change the above configuration to the following:

  radarr:
    - host: 192.168.0.78
      port: 7878
      api_token: someApiToken1234
  sonarr:
    - host: 192.168.0.89
      port: 8989
      api_token: someApiToken1234
  

• The --config flag has been renamed to --config-fileto make it more clear what it does.

Features

• Users can now specify multiple instances of the same type of Servarr and give them custom names and ordering. This allows users to manage multiple instances of the same Servarr, such as an Anime and TV Show instance of Sonarr. To configure, add a list of Servarrs under the respective type (e.g. radarr, sonarr, etc.). (#17)

  • You can specify ordering of your Servarrs and how they will appear in the UI via the weight field. The lower the weight, the further to the left the Servarr will appear in the UI.
  • You can also name your Servarrs whatever you wish. This name will be displayed in the UI. For example, to name your Sonarr instances:

    sonarr:
      - name: Anime
        host: 192.168.0.89
        api_token: someApiToken
    
      - name: TV Shows
        host: 192.168.0.88
        api_token: someOtherApiToken
    

  • This change also required the introduction of a new CLI flag to specify which Servarr you wish to interact with: --servarr-name. This corresponds directly to the value of the name field in your configuration. If you did not specify a name in the configuration, then default names are provided for you corresponding to the Servarr; For example, if you defined two Radarr instances with no names, they will be named Radarr 1 and Radarr 2, respectively.
  • Omitting the --servarr-name flag with multi-instance configurations will default to using the first instance that appears in your config. For example, for the following configuration:

    sonarr:
      - host: 192.168.0.89
        api_token: someApiToken
    
      - host: 192.168.0.88
        api_token: someOtherApiToken
    

    Running managarr sonarr list series will default to interacting with the Sonarr instance at 192.168.0.89. This is the same as running managarr sonarr list series --servarr-name 'Sonarr 1'.

• API tokens can now be fetched from files instead of needing to be hardcoded (#31). The following is an example config that loads the API token from a file:

  radarr:
    - host: 192.168.0.78
      api_token_file: /home/root/.config/radarr_token
  

• Configurations now interpolate environment variables (#23). This allows you to load sensitive information from environment variables. For example, to load the API token from an environment variable, you can do the following:

  radarr:
    - host: 192.168.0.78
      api_token: ${MY_RADARR_API_TOKEN_ENV_VAR}
  

  This is available for all fields in the configuration file.

Security Updates

• Updated OpenSSL to v0.10.70 to mitigate CVE-2025-24898

Miscellaneous

• Managarr now has a Matrix space! Feel free to drop in and message me directly if you're looking to discuss features, ideas, or just want to say, "Hi!".

Managarr - A TUI and CLI to help you manage your Servarrs.

Thanks to everyone who contributed to this release, be that in code, issues, or enhancement suggestions! You all help fuel my passion for working on this and it doesn't go unappreciated! 😄

As always, you can try out the changes yourself via the Managarr Demo Site

Breaking Changes

• Managarr now supports multiple instances of the same Servarr with custom names and ordering. (See Features below) To accommodate this, configuration files must be updated so that all Servarrs listed beneath radarr, sonarr, etc., be updated to be lists, not individual Servarrs. For example: to migrate from the following config:

  radarr:
    host: 192.168.0.78
    port: 7878
    api_token: someApiToken1234
  sonarr:
    host: 192.168.0.89
    port: 8989
    api_token: someApiToken1234
  

  You would change the above configuration to the following:

  radarr:
    - host: 192.168.0.78
      port: 7878
      api_token: someApiToken1234
  sonarr:
    - host: 192.168.0.89
      port: 8989
      api_token: someApiToken1234
  

• The --config flag has been renamed to --config-fileto make it more clear what it does.

Features

• Users can now specify multiple instances of the same type of Servarr and give them custom names and ordering. This allows users to manage multiple instances of the same Servarr, such as an Anime and TV Show instance of Sonarr. To configure, add a list of Servarrs under the respective type (e.g. radarr, sonarr, etc.). (#17)

  • You can specify ordering of your Servarrs and how they will appear in the UI via the weight field. The lower the weight, the further to the left the Servarr will appear in the UI.
  • You can also name your Servarrs whatever you wish. This name will be displayed in the UI. For example, to name your Sonarr instances:

    sonarr:
      - name: Anime
        host: 192.168.0.89
        api_token: someApiToken
    
      - name: TV Shows
        host: 192.168.0.88
        api_token: someOtherApiToken
    

  • This change also required the introduction of a new CLI flag to specify which Servarr you wish to interact with: --servarr-name. This corresponds directly to the value of the name field in your configuration. If you did not specify a name in the configuration, then default names are provided for you corresponding to the Servarr; For example, if you defined two Radarr instances with no names, they will be named Radarr 1 and Radarr 2, respectively.
  • Omitting the --servarr-name flag with multi-instance configurations will default to using the first instance that appears in your config. For example, for the following configuration:

    sonarr:
      - host: 192.168.0.89
        api_token: someApiToken
    
      - host: 192.168.0.88
        api_token: someOtherApiToken
    

    Running managarr sonarr list series will default to interacting with the Sonarr instance at 192.168.0.89. This is the same as running managarr sonarr list series --servarr-name 'Sonarr 1'.

• API tokens can now be fetched from files instead of needing to be hardcoded (#31). The following is an example config that loads the API token from a file:

  radarr:
    - host: 192.168.0.78
      api_token_file: /home/root/.config/radarr_token
  

• Configurations now interpolate environment variables (#23). This allows you to load sensitive information from environment variables. For example, to load the API token from an environment variable, you can do the following:

  radarr:
    - host: 192.168.0.78
      api_token: ${MY_RADARR_API_TOKEN_ENV_VAR}
  

  This is available for all fields in the configuration file.

Security Updates

• Updated OpenSSL to v0.10.70 to mitigate CVE-2025-24898

Miscellaneous

• Managarr now has a Matrix space! Feel free to drop in and message me directly if you're looking to discuss features, ideas, or just want to say, "Hi!".

Managarr - A TUI and CLI to help you manage your Servarrs.

Thanks to everyone who contributed to this release, be that in code, issues, or enhancement suggestions! You all help fuel my passion for working on this and it doesn't go unappreciated! 😄

As always, you can try out the changes yourself via the Managarr Demo Site

Breaking Changes

• Managarr now supports multiple instances of the same Servarr with custom names and ordering. (See Features below) To accommodate this, configuration files must be updated so that all Servarrs listed beneath radarr, sonarr, etc., be updated to be lists, not individual Servarrs. For example: to migrate from the following config:

  radarr:
    host: 192.168.0.78
    port: 7878
    api_token: someApiToken1234
  sonarr:
    host: 192.168.0.89
    port: 8989
    api_token: someApiToken1234
  

  You would change the above configuration to the following:

  radarr:
    - host: 192.168.0.78
      port: 7878
      api_token: someApiToken1234
  sonarr:
    - host: 192.168.0.89
      port: 8989
      api_token: someApiToken1234
  

• The --config flag has been renamed to --config-fileto make it more clear what it does.

Features

• Users can now specify multiple instances of the same type of Servarr and give them custom names and ordering. This allows users to manage multiple instances of the same Servarr, such as an Anime and TV Show instance of Sonarr. To configure, add a list of Servarrs under the respective type (e.g. radarr, sonarr, etc.). (#17)

  • You can specify ordering of your Servarrs and how they will appear in the UI via the weight field. The lower the weight, the further to the left the Servarr will appear in the UI.
  • You can also name your Servarrs whatever you wish. This name will be displayed in the UI. For example, to name your Sonarr instances:

    sonarr:
      - name: Anime
        host: 192.168.0.89
        api_token: someApiToken
    
      - name: TV Shows
        host: 192.168.0.88
        api_token: someOtherApiToken
    

  • This change also required the introduction of a new CLI flag to specify which Servarr you wish to interact with: --servarr-name. This corresponds directly to the value of the name field in your configuration. If you did not specify a name in the configuration, then default names are provided for you corresponding to the Servarr; For example, if you defined two Radarr instances with no names, they will be named Radarr 1 and Radarr 2, respectively.
  • Omitting the --servarr-name flag with multi-instance configurations will default to using the first instance that appears in your config. For example, for the following configuration:

    sonarr:
      - host: 192.168.0.89
        api_token: someApiToken
    
      - host: 192.168.0.88
        api_token: someOtherApiToken
    

    Running managarr sonarr list series will default to interacting with the Sonarr instance at 192.168.0.89. This is the same as running managarr sonarr list series --servarr-name 'Sonarr 1'.

• API tokens can now be fetched from files instead of needing to be hardcoded (#31). The following is an example config that loads the API token from a file:

  radarr:
    - host: 192.168.0.78
      api_token_file: /home/root/.config/radarr_token
  

• Configurations now interpolate environment variables (#23). This allows you to load sensitive information from environment variables. For example, to load the API token from an environment variable, you can do the following:

  radarr:
    - host: 192.168.0.78
      api_token: ${MY_RADARR_API_TOKEN_ENV_VAR}
  

  This is available for all fields in the configuration file.

Security Updates

• Updated OpenSSL to v0.10.70 to mitigate CVE-2025-24898

Miscellaneous

• Managarr now has a Matrix space! Feel free to drop in and message me directly if you're looking to discuss features, ideas, or just want to say, "Hi!".

Managarr - A TUI and CLI to help you manage your Servarrs.

Thanks to everyone who contributed to this release, be that in code, issues, or enhancement suggestions! You all help fuel my passion for working on this and it doesn't go unappreciated! 😄

As always, you can try out the changes yourself via the Managarr Demo Site

Breaking Changes

• Managarr now supports multiple instances of the same Servarr with custom names and ordering. (See Features below) To accommodate this, configuration files must be updated so that all Servarrs listed beneath radarr, sonarr, etc., be updated to be lists, not individual Servarrs. For example: to migrate from the following config:

  radarr:
    host: 192.168.0.78
    port: 7878
    api_token: someApiToken1234
  sonarr:
    host: 192.168.0.89
    port: 8989
    api_token: someApiToken1234
  

  You would change the above configuration to the following:

  radarr:
    - host: 192.168.0.78
      port: 7878
      api_token: someApiToken1234
  sonarr:
    - host: 192.168.0.89
      port: 8989
      api_token: someApiToken1234
  

• The --config flag has been renamed to --config-fileto make it more clear what it does.

Features

• Users can now specify multiple instances of the same type of Servarr and give them custom names and ordering. This allows users to manage multiple instances of the same Servarr, such as an Anime and TV Show instance of Sonarr. To configure, add a list of Servarrs under the respective type (e.g. radarr, sonarr, etc.). (#17)

  • You can specify ordering of your Servarrs and how they will appear in the UI via the weight field. The lower the weight, the further to the left the Servarr will appear in the UI.
  • You can also name your Servarrs whatever you wish. This name will be displayed in the UI. For example, to name your Sonarr instances:

    sonarr:
      - name: Anime
        host: 192.168.0.89
        api_token: someApiToken
    
      - name: TV Shows
        host: 192.168.0.88
        api_token: someOtherApiToken
    

  • This change also required the introduction of a new CLI flag to specify which Servarr you wish to interact with: --servarr-name. This corresponds directly to the value of the name field in your configuration. If you did not specify a name in the configuration, then default names are provided for you corresponding to the Servarr; For example, if you defined two Radarr instances with no names, they will be named Radarr 1 and Radarr 2, respectively.
  • Omitting the --servarr-name flag with multi-instance configurations will default to using the first instance that appears in your config. For example, for the following configuration:

    sonarr:
      - host: 192.168.0.89
        api_token: someApiToken
    
      - host: 192.168.0.88
        api_token: someOtherApiToken
    

    Running managarr sonarr list series will default to interacting with the Sonarr instance at 192.168.0.89. This is the same as running managarr sonarr list series --servarr-name 'Sonarr 1'.

• API tokens can now be fetched from files instead of needing to be hardcoded (#31). The following is an example config that loads the API token from a file:

  radarr:
    - host: 192.168.0.78
      api_token_file: /home/root/.config/radarr_token
  

• Configurations now interpolate environment variables (#23). This allows you to load sensitive information from environment variables. For example, to load the API token from an environment variable, you can do the following:

  radarr:
    - host: 192.168.0.78
      api_token: ${MY_RADARR_API_TOKEN_ENV_VAR}
  

  This is available for all fields in the configuration file.

Security Updates

• Updated OpenSSL to v0.10.70 to mitigate CVE-2025-24898

Miscellaneous

• Managarr now has a Matrix space! Feel free to drop in and message me directly if you're looking to discuss features, ideas, or just want to say, "Hi!".

Managarr - A TUI and CLI to help you manage your Servarrs.

Thanks to everyone who contributed to this release, be that in code, issues, or enhancement suggestions! You all help fuel my passion for working on this and it doesn't go unappreciated! 😄

As always, you can try out the changes yourself via the Managarr Demo Site

Breaking Changes

• Managarr now supports multiple instances of the same Servarr with custom names and ordering. (See Features below) To accommodate this, configuration files must be updated so that all Servarrs listed beneath radarr, sonarr, etc., be updated to be lists, not individual Servarrs. For example: to migrate from the following config:

  radarr:
    host: 192.168.0.78
    port: 7878
    api_token: someApiToken1234
  sonarr:
    host: 192.168.0.89
    port: 8989
    api_token: someApiToken1234
  

  You would change the above configuration to the following:

  radarr:
    - host: 192.168.0.78
      port: 7878
      api_token: someApiToken1234
  sonarr:
    - host: 192.168.0.89
      port: 8989
      api_token: someApiToken1234
  

• The --config flag has been renamed to --config-fileto make it more clear what it does.

Features

• Users can now specify multiple instances of the same type of Servarr and give them custom names and ordering. This allows users to manage multiple instances of the same Servarr, such as an Anime and TV Show instance of Sonarr. To configure, add a list of Servarrs under the respective type (e.g. radarr, sonarr, etc.). (#17)

  • You can specify ordering of your Servarrs and how they will appear in the UI via the weight field. The lower the weight, the further to the left the Servarr will appear in the UI.
  • You can also name your Servarrs whatever you wish. This name will be displayed in the UI. For example, to name your Sonarr instances:

    sonarr:
      - name: Anime
        host: 192.168.0.89
        api_token: someApiToken
    
      - name: TV Shows
        host: 192.168.0.88
        api_token: someOtherApiToken
    

  • This change also required the introduction of a new CLI flag to specify which Servarr you wish to interact with: --servarr-name. This corresponds directly to the value of the name field in your configuration. If you did not specify a name in the configuration, then default names are provided for you corresponding to the Servarr; For example, if you defined two Radarr instances with no names, they will be named Radarr 1 and Radarr 2, respectively.
  • Omitting the --servarr-name flag with multi-instance configurations will default to using the first instance that appears in your config. For example, for the following configuration:

    sonarr:
      - host: 192.168.0.89
        api_token: someApiToken
    
      - host: 192.168.0.88
        api_token: someOtherApiToken
    

    Running managarr sonarr list series will default to interacting with the Sonarr instance at 192.168.0.89. This is the same as running managarr sonarr list series --servarr-name 'Sonarr 1'.

• API tokens can now be fetched from files instead of needing to be hardcoded (#31). The following is an example config that loads the API token from a file:

  radarr:
    - host: 192.168.0.78
      api_token_file: /home/root/.config/radarr_token
  

• Configurations now interpolate environment variables (#23). This allows you to load sensitive information from environment variables. For example, to load the API token from an environment variable, you can do the following:

  radarr:
    - host: 192.168.0.78
      api_token: ${MY_RADARR_API_TOKEN_ENV_VAR}
  

  This is available for all fields in the configuration file.

Security Updates

• Updated OpenSSL to v0.10.70 to mitigate CVE-2025-24898

Miscellaneous

• Managarr now has a Matrix space! Feel free to drop in and message me directly if you're looking to discuss features, ideas, or just want to say, "Hi!".

Managarr - A TUI and CLI to help you manage your Servarrs.

Thanks to everyone who contributed to this release, be that in code, issues, or enhancement suggestions! You all help fuel my passion for working on this and it doesn't go unappreciated! 😄

As always, you can try out the changes yourself via the Managarr Demo Site

Breaking Changes

• Managarr now supports multiple instances of the same Servarr with custom names and ordering. (See Features below) To accommodate this, configuration files must be updated so that all Servarrs listed beneath radarr, sonarr, etc., be updated to be lists, not individual Servarrs. For example: to migrate from the following config:

  radarr:
    host: 192.168.0.78
    port: 7878
    api_token: someApiToken1234
  sonarr:
    host: 192.168.0.89
    port: 8989
    api_token: someApiToken1234
  

  You would change the above configuration to the following:

  radarr:
    - host: 192.168.0.78
      port: 7878
      api_token: someApiToken1234
  sonarr:
    - host: 192.168.0.89
      port: 8989
      api_token: someApiToken1234
  

• The --config flag has been renamed to --config-fileto make it more clear what it does.

Features

• Users can now specify multiple instances of the same type of Servarr and give them custom names and ordering. This allows users to manage multiple instances of the same Servarr, such as an Anime and TV Show instance of Sonarr. To configure, add a list of Servarrs under the respective type (e.g. radarr, sonarr, etc.). (#17)

  • You can specify ordering of your Servarrs and how they will appear in the UI via the weight field. The lower the weight, the further to the left the Servarr will appear in the UI.
  • You can also name your Servarrs whatever you wish. This name will be displayed in the UI. For example, to name your Sonarr instances:

    sonarr:
      - name: Anime
        host: 192.168.0.89
        api_token: someApiToken
    
      - name: TV Shows
        host: 192.168.0.88
        api_token: someOtherApiToken
    

  • This change also required the introduction of a new CLI flag to specify which Servarr you wish to interact with: --servarr-name. This corresponds directly to the value of the name field in your configuration. If you did not specify a name in the configuration, then default names are provided for you corresponding to the Servarr; For example, if you defined two Radarr instances with no names, they will be named Radarr 1 and Radarr 2, respectively.
  • Omitting the --servarr-name flag with multi-instance configurations will default to using the first instance that appears in your config. For example, for the following configuration:

    sonarr:
      - host: 192.168.0.89
        api_token: someApiToken
    
      - host: 192.168.0.88
        api_token: someOtherApiToken
    

    Running managarr sonarr list series will default to interacting with the Sonarr instance at 192.168.0.89. This is the same as running managarr sonarr list series --servarr-name 'Sonarr 1'.

• API tokens can now be fetched from files instead of needing to be hardcoded (#31). The following is an example config that loads the API token from a file:

  radarr:
    - host: 192.168.0.78
      api_token_file: /home/root/.config/radarr_token
  

• Configurations now interpolate environment variables (#23). This allows you to load sensitive information from environment variables. For example, to load the API token from an environment variable, you can do the following:

  radarr:
    - host: 192.168.0.78
      api_token: ${MY_RADARR_API_TOKEN_ENV_VAR}
  

  This is available for all fields in the configuration file.

Security Updates

• Updated OpenSSL to v0.10.70 to mitigate CVE-2025-24898

Miscellaneous

• Managarr now has a Matrix space! Feel free to drop in and message me directly if you're looking to discuss features, ideas, or just want to say, "Hi!".

Managarr - A TUI and CLI to help you manage your Servarrs.

Thanks to everyone who contributed to this release, be that in code, issues, or enhancement suggestions! You all help fuel my passion for working on this and it doesn't go unappreciated! 😄

As always, you can try out the changes yourself via the Managarr Demo Site

Breaking Changes

• Managarr now supports multiple instances of the same Servarr with custom names and ordering. (See Features below) To accommodate this, configuration files must be updated so that all Servarrs listed beneath radarr, sonarr, etc., be updated to be lists, not individual Servarrs. For example: to migrate from the following config:

  radarr:
    host: 192.168.0.78
    port: 7878
    api_token: someApiToken1234
  sonarr:
    host: 192.168.0.89
    port: 8989
    api_token: someApiToken1234
  

  You would change the above configuration to the following:

  radarr:
    - host: 192.168.0.78
      port: 7878
      api_token: someApiToken1234
  sonarr:
    - host: 192.168.0.89
      port: 8989
      api_token: someApiToken1234
  

• The --config flag has been renamed to --config-fileto make it more clear what it does.

Features

• Users can now specify multiple instances of the same type of Servarr and give them custom names and ordering. This allows users to manage multiple instances of the same Servarr, such as an Anime and TV Show instance of Sonarr. To configure, add a list of Servarrs under the respective type (e.g. radarr, sonarr, etc.). (#17)

  • You can specify ordering of your Servarrs and how they will appear in the UI via the weight field. The lower the weight, the further to the left the Servarr will appear in the UI.
  • You can also name your Servarrs whatever you wish. This name will be displayed in the UI. For example, to name your Sonarr instances:

    sonarr:
      - name: Anime
        host: 192.168.0.89
        api_token: someApiToken
    
      - name: TV Shows
        host: 192.168.0.88
        api_token: someOtherApiToken
    

  • This change also required the introduction of a new CLI flag to specify which Servarr you wish to interact with: --servarr-name. This corresponds directly to the value of the name field in your configuration. If you did not specify a name in the configuration, then default names are provided for you corresponding to the Servarr; For example, if you defined two Radarr instances with no names, they will be named Radarr 1 and Radarr 2, respectively.
  • Omitting the --servarr-name flag with multi-instance configurations will default to using the first instance that appears in your config. For example, for the following configuration:

    sonarr:
      - host: 192.168.0.89
        api_token: someApiToken
    
      - host: 192.168.0.88
        api_token: someOtherApiToken
    

    Running managarr sonarr list series will default to interacting with the Sonarr instance at 192.168.0.89. This is the same as running managarr sonarr list series --servarr-name 'Sonarr 1'.

• API tokens can now be fetched from files instead of needing to be hardcoded (#31). The following is an example config that loads the API token from a file:

  radarr:
    - host: 192.168.0.78
      api_token_file: /home/root/.config/radarr_token
  

• Configurations now interpolate environment variables (#23). This allows you to load sensitive information from environment variables. For example, to load the API token from an environment variable, you can do the following:

  radarr:
    - host: 192.168.0.78
      api_token: ${MY_RADARR_API_TOKEN_ENV_VAR}
  

  This is available for all fields in the configuration file.

Security Updates

• Updated OpenSSL to v0.10.70 to mitigate CVE-2025-24898

Miscellaneous

• Managarr now has a Matrix space! Feel free to drop in and message me directly if you're looking to discuss features, ideas, or just want to say, "Hi!".

Managarr - A TUI and CLI to help you manage your Servarrs.

Thanks to everyone who contributed to this release, be that in code, issues, or enhancement suggestions! You all help fuel my passion for working on this and it doesn't go unappreciated! 😄

As always, you can try out the changes yourself via the Managarr Demo Site

Breaking Changes

• Managarr now supports multiple instances of the same Servarr with custom names and ordering. (See Features below) To accommodate this, configuration files must be updated so that all Servarrs listed beneath radarr, sonarr, etc., be updated to be lists, not individual Servarrs. For example: to migrate from the following config:

  radarr:
    host: 192.168.0.78
    port: 7878
    api_token: someApiToken1234
  sonarr:
    host: 192.168.0.89
    port: 8989
    api_token: someApiToken1234
  

  You would change the above configuration to the following:

  radarr:
    - host: 192.168.0.78
      port: 7878
      api_token: someApiToken1234
  sonarr:
    - host: 192.168.0.89
      port: 8989
      api_token: someApiToken1234
  

• The --config flag has been renamed to --config-fileto make it more clear what it does.

Features

• Users can now specify multiple instances of the same type of Servarr and give them custom names and ordering. This allows users to manage multiple instances of the same Servarr, such as an Anime and TV Show instance of Sonarr. To configure, add a list of Servarrs under the respective type (e.g. radarr, sonarr, etc.). (#17)

  • You can specify ordering of your Servarrs and how they will appear in the UI via the weight field. The lower the weight, the further to the left the Servarr will appear in the UI.
  • You can also name your Servarrs whatever you wish. This name will be displayed in the UI. For example, to name your Sonarr instances:

    sonarr:
      - name: Anime
        host: 192.168.0.89
        api_token: someApiToken
    
      - name: TV Shows
        host: 192.168.0.88
        api_token: someOtherApiToken
    

  • This change also required the introduction of a new CLI flag to specify which Servarr you wish to interact with: --servarr-name. This corresponds directly to the value of the name field in your configuration. If you did not specify a name in the configuration, then default names are provided for you corresponding to the Servarr; For example, if you defined two Radarr instances with no names, they will be named Radarr 1 and Radarr 2, respectively.
  • Omitting the --servarr-name flag with multi-instance configurations will default to using the first instance that appears in your config. For example, for the following configuration:

    sonarr:
      - host: 192.168.0.89
        api_token: someApiToken
    
      - host: 192.168.0.88
        api_token: someOtherApiToken
    

    Running managarr sonarr list series will default to interacting with the Sonarr instance at 192.168.0.89. This is the same as running managarr sonarr list series --servarr-name 'Sonarr 1'.

• API tokens can now be fetched from files instead of needing to be hardcoded (#31). The following is an example config that loads the API token from a file:

  radarr:
    - host: 192.168.0.78
      api_token_file: /home/root/.config/radarr_token
  

• Configurations now interpolate environment variables (#23). This allows you to load sensitive information from environment variables. For example, to load the API token from an environment variable, you can do the following:

  radarr:
    - host: 192.168.0.78
      api_token: ${MY_RADARR_API_TOKEN_ENV_VAR}
  

  This is available for all fields in the configuration file.

Security Updates

• Updated OpenSSL to v0.10.70 to mitigate CVE-2025-24898

Miscellaneous

• Managarr now has a Matrix space! Feel free to drop in and message me directly if you're looking to discuss features, ideas, or just want to say, "Hi!".

I was recently furloughed from work, so in between job applications, I decided to polish off Sonarr support in my Managarr TUI. Thus, I'm very proud to announce the beta release of Managarr with Sonarr support!

TL;DR: Managarr is a TUI and CLI for managing your Servarr instances. As of now, it now supports both Radarr and Sonarr and all the features that are available in the UI are also available in the CLI for scripting and additional automation.

The new version has the following features:

• Wider platform support (Windows, Mac, Linux, x86_64 and arm64)
• View your library, downloads, blocklist, episodes
• View details of a specific series, or episode including description, history, downloaded file info, or the credits
• View your host and security configs from the CLI to programmatically fetch the API token, among other settings
• Search your library
• Add series to your library
• Delete series, downloads, indexers, root folders, and episode files
• Trigger automatic searches for series, seasons, or episodes
• Trigger refresh and disk scan for series and downloads
• Manually search for series, seasons, or episodes
• Edit your series and indexers
• Manage your tags
• Manage your root folders
• Manage your blocklist
• View and browse logs, tasks, events queues, and updates
• Manually trigger scheduled tasks
• Manually trigger scheduled tasks
• And more!

Here's some screenshots of the Sonarr tab:

Thanks to everyone's feedback when I first posted the alpha release here, this version sports a handful of additional performance improvements and platform support.

This is now technically in beta, so if anyone encounters any issues, please let me know!

I was recently furloughed from work, so in between job applications, I decided to polish off Sonarr support in my Managarr TUI. Thus, I'm very proud to announce the beta release of Managarr with Sonarr support!

TL;DR: Managarr is a TUI and CLI for managing your Servarr instances. As of now, it now supports both Radarr and Sonarr and all the features that are available in the UI are also available in the CLI for scripting and additional automation.

The new version has the following features:

• Wider platform support (Windows, Mac, Linux, x86_64 and arm64)
• View your library, downloads, blocklist, episodes
• View details of a specific series, or episode including description, history, downloaded file info, or the credits
• View your host and security configs from the CLI to programmatically fetch the API token, among other settings
• Search your library
• Add series to your library
• Delete series, downloads, indexers, root folders, and episode files
• Trigger automatic searches for series, seasons, or episodes
• Trigger refresh and disk scan for series and downloads
• Manually search for series, seasons, or episodes
• Edit your series and indexers
• Manage your tags
• Manage your root folders
• Manage your blocklist
• View and browse logs, tasks, events queues, and updates
• Manually trigger scheduled tasks
• Manually trigger scheduled tasks
• And more!

Here's some screenshots of the Sonarr tab:

Thanks to everyone's feedback when I first posted the alpha release here, this version sports a handful of additional performance improvements and platform support.

This is now technically in beta, so if anyone encounters any issues, please let me know!

I was recently furloughed from work, so in between job applications, I decided to polish off Sonarr support in my Managarr TUI. Thus, I'm very proud to announce the beta release of Managarr with Sonarr support!

TL;DR: Managarr is a TUI and CLI for managing your Servarr instances. As of now, it now supports both Radarr and Sonarr and all the features that are available in the UI are also available in the CLI for scripting and additional automation.

The new version has the following features:

• Wider platform support (Windows, Mac, Linux, x86_64 and arm64)
• View your library, downloads, blocklist, episodes
• View details of a specific series, or episode including description, history, downloaded file info, or the credits
• View your host and security configs from the CLI to programmatically fetch the API token, among other settings
• Search your library
• Add series to your library
• Delete series, downloads, indexers, root folders, and episode files
• Trigger automatic searches for series, seasons, or episodes
• Trigger refresh and disk scan for series and downloads
• Manually search for series, seasons, or episodes
• Edit your series and indexers
• Manage your tags
• Manage your root folders
• Manage your blocklist
• View and browse logs, tasks, events queues, and updates
• Manually trigger scheduled tasks
• Manually trigger scheduled tasks
• And more!

Here's some screenshots of the Sonarr tab:

Thanks to everyone's feedback when I first posted the alpha release here, this version sports a handful of additional performance improvements and platform support.

This is now technically in beta, so if anyone encounters any issues, please let me know!