Getting Started

Guida is a Windows browser automation system built on WebView2. Guida Complete is the normal desktop app. Guida Node is a headed remote executor for browser/workspace automation. Both can expose Remote Ops, while MCP remains the local AI-agent integration surface.

Most users do not need the whole surface area on day one. Pick the path that matches what you are trying to do first.

Choose your path

I want to automate browser tasks manually

Start here if you want to click, type, navigate, extract content, and run scripts yourself.

1. Install Guida
2. Run your first script
3. Try the Open a page and inspect it recipe
4. Use Tools > Developer > Generate Scripting Support Files… for editor completions, language guides, and local LLM context files

I want an AI agent to browse under supervision

Start here if you want Claude Code, Claude Desktop, or another MCP client to operate Guida with approvals, domain controls, and audit history.

1. Read MCP Integration
2. Open a workspace so the agent has project-local scripts and configuration
3. Add custom tools when the agent needs repeatable workspace-specific actions
4. Review Source Boundaries to understand what stays local, what is audited, and what the closed scraping layer covers

I want to scrape and store data

Start here if your first goal is extraction, local storage, or moving scraped data into external systems.

1. Run the Quick Start to learn the basic script loop
2. Try the Scrape and store page data recipe
3. Read Data & Storage for g.store, g.queue, g.search, S3-compatible storage, MongoDB, PostgreSQL, and Elasticsearch
4. Use Database Integrations when you need external databases or object storage

I want to process queues and workers

Start here if you have many URLs or records to process across multiple browser tabs.

1. Open a workspace so Guida can create queue and store databases
2. Try the Queue URLs and process them recipe
3. Read Queue Workers for declarative and programmatic worker pools
4. Try the Run parallel workers recipe

I want a remote execution node

Start here if you want another machine to run headed browser automation, workspace workers, queues, and Remote Ops while you control it over a trusted private channel.

1. Install Guida Node only if you specifically need remote execution; otherwise install Guida Complete
2. Read Installation to choose between Guida Complete and Guida Node
3. Read Remote Ops API for the trusted-channel JSON-RPC control plane
4. Use Remote View when a client needs to stream or control a live browser tab

I want local LLM features

Start here if you want scripts to classify, summarize, or extract data with a local model.

1. Configure LLM Setup with Ollama or LlamaSharp
2. Try the Ask the local LLM recipe
3. Read AI, HTTP & Tools for g.llm.promptLocalLlm() and HTTP helpers
4. Combine LLM calls with Queue Workers for batch classification or extraction

I want to understand security and secrets

Start here if you are evaluating Guida for sensitive workflows, API credentials, or AI-assisted browsing.

1. Read MCP Integration for domain whitelisting, tool approval, and audit logging
2. Read Secrets for DPAPI-encrypted credentials and MCP-origin restrictions
3. Read Source Boundaries for what is closed, what is already public, and what will be opened once extracted and stable
4. Read Database Integrations if scripts need connection secrets for PostgreSQL, MongoDB, S3-compatible storage, or Elasticsearch

Common first actions

Task	Start here
Install Guida	Installation
Choose Complete vs Node	Installation
Run your first script	Quick Start
Open a workspace	Workspaces
Connect an MCP client	MCP Integration
Control a remote node	Remote Ops API
Use secrets safely	Secrets
Run queue workers	Queue Workers
Store or query extracted data	Data & Storage
Capture network traffic	Capture network traffic recipe

How it works

Scripts use the g.* API to control browser tabs, inspect the DOM, store data, run queues, call local LLMs, and integrate with workspace services. JavaScript and Janet methods return values directly and throw on error. Lua uses multiple returns.

await g.nav.navigateToUrl("https://example.com");
await g.dom.waitForDomStable();

const html = await g.page.getDom();
g.store.put("pages", "example", { html });

Everything runs on your machine. Workspace data stays in your workspace folder, app state stays under your Windows user profile, and Guida does not require accounts, telemetry, or cloud sync.