Start with ChatGPT Free
Open Plugins and connect the services you already use. Availability can vary by account and region, but the plugin directory is available across ChatGPT plans.
Practical guide
You do not need to start with a big API budget. Connect an AI to the services and computer you already use, then let it do most of the technical setup for you.
Open Plugins and connect the services you already use. Availability can vary by account and region, but the plugin directory is available across ChatGPT plans.
If Gmail is available on your account, connect it before automating the Gmail website. Direct connectors are usually faster and more reliable for reading, searching, drafting, and supported send actions.
This is the turning point. It gives the AI controlled access to your computer or server: terminal, files, code, processes, and scripts.
Once it works, stop following most setup guides by hand. Ask the AI to install, test, document, and maintain the rest.
Paste a clear goal instead of manually installing every component:
Set this computer up as a safe AI automation workstation. Install and verify agent-browser, create persistent browser sessions where useful, prefer direct connectors when available, and document what you change. Do not hard-code passwords or secrets. Stop for me when a login, permission, CAPTCHA, 2FA prompt, or other human approval is required.
agent-browser gives the AI browser control for normal websites: navigation, clicking, typing, forms, uploads, screenshots, and page inspection. The AI can install and verify it through Desktop Commander.
If you want to do it manually, the recommended install is npm install -g agent-browser followed by agent-browser install.
Use Bitwarden Password Manager for normal logins. For agent credentials, prefer narrowly scoped secrets through Bitwarden Secrets Manager or another secrets broker instead of passwords embedded in scripts.
Ask ChatGPT to run recurring or monitoring work for you. Free accounts can keep up to three active scheduled tasks, with recurring tasks running at most once per day. Supported connected apps such as Gmail can be used inside scheduled tasks.
Example: “Every morning, check my Gmail and summarize anything important.” Event-triggered tasks such as “when a new Gmail arrives” require an eligible paid plan.
Use this order: direct connector first → browser automation second → full desktop/UI control only when needed.
Use Scheduled Tasks for recurring cloud work, and Desktop Commander + agent-browser when the AI needs to operate your own computer or a website directly.
Claude works too. Claude Free can use connectors, and Claude Desktop supports local desktop extensions/MCP. Free users currently get one custom remote connector, so the exact setup limits differ from ChatGPT, but the same architecture applies.
When local browser automation struggles: a managed service such as TinyFish can be a useful paid fallback for difficult websites. Start local first to keep cost and lock-in low.
OpenAI’s current plugin and availability guide.
OpenAI’s current guide to one-time, recurring, monitoring, and event-triggered tasks.
Connect an authorized computer or server to an AI assistant.
Open-source browser automation CLI for AI agents.
Password Manager and Secrets Manager for safer credential handling.
Anthropic’s current connector and MCP setup guidance.
Optional managed browser automation when a local browser is not enough.