[Pi Series 6] Installable pi packages 2: web research and advanced operations

In the previous post, we looked at packages that help almost everywhere: resource management, structured questions, and document parsing.

This post starts with the web research package @demigodmode/pi-web-agent, then explains how to think about more advanced extensions and package scope.

---

What this post covers

• Install @demigodmode/pi-web-agent
• Check it with /web-agent doctor
• Understand when to use web_explore
• Adjust web result presentation modes
• Choose advanced extensions with the right criteria
• Decide between global and project-local installs

---

1. @demigodmode/pi-web-agent

Install

pi install npm:@demigodmode/pi-web-agent

After installation, restart pi or run /reload.

/reload

This package requires Pi 0.74 or newer. If your pi version is old, update pi first.

pi update --self

Check installation

Run the doctor command inside pi.

/web-agent doctor

You can also open the action menu.

/web-agent

Open settings with:

/web-agent settings

Use

This package provides a research tool called web_explore. In normal use, you do not need to call the tool with a raw tool-call format. Just ask for web research in natural language.

Example:

Research popular pi packages and summarize their install commands and use cases.

If you want to be explicit:

Use web_explore to research the pi coding agent package installation docs and summarize the key commands.

web_explore is designed as one bounded workflow that handles search, fetch, targeted headless rendering when needed, and source notes. Instead of exposing many separate web tools to the model, you give it one research question.

When it is useful

• Checking current official documentation
• Comparing npm packages or GitHub repositories
• Searching an error message
• Verifying sources before writing a blog post
• Research tasks that need evidence and caveats, not just a quick search result

One caveat: headless rendering fallback may require a Chromium-family browser such as Chrome, Chromium, Edge, or Brave. Search and plain HTTP reads can still work without it, but pages that require rendering may be limited.

---

Change presentation mode

pi-web-agent can adjust how results are displayed.

/web-agent mode preview
/web-agent mode web_explore verbose
/web-agent mode web_explore inherit

To see the current settings:

/web-agent show

A simple guide:

Mode	When to use
compact	When you only need the conclusion quickly
preview	When you want key evidence with the conclusion
verbose	When preparing a blog post or report with source details

---

2. Look for packages before advanced .ts examples

The official examples include many advanced extension files:

permission-gate.ts
protected-paths.ts
git-checkpoint.ts
preset.ts
plan-mode/
ssh.ts
subagent/

But these names are not install commands. For most users, it is better to look for a package first instead of copying .ts files.

A good order is:

1. Search /resource or the package gallery for the feature you want.
2. Check the package README for install instructions.
3. Install with pi install npm:... or pi install git:....
4. Check the slash commands or tools the package provides.
5. Only if no package exists, use the official .ts examples as a base for your own setup.

Advanced extensions should be consumed as packages first, and customized only when necessary.

---

3. What advanced features should you look for?

Even when a feature is not packaged yet, it helps to know what categories to search for.

Category	Feature to look for
Safety	Confirm dangerous bash commands, protect paths
Git recovery	Turn-level checkpoints, auto commits, session bookmarks
Context management	Custom compaction, compact triggers, handoff
Workflow	Presets, tool enable/disable, plan mode, TODO management
UI/notifications	Notifications, status line, model status, custom footer
Integrations	GitHub issues, SSH, custom providers, subagents

This table does not mean “install these exact names now.” It is a map of search keywords.

For example, if you want dangerous-command confirmation, search for words like permission, guard, safe, or protected. For web research, search for web, search, or research. For document handling, search for doc, pdf, or ocr.

---

4. Global vs project-local installs

Web research and document parsing are useful, but not every project needs them all the time. Separating install scope keeps pi from becoming heavy again.

Good global candidates:

pi install npm:pi-resource-center
pi install npm:@eko24ive/pi-ask

Good project-local candidates:

pi install npm:@demigodmode/pi-web-agent -l
pi install npm:pi-docparser -l

A simple decision table:

Question	Global install	Project-local install
Do you use it in every project?	Yes	No
Does it need network access?	Be careful	Often better
Does it process documents or images?	If used often	If project-specific
Should the team share it?	Personal tool: global	Team standard: project

---

5. My recommended starting set

Start with this:

pi install npm:pi-resource-center
pi install npm:@eko24ive/pi-ask

Add web research when needed:

pi install npm:@demigodmode/pi-web-agent

Add document parsing when needed:

pi install npm:pi-docparser

Check them with:

/resource
/ask-settings
/web-agent doctor
/docparser:doctor

You can install all four globally, but if you want stricter project separation, install pi-web-agent and pi-docparser with -l.

---

Security checklist

Web research, document parsing, SSH, and custom provider packages can have broader permissions and network access. Before installing, check:

• Does the README clearly explain install and usage commands?
• What tools or slash commands does it add?
• Does it send network requests?
• Does it read or write local files?
• Does it require a browser or host dependency?
• Does it handle API keys, tokens, or cookies?
• Would a project-local install be safer than a global install?

Using useful packages is good. Keeping packages enabled without understanding their permissions is not.

---

Summary

Purpose	Install	Check/use
Web research	pi install npm:@demigodmode/pi-web-agent	/web-agent doctor
Package browsing	pi install npm:pi-resource-center	/resource
Structured questions	pi install npm:@eko24ive/pi-ask	/ask-settings, /answer
Document parsing	pi install npm:pi-docparser	/docparser:doctor
Project-local install	pi install npm:package -l	.pi/settings.json

Using pi lightly does not mean avoiding packages. It means installing the packages you need, choosing the right scope, and understanding their permissions.