seed-network-agent

The Seed Network Agent is a wrapped version of the pi coding agent. It is focused on interacting with the seed network, not coding.

Boundary

Seed-owned behavior:

• prompts/*
• src/extension/* — Pi extension entrypoint and shared extension types
• src/features/* — feature modules registered by the extension
• src/wizard.ts — shared deterministic questionnaire helper used by feature commands

Pi boundary:

• src/pi.ts

Only src/pi.ts should import or execute Pi directly. Feature modules are normal upstream Pi extension code registered through src/extension/index.ts.

Feature layout

Features should be easy to find and remove. Add new Seed Agent behavior under src/features/<feature-name>/, then register it from src/extension/index.ts.

Current features:

• features/branding — Seed header/title customization.
• features/agent-auth — /connect and /seed Agent Auth management commands.
• features/submit-deal-pdf — /create-deal PDF draft intake/background interpretation and /submit-deal final capability execution.
• features/venture-partner-persona — prompt-only deal draft Venture Partner mode and /show-thesis thesis previews.

Pi supports this directory-extension shape directly: a multi-file extension is an index.ts entrypoint plus helper modules.

What we changed

1. Start Pi with Seed Network Agent resources loaded.
2. Register Seed feature modules from src/extension/index.ts.
3. Load versioned feature questionnaires from each feature directory.
4. Add /create-deal for local PDF deal draft intake with background deck interpretation/upload.
5. Add /submit-deal to submit the active deal draft to Seed Network when the user is ready.
6. Add prompt-only Venture Partner mode for active deal drafts, with repeatable /show-thesis previews.
7. Add /connect and /seed commands for Agent Auth connection management.

What we do not change

• Pi model/provider logic
• Pi auth behavior
• Pi session engine
• Pi tool execution internals
• Pi TUI internals
• Pi package manager

Install

Install the published CLI globally:

npm install -g @connormartin/seed-network-agent
seed

Or run the latest version without a global install:

npx @connormartin/seed-network-agent@latest

The CLI checks npm for updates at startup at most once per day and prints the exact update command when a newer version is available. Disable this with SEED_NETWORK_AGENT_NO_UPDATE_CHECK=1.

Pi compatibility and isolation

seed runs on top of Pi, but it does not share Pi's normal global files. The wrapper forces Pi to use Seed-owned paths:

• Pi config/auth/packages/tools: ~/.seed-network-agent/pi/
• Pi sessions: ~/.seed-network-agent/pi/sessions/
• Seed Agent Auth grants: ~/.seed-network-agent/auth/

This keeps Seed installs compatible with users who already have pi installed and avoids loading or updating packages from ~/.pi/agent. The wrapper also disables Pi's own version check with PI_SKIP_VERSION_CHECK=1; Seed Network Agent has its own npm update check.

Override the isolated Pi paths with SEED_NETWORK_AGENT_PI_DIR or SEED_NETWORK_AGENT_PI_SESSION_DIR if needed. To force Pi's startup network operations off entirely, set SEED_NETWORK_AGENT_PI_OFFLINE=1. If the current project has .pi/settings.json with package entries, the wrapper also starts Pi offline to avoid project Pi packages triggering SSH/Git prompts; set SEED_NETWORK_AGENT_ALLOW_PROJECT_PI_PACKAGES=1 to opt into those project package operations.

Update, build, and publish

From the repository root, make the agent changes, then build the package:

pnpm --filter @connormartin/seed-network-agent build

Before publishing, bump the npm package version in apps/agent/package.json to a version higher than the current npm latest:

npm view @connormartin/seed-network-agent version
cd apps/agent
npm version <next-version> --no-git-tag-version

Use semver patch/minor/major as appropriate. For example, if npm latest is 0.1.3, publish 0.1.4 or higher. Then verify the package contents and publish:

npm pack --dry-run
npm publish --access public

After publishing, users can update their installed CLI with:

npm install -g @connormartin/seed-network-agent@latest

If npm returns ETARGET immediately after publishing, the registry metadata and tarball may not have fully propagated yet. Wait a minute, verify the package, then retry with fresh registry metadata:

npm view @connormartin/seed-network-agent version versions
npm install -g @connormartin/seed-network-agent@latest --prefer-online --registry=https://registry.npmjs.org/
hash -r

Or run the latest version directly:

npx @connormartin/seed-network-agent@latest

Run locally

From the repository root:

pnpm agent

Build the publishable CLI from apps/agent:

pnpm --filter @connormartin/seed-network-agent build
pnpm --filter @connormartin/seed-network-agent start

Run /seed-help inside the agent to see the Seed-specific commands. Run /create-deal to create a local deal draft from a pitch deck PDF and intake questions. The deck is interpreted/uploaded in the background, Venture Partner mode starts immediately after the draft is created, and /submit-deal submits the active draft to Seed Network when ready.

You can forward normal Pi flags through the wrapper:

pnpm agent -- --model anthropic/claude-sonnet-4-5

Seed Agent Auth

The wrapper can connect to the Seed Network web app as an Agent Auth client:

/connect [provider-url]
/seed status
/seed disconnect

By default, the published npm CLI (seed) connects to https://seed-network-v2.vercel.app/, while the local source command (pnpm agent) connects to http://localhost:3000 for development. Override either with SEED_NETWORK_AGENT_AUTH_PROVIDER. Agent Auth identity and grants are stored locally under ~/.seed-network-agent/auth/.

If /submit-deal fails with fetch failed during PDF upload, check the upload URL in the error. If it mentions localhost:3000, remove stale local Agent Auth state and reconnect to production:

/seed disconnect
/connect

You can also force the provider for one run:

SEED_NETWORK_AGENT_AUTH_PROVIDER=https://seed-network-v2.vercel.app/ seed