Spatial AI Coding Assistant by Wherobots

Turn VS Code into an agentic geospatial engineering workspace. The Spatial AI Coding Assistant by Wherobots combines cloud-scale compute, notebook integration, MCP-powered SQL execution, and AI-assisted workflows so you can explore data, generate spatial SQL and Python, execute code, and submit jobs without leaving your IDE.

Why This Extension

• Build and run geospatial workflows where you already code, review, and iterate.
• Use Wherobots Cloud for agentic data analytics and execution with scalable runtimes and regions.
• Combine Copilot Chat + Wherobots MCP + cloud workspaces to move from question to runnable code quickly.
• Keep production-oriented controls in reach with configurable runtime size, region, timeout, API endpoint, and integration toggles.

What You Can Do

Agentic Analytics with Wherobots Cloud

Wherobots Cloud powers the execution layer behind this extension:

• Agentic analysis and execution: go from natural-language prompt to generated geospatial code to execution.
• Scale and performance: choose runtime sizes and regions for workload-appropriate compute.
• Security and governance controls: authenticate with API keys and target approved environments through settings.
• Unified developer flow: keep code authoring, AI assistance, runtime management, and job submission in one place.

Quickstart: Notebook-First Agentic Workflow

Use this path for first-run success with agentic notebook engineering.

1. Install this extension.
2. Generate a Wherobots API Key on Wherobots Cloud
3. Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P) and run Wherobots: Set API Key.
4. Create or open a notebook file (.ipynb).
5. Open the Wherobots sidebar and click the button to create a new workspace.
6. Once the workspace is running, from the notebook kernel picker, choose your new Wherobots workspace to connect.
7. Open Copilot Chat and ask it to write your notebook cells for the geospatial task.
8. Execute notebook cells using the connected Wherobots kernel.

Additional Workflow: Submit Python Jobs

When you want non-notebook execution:

1. Open a saved Python file (.py).
2. Open the Command Palette and run Wherobots: Submit Job.
3. Confirm job options in the form (runtime, region, args, timeout).
4. Submit and use the Open Job action from the success notification.

Inline Job Configuration in Python Files

You can provide job defaults directly in Python comments:

# wvsc-region: aws-us-west-2
# wvsc-instanceSize: medium
# wvsc-timeout: 7200
# wvsc-args: input.csv,output.csv

Supported keys:

• # wvsc-region: <region>
• # wvsc-instanceSize: <size> (also supports wvsc-runtime-size)
• # wvsc-timeout: <seconds>
• # wvsc-args: <arg1>,<arg2>,...

Feature and Command Reference

Core Commands

• Wherobots: Set API Key - Save or update your Wherobots API key securely.
• Wherobots: Generate API Key on Wherobots Cloud - Open the API key page in Wherobots Cloud.
• Wherobots: Submit Job - Submit the current saved .py file as a cloud job run.
• Wherobots: Install Jupyter Extension - Install VS Code Jupyter integration if missing.
• Wherobots: Create Workspace - Start a new Wherobots workspace.
• Wherobots: Refresh Workspaces - Refresh workspace list state.
• Wherobots: Open Settings - Open extension settings quickly.

Workspace Item Actions

• Connect Kernel - Connect the selected running workspace to a notebook kernel.
• Stop Workspace - Stop a running or starting workspace.
• Open in Browser - Open the workspace in the Wherobots web console.
• Open Spark UI - Open Spark UI for a running workspace when available.
• Copy Jupyter URL - Copy workspace Jupyter endpoint.
• Dismiss - Hide a failed workspace entry from the sidebar.

Settings Reference

All settings are under the wherobotsjobsubmit section in VS Code Settings.

• wherobotsjobsubmit.scriptPath - Cloud storage path used for submitted scripts; if empty, the extension uses your managed default path (data/customer-<your-user-id>/vscode-scripts).
• wherobotsjobsubmit.region - Default cloud region for job submission; if empty, organization default is used.
• wherobotsjobsubmit.instanceSize - Default runtime size for job submissions; if empty, organization default is used.
• wherobotsjobsubmit.timeout - Default job timeout in seconds for submissions.
• wherobotsjobsubmit.mcpServerEnabled - Enables or disables Wherobots MCP server exposure to AI assistants.
• wherobotsjobsubmit.apiBaseUrl - Overrides the Wherobots API base URL; leave empty for production default.
• wherobotsjobsubmit.mcpServerRuntimeId - Optional runtime ID header for MCP queries.
• wherobotsjobsubmit.mcpServerRuntimeRegion - Optional runtime region header for MCP queries.
• wherobotsjobsubmit.mcpServerQueryTimeout - Optional timeout (seconds) header for MCP queries.
• wherobotsjobsubmit.jupyterIntegrationEnabled - Enables or disables Wherobots in the Jupyter kernel picker.

Authentication and Security Notes

• API keys are stored in VS Code Secret Storage.
• MCP and cloud actions require a valid API key.
• If using custom endpoints (apiBaseUrl), ensure they are trusted and valid for your organization.

Troubleshooting and FAQ

"No API key set" or auth prompts keep appearing

• Run Wherobots: Set API Key again.
• If needed, generate a key with Wherobots: Generate API Key on Wherobots Cloud.

Workspace is visible but kernel connection fails

• Confirm the workspace status is running.
• Try Wherobots: Refresh Workspaces and reconnect from the kernel picker.
• Ensure Jupyter integration is enabled: wherobotsjobsubmit.jupyterIntegrationEnabled.

MCP tools do not appear in AI assistant workflows

• Confirm wherobotsjobsubmit.mcpServerEnabled is true.
• Verify your VS Code version supports MCP server definition providers.
• Re-check API key validity and optional MCP runtime/region/timeout settings.

"The current file is not a Python file" when submitting

• Job submission supports saved .py files.
• Save untitled files and confirm extension is .py before running Wherobots: Submit Job.

"No script path configured" warnings

• Set wherobotsjobsubmit.scriptPath to an explicit managed path if needed.
• If left empty, the extension derives a managed default path for your user.