Research questions on the web and produce a report with source links. Read full pages, check important claims against independent sources, and clearly distinguish supported findings from uncertain evidence or disagreements.
Procedure for answering a question with a thorough, cross-checked, cited web-research report using the Keenable search + fetch tools.
Review the instructions the agent will receive before you install.
Use this for any question that needs current, verifiable information from the web. The deliverable is a synthesized answer where every load-bearing claim is backed by a source you actually read.
search_web_pages(query, [site], [published_after], [published_before], [mode])
— discover candidate sources. Write the query as a natural-language
description of the ideal page, not keywords. Use mode: pro (default).fetch_page_content(url, [max_chars]) — read the full page (markdown). A
search snippet is NEVER sufficient evidence — fetch before you cite.search_web_pages per sub-query. Prefer primary sources;
use published_after for anything time-sensitive.fetch_page_content on the 2-3 most promising results per
sub-query. Quote/cite only what you read, not what a snippet implied.Sources list of the URLs you actually fetched.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Test Omnigent’s native Antigravity integration with a live local server and the real agy CLI. Verify messages traveling between the web interface and terminal, mirrored replies, permission requests, interruption, session resumption, and process cleanup.
Test Omnigent’s Antigravity SDK integration against a live local server. Build test agents and run real conversations to check Gemini authentication, model selection, tool connections, and failures across the full execution path.
Create reference documentation directly from source code for public functions, classes, command-line commands, and endpoints. Organize parameters, defaults, return values, errors, and runnable examples, then check that the documentation matches the implementation.
Create an Omnigent agent directory using validated templates for configuration and instructions. Choose how the agent runs, then add web search, shell access, external tool connections, or subagents only when the task requires them.
Turn a selected range of commits or merged pull requests into release notes grouped by change type. Describe user-visible effects, link to supporting changes, and highlight breaking changes so readers can assess an upgrade.
Test Omnigent’s setup, help, and terminal interactions by driving the real CLI in an isolated environment. Capture rendered screens and compare checks before and after a change to establish whether a reported interface problem was fixed.