agent-browser

Automatisation de navigateur pour agents IA via inference.sh. Naviguer sur des pages web, interagir avec des éléments en utilisant les références @e, prendre des captures d'écran, enregistrer des vidéos. Capacités : scraping web, remplissage de formulaires, clics, saisie, glisser-déposer, téléchargement de fichiers, exécution JavaScript. Utilisation pour : automatisation web, extraction de données, tests, navigation agent, recherche. Déclencheurs : navigateur, automatisation web, scraping, navigation, clic, remplissage de formulaire, capture d'écran, navigation web, playwright, navigateur headless, agent web, surf internet, enregistrement vidéo

npx skills add https://github.com/halt-catch-fire/skills --skill agent-browser

Install the belt CLI skill: npx skills add belt-sh/cli

Agentic Browser

Browser automation for AI agents via inference.sh. Uses Playwright under the hood with a simple @e ref system for element interaction.

Agentic Browser

Quick Start

Requires inference.sh CLI (belt). Install instructions

belt login

# Open a page and get interactive elements
belt app run agent-browser --function open --input '{"url": "https://example.com"}' --session new

Core Workflow

Every browser automation follows this pattern:

  1. Open - Navigate to URL, get @e refs for elements
  2. Interact - Use refs to click, fill, drag, etc.
  3. Re-snapshot - After navigation/changes, get fresh refs
  4. Close - End session (returns video if recording)
# 1. Start session
RESULT=$(belt app run agent-browser --function open --session new --input '{
  "url": "https://example.com/login"
}')
SESSION_ID=$(echo $RESULT | jq -r '.session_id')
# Elements: @e1 [input] "Email", @e2 [input] "Password", @e3 [button] "Sign In"

# 2. Fill and submit
belt app run agent-browser --function interact --session $SESSION_ID --input '{
  "action": "fill", "ref": "@e1", "text": "user@example.com"
}'
belt app run agent-browser --function interact --session $SESSION_ID --input '{
  "action": "fill", "ref": "@e2", "text": "password123"
}'
belt app run agent-browser --function interact --session $SESSION_ID --input '{
  "action": "click", "ref": "@e3"
}'

# 3. Re-snapshot after navigation
belt app run agent-browser --function snapshot --session $SESSION_ID --input '{}'

# 4. Close when done
belt app run agent-browser --function close --session $SESSION_ID --input '{}'

Functions

FunctionDescription
openNavigate to URL, configure browser (viewport, proxy, video recording)
snapshotRe-fetch page state with @e refs after DOM changes
interactPerform actions using @e refs (click, fill, drag, upload, etc.)
screenshotTake page screenshot (viewport or full page)
executeRun JavaScript code on the page
closeClose session, returns video if recording was enabled

Interact Actions

ActionDescriptionRequired Fields
clickClick elementref
dblclickDouble-click elementref
fillClear and type textref, text
typeType text (no clear)text
pressPress key (Enter, Tab, etc.)text
selectSelect dropdown optionref, text
hoverHover over elementref
checkCheck checkboxref
uncheckUncheck checkboxref
dragDrag and dropref, target_ref
uploadUpload file(s)ref, file_paths
scrollScroll pagedirection (up/down/left/right), scroll_amount
backGo back in history-
waitWait millisecondswait_ms
gotoNavigate to URLurl

Element Refs

Elements are returned with @e refs:

@e1 [a] "Home" href="/"
@e2 [input type="text"] placeholder="Search"
@e3 [button] "Submit"
@e4 [select] "Choose option"
@e5 [input type="checkbox"] name="agree"

Important: Refs are invalidated after navigation. Always re-snapshot after:

  • Clicking links/buttons that navigate
  • Form submissions
  • Dynamic content loading

Features

Video Recording

Record browser sessions for debugging or documentation:

# Start with recording enabled (optionally show cursor indicator)
SESSION=$(belt app run agent-browser --function open --session new --input '{
  "url": "https://example.com",
  "record_video": true,
  "show_cursor": true
}' | jq -r '.session_id')

# ... perform actions ...

# Close to get the video file
belt app run agent-browser --function close --session $SESSION --input '{}'
# Returns: {"success": true, "video": <File>}

Cursor Indicator

Show a visible cursor in screenshots and video (useful for demos):

belt app run agent-browser --function open --session new --input '{
  "url": "https://example.com",
  "show_cursor": true,
  "record_video": true
}'

The cursor appears as a red dot that follows mouse movements and shows click feedback.

Proxy Support

Route traffic through a proxy server:

belt app run agent-browser --function open --session new --input '{
  "url": "https://example.com",
  "proxy_url": "http://proxy.example.com:8080",
  "proxy_username": "user",
  "proxy_password": "pass"
}'

File Upload

Upload files to file inputs:

belt app run agent-browser --function interact --session $SESSION --input '{
  "action": "upload",
  "ref": "@e5",
  "file_paths": ["/path/to/file.pdf"]
}'

Drag and Drop

Drag elements to targets:

belt app run agent-browser --function interact --session $SESSION --input '{
  "action": "drag",
  "ref": "@e1",
  "target_ref": "@e2"
}'

JavaScript Execution

Run custom JavaScript:

belt app run agent-browser --function execute --session $SESSION --input '{
  "code": "document.querySelectorAll(\"h2\").length"
}'
# Returns: {"result": "5", "screenshot": <File>}

Deep-Dive Documentation

ReferenceDescription
references/commands.mdFull function reference with all options
references/snapshot-refs.mdRef lifecycle, invalidation rules, troubleshooting
references/session-management.mdSession persistence, parallel sessions
references/authentication.mdLogin flows, OAuth, 2FA handling
references/video-recording.mdRecording workflows for debugging
references/proxy-support.mdProxy configuration, geo-testing

Ready-to-Use Templates

TemplateDescription
templates/form-automation.shForm filling with validation
templates/authenticated-session.shLogin once, reuse session
templates/capture-workflow.shContent extraction with screenshots

Examples

Form Submission

SESSION=$(belt app run agent-browser --function open --session new --input '{
  "url": "https://example.com/contact"
}' | jq -r '.session_id')

# Get elements: @e1 [input] "Name", @e2 [input] "Email", @e3 [textarea], @e4 [button] "Send"

belt app run agent-browser --function interact --session $SESSION --input '{"action": "fill", "ref": "@e1", "text": "John Doe"}'
belt app run agent-browser --function interact --session $SESSION --input '{"action": "fill", "ref": "@e2", "text": "john@example.com"}'
belt app run agent-browser --function interact --session $SESSION --input '{"action": "fill", "ref": "@e3", "text": "Hello!"}'
belt app run agent-browser --function interact --session $SESSION --input '{"action": "click", "ref": "@e4"}'

belt app run agent-browser --function snapshot --session $SESSION --input '{}'
belt app run agent-browser --function close --session $SESSION --input '{}'

Search and Extract

SESSION=$(belt app run agent-browser --function open --session new --input '{
  "url": "https://google.com"
}' | jq -r '.session_id')

belt app run agent-browser --function interact --session $SESSION --input '{"action": "fill", "ref": "@e1", "text": "weather today"}'
belt app run agent-browser --function interact --session $SESSION --input '{"action": "press", "text": "Enter"}'
belt app run agent-browser --function interact --session $SESSION --input '{"action": "wait", "wait_ms": 2000}'

belt app run agent-browser --function snapshot --session $SESSION --input '{}'
belt app run agent-browser --function close --session $SESSION --input '{}'

Screenshot with Video

SESSION=$(belt app run agent-browser --function open --session new --input '{
  "url": "https://example.com",
  "record_video": true
}' | jq -r '.session_id')

# Take full page screenshot
belt app run agent-browser --function screenshot --session $SESSION --input '{
  "full_page": true
}'

# Close and get video
RESULT=$(belt app run agent-browser --function close --session $SESSION --input '{}')
echo $RESULT | jq '.video'

Sessions

Browser state persists within a session. Always:

  1. Start with --session new on first call
  2. Use returned session_id for subsequent calls
  3. Close session when done

Related Skills

# Web search (for research + browse)
npx skills add inference-sh/skills@web-search

# LLM models (analyze extracted content)
npx skills add inference-sh/skills@llm-models

Documentation

Plus de skills de halt-catch-fire

ai-image-generation
halt-catch-fire
Générez des images IA avec GPT-Image-2, FLUX, Gemini, Grok, Seedream, Reve et plus de 50 modèles via l'interface CLI inference.sh. Modèles : GPT-Image-2, FLUX Dev LoRA, FLUX.2 Klein LoRA, Gemini 3 Pro Image, Grok Imagine, Seedream 4.5, Reve, ImagineArt. Capacités : texte vers image, image vers image, inpainting, LoRA, édition d'image, upscaling, rendu de texte. Utilisation pour : art IA, maquettes de produits, concept art, graphiques pour réseaux sociaux, visuels marketing, illustrations. Déclencheurs : flux, génération d'image, image IA, texte vers...
creativemediaimage
ai-video-generation
halt-catch-fire
We need to translate the given text from English to French. The text describes an AI video generation skill. We must preserve the name "ai-video-generation" but it's not in the text, so we ignore. Preserve product names, protocol names, URLs, numbers, technical terms. So "Google Veo", "Seedance 2.0", "HappyHorse", "Wan", "Grok", "inference.sh CLI", "Veo 3.1", "Veo 3", "Seedance 2.0", "HappyHorse 1.0", "Wan 2.5", "Grok Imagine Video", "OmniHuman", "Fabric", "HunyuanVideo", "text-to-video", "image-to-video", "reference-to-video", "video editing", "lipsync", "avatar animation", "video upscaling", "foley sound", "social media videos", "marketing content", "explainer videos", "product demos", "AI avatars",
creativevideomedia
twitter-automation
halt-catch-fire
Automatisez Twitter/X avec publication, engagement et gestion des utilisateurs via l'interface CLI inference.sh. Applications : x/post-tweet, x/post-create (avec média), x/post-like, x/post-retweet, x/dm-send, x/user-follow. Capacités : publier des tweets, planifier du contenu, aimer des publications, retweeter, envoyer des messages directs, suivre des utilisateurs, obtenir des profils. Utilisation pour : automatisation des réseaux sociaux, planification de contenu, bots d'engagement, croissance d'audience, API X. Déclencheurs : twitter api, x api, tweet automation, post to twitter, twitter bot, social media automation, x...
marketingapicommunication
ai-avatar-video
halt-catch-fire
We need to translate the given text from English to French, preserving the name "ai-avatar-video" and other technical terms. The text describes creating AI avatar and talking head videos via inference.sh CLI. It recommends P-Video-Avatar, and lists other options: OmniHuman, Fabric, PixVerse. Audio options: Inworld TTS-2, ElevenLabs, Kokoro. Capabilities: audio-driven avatars, text-to-avatar, lipsync videos, talking head generation, virtual presenters, UGC content. Use for: AI presenters, explainer videos, virtual influencers, dubbing, marketing videos, UGC ads, gaming avatars,... We must not include the name "ai-avatar-video" unless it appears in the source text. It does not appear in the source text, so we omit it. We translate the rest naturally. Keep product names, protocol names, URLs, numbers, technical terms as is. So "inference.sh CLI" stays, "P-Video-Avatar", "OmniHuman", "F
videocreativemedia
web-search
halt-catch-fire
Recherche web et extraction de contenu avec Tavily et Exa via l'interface en ligne de commande inference.sh. Applications : Tavily Search, Tavily Extract, Exa Search, Exa Answer, Exa Extract. Capacités : recherche assistée par IA, extraction de contenu, réponses directes, recherche documentaire. Utilisation pour : recherche, pipelines RAG, vérification des faits, agrégation de contenu, agents. Déclencheurs : recherche web, tavily, exa, api de recherche, extraction de contenu, recherche, recherche internet, recherche IA, assistant de recherche, scraping web, rag, alternative à perplexity
researchweb-scrapingapi
infsh-cli
halt-catch-fire
We need to translate the given text from English to French, preserving the name "infsh-cli" and other technical terms, product names, protocol names, URLs, numbers, etc. The instruction says: "Do not include the name unless it appears in the source text." The name "infsh-cli" is not in the source text, so we don't include it. The source text has "inference.sh CLI" - that should be preserved as is? The instruction says preserve product names, so "inference.sh CLI" should stay. Also "FLUX, Veo, Gemini, Grok, Claude, Seedance, OmniHuman, Tavily, Exa, OpenRouter" are product names, keep them. "Twitter" is a product name. "AI" is a term, keep as is or translate? Usually "IA" in French, but the instruction says preserve technical terms? "AI" is a common acronym, often kept as is. But in French, "IA" is used. However, the instruction says "preserve product names
developmentapicreative
landing-page-design
halt-catch-fire
We need to translate the given text from English to French. The text is a description of an agent skill for landing page design. We must preserve the name "landing-page-design" but it's not in the text, so we don't include it. We translate only the text inside <text>. No extra labels. Keep technical terms like "CTA", "F-pattern", "SaaS", etc. as is or translate if appropriate? The instruction says preserve technical terms, so "CTA" stays, "F-pattern" might be kept or translated? Usually "F-pattern" is a known term, but in French it might be "motif en F" or keep as is. Since it's a technical term, I'll keep "F-pattern" as is. "above-the-fold" is a term, often kept as "above-the-fold" or "au-dessus de la ligne de flottaison". I'll keep as "above-the-fold" for consistency. "social proof" -> "preuve sociale". "mobile design" -> "conception mobile
product-photography
halt-catch-fire
We need to translate the given text from English to French. The text describes an AI product photography skill. We must preserve the name "product-photography" but it's not in the text, so we don't include it. We translate only the text inside <text>. No extra labels. Keep technical terms like "packshot", "hero shot", "lifestyle shots", "e-commerce", "Amazon" as is or with appropriate French translation? The instruction says preserve product names, protocol names, URLs, numbers, technical terms. "Amazon" is a product name, keep as is. "packshot" is a technical term, often kept in English in French contexts, but could be translated? The instruction says preserve technical terms, so keep "packshot". "hero shot" is also technical, keep. "lifestyle shots" - "lifestyle" is often used in French, but "shots" might be translated as "photos" or kept. I'll keep "lifestyle shots" as is. "studio lighting" - "éclairage studio".
creativeecommerceimage