Repository navigation
Provide a bundled GUI client or a standalone desktop app instead of relying on heavy CLI setups #21
Description
What is your feature suggestion?
Setting up the environment for google-agents-cli on Windows is currently very friction-heavy for developers (managing Python versions, installing Google Cloud CLI separately, handling ADC authentication, and fighting PATH environment variables).
To make this amazing tool accessible to more creators, please consider productizing it into a standalone software/GUI. Instead of wrapping complex CLI dependencies that easily break on different OS platforms, a unified installer or an extension integrated directly into IDEs (like VS Code/Cursor) would dramatically improve the developer experience. Let's move away from environment setup hell!
What will this enable you to do?
Additional context
No response
Activity
optimization2026 commentedon Jun 30, 2026
I think a GUI/desktop client could help a lot, but the important design point is to keep the lifecycle contract clear.
A GUI should not hide the same setup gates that the CLI currently exposes.
It should make them more understandable:
A standard AISP V1.0.0 companion contract could define the setup wizard lifecycle:
[ { "role": "system", "content": { "protocol": "AISP V1.0.0", "axiom_0": "Human_Sovereignty_and_Wellbeing", "id": "google_agents_cli_desktop_setup_contract_aisp", "name": "Google Agents CLI Desktop Setup Contract", "version": "1.0.0", "license": "Apache-2.0", "summary": "A machine-checkable AISP package for a GUI/desktop setup wizard around agents-cli.", "description": "Defines setup gates for Python environment, Google Cloud CLI, ADC auth, project selection, region, manifest detection, eval readiness, and deploy readiness.", "flow_format": "mermaid", "loading_mode": "node", "tools": ["filesystem", "shell"], "params": { "workspace": "string", "platform": "string" }, "system_prompt": "" } }, { "role": "user", "content": { "instruction": "STRICTLY OBEY aisp_contract; its non_negotiable rules are inviolable; then RUN aisop.main", "user_input": "{user_input}", "aisp_contract": { "profile": "aisp.skill.v1", "invocation": { "mode": "desktop_setup_wizard", "when_to_use": [ "when onboarding users through GUI/desktop app", "when Windows setup is blocked by Python, gcloud, ADC, or PATH issues", "before enabling deploy/eval buttons" ], "when_not_to_use": [ "headless CI usage", "advanced CLI-only users who intentionally bypass GUI" ] }, "non_negotiable": [ { "rule": "GUI must show setup readiness gates instead of hiding failed prerequisites.", "enforced_by": "readiness.step2:sys.assert" }, { "rule": "Deploy action must remain blocked until project, auth, region, manifest, and eval/deploy prerequisites are valid.", "enforced_by": "deploy_gate.step2:sys.assert" }, { "rule": "GUI actions must map to equivalent CLI commands or documented internal APIs.", "enforced_by": "action_map.step2:sys.assert" } ], "discovery": { "category": "developer_experience", "tags": ["agents-cli", "gui", "desktop", "windows", "setup", "onboarding", "aisp"] }, "risk_level": "medium", "resources": [ { "id": "workspace", "path": "{workspace}", "kind": "workspace", "mode": "read_only", "when": "Read before GUI setup readiness checks.", "scope": "skill" } ] }, "aisop": { "main": "graph TD\n detect[Detect platform and workspace] --> readiness[Check setup readiness]\n readiness --> action_map[Map GUI actions to CLI/API]\n action_map --> eval_gate[Check eval readiness]\n eval_gate --> deploy_gate[Check deploy readiness]\n deploy_gate --> report[Show setup status]\n report --> end_node((End))" }, "functions": { "detect": { "step1": "Detect platform, workspace, existing project, Python, gcloud, auth, and PATH state.", "output_mapping": "environment_detection" }, "readiness": { "step1": "Evaluate setup gates: Python, agents-cli install, gcloud, ADC, project, region, manifest.", "step2": "sys.assert('readiness gates are visible to user', 'GUI must expose setup readiness gates')", "output_mapping": "setup_readiness" }, "action_map": { "step1": "Map GUI actions to CLI commands or internal APIs.", "step2": "sys.assert('GUI actions have command/API equivalents', 'GUI actions must map to supported operations')", "output_mapping": "gui_action_map" }, "eval_gate": { "step1": "Check whether eval setup is ready.", "output_mapping": "eval_readiness" }, "deploy_gate": { "step1": "Check deploy prerequisites.", "step2": "sys.assert('deploy prerequisites valid before enabling deploy', 'Deploy must be gated by readiness checks')", "output_mapping": "deploy_readiness" }, "report": { "step1": "Render setup checklist with fix actions and exact CLI equivalent commands.", "output_mapping": "desktop_setup_report" }, "end_node": { "step1": "Return desktop_setup_report." } } } } ]The GUI can make setup much easier, especially on Windows, while preserving the lifecycle gates:
A good MVP might be: