← Back to AI Insights
Gemini Executive Synthesis

Windows service installation for a CLI/Telegram AI agent, specifically `mercury up/service install` command failures due to pathing issues with `schtasks` and `node.exe`.

Technical Positioning
Reliable, cross-platform deployment and continuous 24/7 operation for AI agents, leveraging native OS scheduling for seamless background execution on Windows.
SaaS Insight & Market Implications
This issue highlights critical friction in the `mercury-agent` deployment pipeline on Windows. The core problem is a `schtasks` command failure, likely due to incorrect path handling or escaping for `node.exe` within the service definition. Despite reporting success, the service fails to install or start, indicating a broken user experience for Windows deployments. This directly impacts the product's 'runs 24/7' value proposition, as continuous operation is contingent on reliable service installation. Market implications include reduced adoption among Windows-centric developer teams and increased support overhead. Robust, platform-native installation mechanisms are non-negotiable for agents targeting continuous background operation.
Proprietary Technical Taxonomy
system service schtasks PowerShell CMD admin access node.exe daemon Task Scheduler

Raw Developer Origin & Technical Request

Source Icon GitHub Issue Apr 26, 2026
Repo: cosmicstack-labs/mercury-agent
Service cannot be installed in Windows

mercury up/service install commands cannot install the service in Windows, failing with the following error message:

```
PS C:\Windows\System32> mercury up

Installing Mercury as a system service...
Error: Argumento u opción no válido - "Files\nodejs\node.exe C:\Users\chris\AppData\Roaming\npm\node_modules\@cosmicstack\mercury-agent\lib\node_modules\@cosmicstack\mercury-agent\dist\index.js start --daemon".
Escriba "SCHTASKS /CREATE /?" para su uso.
schtasks create failed. Try running from an Administrator cmd:
schtasks /create /tn "MercuryAgent" /tr ""C:\Program Files\nodejs\node.exe" "C:\Users\chris\AppData\Roaming\npm\node_modules\@cosmicstack\mercury-agent\lib\node_modules\@cosmicstack\mercury-agent\dist\index.js" start --daemon" /sc onlogon /rl limited /f
Error: El sistema no puede encontrar el archivo especificado.
Task created but failed to start immediately. It will start on next login.

Mercury service installed (Windows Task Scheduler)
Task: MercuryAgent
Trigger: on logon
Logs: C:\Users\chris\.mercury\daemon.log
Auto-starts on login. Use --daemon flag for crash recovery.

Uninstall: mercury service uninstall

Mercury started in background (PID: 18508)
```

It says that the service was installed, but it was not. Tried with PowerShell and CMD, both with and without admin access.

Developer Debate & Comments

No active discussions extracted for this entry yet.

Adjacent Repository Pain Points

Other highly discussed features and pain points extracted from cosmicstack-labs/mercury-agent.

Extracted Positioning
Integration of additional AI model providers (Kimi, GLM) and custom API endpoints compatible with OpenAI/Anthropic.
A flexible, provider-agnostic AI agent platform offering broad compatibility and choice for underlying AI models, reducing vendor lock-in and enabling access to specialized or cost-effective alternatives.
Top Replies
AriaShishegaran • Apr 25, 2026
Following up with the request to support Oauth login for existing subscriptions on coding plans for the existing providers and supporting ACP to be able to use Anthropic leagally as well.
fatinghenji • Apr 26, 2026
The same command request. I hope to see it implemented as soon as possible. I purchased kimi's coding plan, which only seems to support OAuth authorization.
cl1107 • Apr 26, 2026
please add custom openai/anthropic compatible endpoints

Frequently Asked Questions

Market intelligence mapped to Windows service installation for a CLI/Telegram AI agent, specifically `mercury up/service install` command failures due to pathing issues with `schtasks` and `node.exe`..

What problem does Windows service installation for a CLI/Telegram AI agent, specifically `mercury up/service install` command failures due to pathing issues with `schtasks` and `node.exe`. solve?
Based on our AI analysis of the original developer request, its primary technical positioning is: Reliable, cross-platform deployment and continuous 24/7 operation for AI agents, leveraging native OS scheduling for seamless background execution on Windows.
Which technical concepts are associated with Windows service installation for a CLI/Telegram AI agent, specifically `mercury up/service install` command failures due to pathing issues with `schtasks` and `node.exe`.?
Our proprietary extraction maps Windows service installation for a CLI/Telegram AI agent, specifically `mercury up/service install` command failures due to pathing issues with `schtasks` and `node.exe`. to adjacent architectural concepts including system service, schtasks, PowerShell, CMD.

Engagement Signals

0
Replies
open
Issue Status

Cross-Market Term Frequency

Quantifies the cross-market adoption of foundational terms like daemon and CMD by tracking occurrence frequency across active SaaS architectures and enterprise developer debates.