Email contact@gramshift.com in English or Japanese. We reply within 7 business days, usually sooner. Please include your Windows version, your Stream Deck app version and, if possible, a photo or screenshot of the key.
AI Agents: my PC slept during a long command that Claude was running.
While a single command runs (for example a long build or test run), Claude Code writes nothing to its session file, so after the wait time the session no longer counts. Choose a longer Wait after activity (up to 30 minutes), or press Keep Awake as well for that run.
AI Agents: Claude ended its reply but a command is still running in the background.
The key counts the reply as finished. Background subagents are counted (they have their own session files), background shell commands are not. Use Keep Awake for that time if needed.
AI Agents: I stopped Claude with Esc, but the key still counts the session.
An interrupted reply is not marked as finished in the session file, so the session stops counting when the wait time runs out (the key does not read your messages to find out).
AI Agents: the key shows AI 0 for a moment after I start Claude Code.
New sessions are found within about 30 seconds (the folder is listed every 30 seconds to keep the plugin light). Sessions that were already found are checked every 5 seconds.
AI Agents: which Claude Code does it see?
Claude Code running on Windows, which saves its sessions in %USERPROFILE%\.claude\projects (or in the folder set by CLAUDE_CONFIG_DIR, if that is set for your Windows account). Claude Code inside WSL saves its sessions inside Linux, so the plugin cannot see them. Codex and other agents are not supported in version 1.1.
AI Agents: what does it read?
File names, times and sizes, and the end (at most 64 KB) of recently changed files, where it looks only at the kind of the last entry (from you or from Claude, reply finished or not, and the name of a tool Claude calls). It never keeps or sends your prompts, replies or code. See the Privacy Policy.
My PC still went to sleep.
Check that the key showed a countdown or "ON" at that time. The plugin cannot stop you from putting the PC to sleep yourself, so closing a laptop lid or pressing the power or sleep button still works as usual. Some company PCs have policies that override apps.
The screen turned off although the PC stayed awake.
Turn on "Keep the screen on too" in the key settings.
The screen saver still starts.
The plugin cannot block the screen saver (the Windows function it uses does not stop it). Change the screen saver in Windows Settings if you do not want it.
The key shows a warning triangle when I press it.
The plugin asks Windows to stay awake through Windows PowerShell, which is included with Windows. If PowerShell is blocked or removed on your PC (for example by a company policy), keeping awake cannot start and the key stays OFF.
"Until turned off" stopped by itself.
If no Keep Awake key has been visible on any Stream Deck for 1 hour (for example you removed the key), the plugin stops keeping the PC awake, so the PC cannot stay awake forever by accident. An Add Time key does not count, because it cannot stop "Until turned off". Timed sessions always run until their time is up.
Can I stop keeping awake with the Add Time key?
No. Add Time only adds time or starts a timer. Use a Keep Awake key to stop, or let the timer run out.
What happens if Stream Deck closes or the plugin stops?
Keeping awake ends within a few seconds and normal Windows sleep comes back. Your power plan is never changed.
How can I check that it works?
Open a Command Prompt as administrator and run powercfg /requests. While a Keep Awake key is running you will see powershell.exe under SYSTEM (and under DISPLAY if the screen option is on).
Does it work on Mac?
No. This plugin is for Windows 10 or later only.
The plugin runs entirely on your PC and sends no data anywhere. See the Privacy Policy.
Claude Code is a product of Anthropic. This plugin is not made by or affiliated with Anthropic.