Add Parallel

Add Parallel AI Integration

Legacy MCP-based integration notes for Parallel AI. The Codex version of NanoClaw uses IPC actions instead of MCP.

Note: Sections referencing mcp__* are legacy. Port by defining IPC actions + host-side API calls instead.

What This Adds

• Quick Search - Fast web lookups using Parallel Search API (free to use)
• Deep Research - Comprehensive analysis using Parallel Task API (asks permission)
• Non-blocking Design - Uses NanoClaw scheduler for result polling (no container blocking)

Prerequisites

User must have:

1. Parallel AI API key from https://platform.parallel.ai
2. NanoClaw already set up and running
3. Container system working (Apple Container or Docker)

Implementation Steps

Run all steps automatically. Only pause for user input when explicitly needed.

1. Get Parallel AI API Key

Ask the user:

Do you have a Parallel AI API key, or should I help you get one?

If they have one: Ask them to provide it.

If they need one: Tell them:

1. Go to https://platform.parallel.ai
2. Sign up or log in
3. Navigate to API Keys section
4. Create a new API key
5. Copy the key and paste it here

Wait for the API key.

2. Add API Key to Environment

Add PARALLEL_API_KEY to .env:

# Check if .env exists, create if not
if [ ! -f .env ]; then
    touch .env
fi

# Add PARALLEL_API_KEY if not already present
if ! grep -q "PARALLEL_API_KEY=" .env; then
    echo "PARALLEL_API_KEY=${API_KEY_FROM_USER}" >> .env
    echo "✓ Added PARALLEL_API_KEY to .env"
else
    # Update existing key
    sed -i.bak "s/^PARALLEL_API_KEY=.*/PARALLEL_API_KEY=${API_KEY_FROM_USER}/" .env
    echo "✓ Updated PARALLEL_API_KEY in .env"
fi

Verify:

grep "PARALLEL_API_KEY" .env | head -c 50

3. Update Container Runner

Add PARALLEL_API_KEY to allowed environment variables in src/container-runner.ts:

Find the line:

const allowedVars = ['CODEX_API_KEY'];

Replace with:

const allowedVars = ['CODEX_API_KEY', 'PARALLEL_API_KEY'];

4. Add Host-Side Integration (IPC Actions)

Codex does not use MCP in NanoClaw. Expose Parallel AI via IPC actions:

1. Add new actions to container/agent-runner/response-schema.json (e.g., parallel_search, parallel_task).
2. Handle those actions in container/agent-runner/src/index.ts (write IPC files for the host).
3. Implement the API calls on the host (new module + IPC processing in src/index.ts).
4. Ensure results are sent back via send_message.

5. Add Usage Instructions to MEMORY.md

Add Parallel AI usage instructions to groups/main/MEMORY.md:

Find the "## What You Can Do" section and add after the existing bullet points:

- Use Parallel AI for web research and deep learning tasks

Then add a new section after "## What You Can Do":

## Web Research Tools

You have access to two Parallel AI research tools:

### Quick Web Search (`mcp__parallel-search__search`)
**When to use:** Freely use for factual lookups, current events, definitions, recent information, or verifying facts.

**Examples:**
- "Who invented the transistor?"
- "What's the latest news about quantum computing?"
- "When was the UN founded?"
- "What are the top programming languages in 2026?"

**Speed:** Fast (2-5 seconds)
**Cost:** Low
**Permission:** Not needed - use whenever it helps answer the question

### Deep Research (`mcp__parallel-task__create_task_run`)
**When to use:** Comprehensive analysis, learning about complex topics, comparing concepts, historical overviews, or structured research.

**Examples:**
- "Explain the development of quantum mechanics from 1900-1930"
- "Compare the literary styles of Hemingway and Faulkner"
- "Research the evolution of jazz from bebop to fusion"
- "Analyze the causes of the French Revolution"

**Speed:** Slower (1-20 minutes depending on depth)
**Cost:** Higher (varies by processor tier)
**Permission:** ALWAYS ask the user first before using this tool

**How to ask permission:**

I can do deep research on [topic] using Parallel's Task API. This will take 2-5 minutes and provide comprehensive analysis with citations. Should I proceed?

**After permission - DO NOT BLOCK! Use scheduler instead:**

1. Create the task using `mcp__parallel-task__create_task_run`
2. Get the `run_id` from the response
3. Create a polling scheduled task using `mcp__nanoclaw__schedule_task`:

Prompt: "Check Parallel AI task run [run_id] and send results when ready.

1. Use the Parallel Task MCP to check the task status
2. If status is 'completed', extract the results
3. Send results to user with mcp__nanoclaw__send_message
4. Use mcp__nanoclaw__complete_scheduled_task to mark this task as done

If status is still 'running' or 'pending', do nothing (task will run again in 30s). If status is 'failed', send error message and complete the task."

Schedule: interval every 30 seconds Context mode: isolated

4. Send acknowledgment with tracking link
5. Exit immediately - scheduler handles the rest

### Choosing Between Them

**Use Search when:**
- Question needs a quick fact or recent information
- Simple definition or clarification
- Verifying specific details
- Current events or news

**Use Deep Research (with permission) when:**
- User wants to learn about a complex topic
- Question requires analysis or comparison
- Historical context or evolution of concepts
- Structured, comprehensive understanding needed
- User explicitly asks to "research" or "explain in depth"

**Default behavior:** Prefer search for most questions. Only suggest deep research when the topic genuinely requires comprehensive analysis.

6. Rebuild Container

Build the container with updated agent runner:

./container/build.sh

The build script will automatically:

• Try Apple Container first
• Fall back to Docker if Rosetta is required
• Import to Apple Container

Verify the build:

echo '{}' | container run -i --entrypoint /bin/echo nanoclaw-agent:latest "Container OK"

7. Restart Service

Rebuild the main app and restart:

npm run build
launchctl kickstart -k gui/$(id -u)/com.nanoclaw

Wait 3 seconds for service to start, then verify:

sleep 3
launchctl list | grep nanoclaw

8. Test Integration

Tell the user to test:

Send a message to your assistant: @[YourAssistantName] what's the latest news about AI?

The assistant should use Parallel Search API to find current information.

Then try: @[YourAssistantName] can you research the history of artificial intelligence?

The assistant should ask for permission before using the Task API.

Check logs to verify MCP servers loaded:

tail -20 logs/nanoclaw.log

Look for: Parallel AI MCP servers configured

Troubleshooting

Container hangs or times out:

• Check that type: 'http' is specified in MCP server config
• Verify API key is correct in .env
• Check container logs: cat groups/main/logs/container-*.log | tail -50

MCP servers not loading:

• Ensure PARALLEL_API_KEY is in .env
• Verify container-runner.ts includes PARALLEL_API_KEY in allowedVars
• Check agent-runner logs for "Parallel AI MCP servers configured" message

Task polling not working:

• Verify scheduled task was created: sqlite3 store/messages.db "SELECT * FROM scheduled_tasks"
• Check task runs: tail -f logs/nanoclaw.log | grep "scheduled task"
• Ensure task prompt includes proper Parallel MCP tool names

Uninstalling

To remove Parallel AI integration:

1. Remove from .env: sed -i.bak '/PARALLEL_API_KEY/d' .env
2. Revert changes to container-runner.ts and agent-runner/src/index.ts
3. Remove Web Research Tools section from groups/main/MEMORY.md
4. Rebuild: ./container/build.sh && npm run build
5. Restart: launchctl kickstart -k gui/$(id -u)/com.nanoclaw

Converted and distributed by TomeVault — claim your Tome and manage your conversions.