@spences10/pi-omnisearch

Verified web research workflow reminder that steers Pi agents to use mcp-omnisearch for current sourced answers

Packages

Package details

extension

Install @spences10/pi-omnisearch from npm and Pi will load the resources declared by the package manifest.

$ pi install npm:@spences10/pi-omnisearch
Package
@spences10/pi-omnisearch
Version
0.0.13
Published
May 21, 2026
Downloads
1,619/mo · 31/wk
Author
spences10
License
MIT
Types
extension
Size
10.9 KB
Dependencies
0 dependencies · 1 peer
Pi manifest JSON
{
  "extensions": [
    "./dist/index.js"
  ],
  "image": "https://raw.githubusercontent.com/spences10/my-pi/main/assets/pi-package-preview.png"
}

Security note

Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.

README

@spences10/pi-omnisearch

built with Vite+ tested with Vitest npm version license

my-pi package preview

Make agents verify current facts before answering. pi-omnisearch reminds the model to use the Omnisearch MCP tools for web search, extraction, and cited synthesis instead of relying on stale memory or snippets.

Installation

pi install npm:@spences10/pi-omnisearch

Local development from this monorepo:

pnpm --filter @spences10/pi-omnisearch run build
pi install ./packages/pi-omnisearch
# or for one run only
pi -e ./packages/pi-omnisearch

What it does

The extension injects a system reminder telling the model to use mcp-omnisearch when the user asks to:

  • research current information
  • verify facts or citations
  • inspect documentation
  • compare packages, APIs, or tools
  • extract and summarize web content

It encourages the verified research workflow from the ecosystem guide skill:

  • use web_search for discovery
  • use web_extract to read actual source content before making claims
  • use ai_search for synthesized answers with sources
  • prefer official docs, repositories, release notes, and source files
  • report partial failures, conflicts, and uncertainty

It adds no slash commands and no custom tools.

Example MCP config

mcp-omnisearch must be configured separately, for example in ~/.pi/agent/mcp.json:

{
	"mcpServers": {
		"mcp-omnisearch": {
			"command": "npx",
			"args": ["-y", "mcp-omnisearch"]
		}
	}
}

Using from a custom harness

import omnisearch from '@spences10/pi-omnisearch';

// pass `omnisearch` as an ExtensionFactory to your Pi runtime

my-pi imports this package directly and enables it as the built-in Omnisearch reminder.

Development

Package scripts build transitive workspace dependencies first, then run local tools through Vite+ with vp exec.

pnpm --filter @spences10/pi-omnisearch run check
pnpm --filter @spences10/pi-omnisearch run test
pnpm --filter @spences10/pi-omnisearch run build

License

MIT