LogiGenie / AI Context

Your physical command center for AI. Use the dials on the MX Creative Console to fine-tune your creativity and buttons to set the tone, creating prompts instantly.

Comment

Inspiration

Our inspiration came directly from one of the examples suggested in the DevStudio 2026 call for proposals: "Genie in a bottle: Impersonate your AI assistants in a key." Today, interacting with Large Language Models (LLMs) is a friction-ridden process. Users waste a lot of time typing repetitive prompts to define the tone, role, or creativity level of the artificial intelligence. We realized we could transform abstract software parameters into physical controls, bringing tactility back to the creative workflow and making AI truly accessible at our fingertips.

What it does

LogiGenie / AI Context transforms the Logitech MX Creative Console into a physical control panel for your AI assistants.

LCD Buttons: Instantly "personalize" the AI ​​(e.g., one button gives you a "Code Reviewer" tone, another a "Creative Writer" tone, and another a "Technical Translator" tone).

Analog Dials: Allow you to adjust model parameters in real time. For example, turning the main dial adjusts the AI's "Temperature" (creativity) before sending the command, without having to type complex instructions.

How we built it

We built LogiGenie using the Logi Actions SDK, developing all the logic in C# and leveraging the .NET 8 framework.

We started by using the globally installed LogiPluginTool command-line tool (dotnet tool install --global LogiPluginTool) to generate the project's base template.

Challenges we ran into

One of the main technical challenges was understanding the SDK's local deployment architecture. Initially, we struggled to get the host software to recognize our updates. We discovered that we needed to ensure the .link file was correctly generated in the LogiPluginService directory (C:\Users\USERNAME\AppData\Local\Logi\LogiPluginService\Plugins) for Logitech Options+ to load the plugin.

Additionally, iterating through the code became slow due to manual recompiling. We resolved this by implementing the .NET Hot Reload feature suggested in the documentation. By navigating to our project's src directory and running dotnet watch build, we were able to automatically rebuild and reload the plugin when saving a source file.

Accomplishments that we're proud of

We are very proud to have created a deep integration that appears natively under the "Installed Plugins" section of the Logitech Options+ graphical interface.

We have built a seamless user experience (UX) where pressing a physical button on the console instantly captures the selected text from the operating system, applies the desired AI context, and returns the result, eliminating the need to open a browser tab.

What we learned

Aprendimos a estructurar proyectos modulares usando C# para crear acciones con y sin parámetros dentro del entorno del Logi Actions SDK. Beyond the code, we learned a valuable UX design lesson: tactility dramatically reduces cognitive load. Giving users a physical button for a complex AI task fosters a much faster and more creative workflow.

What's next for LogiGenie / AI Context

The next step is deep haptic integration for MX Master 4 and Actions Ring users.

We want to send a specific tactile response (a "click" or a virtual vibration) to the user's mouse at the exact moment the AI ​​finishes processing and generating the text response, so they can continue working on another screen without looking at loading bars.

Finally, we'll prepare to package and distribute the plugin, ensuring compliance with all Marketplace Approval Guidelines for publication on the Logitech Marketplace, allowing us to reach millions of users.

Built With

  • c#
  • gemini-api
  • logi-actions-sdk
  • logiplugintool
  • logitech-options-plus
  • net-8
  • openai-api
Share this project:

Updates