IVICP — InvoiceVault App Interaction

If the ping fails, the HTTP bridge hasn't been added to the app yet. You need to add it:

1. Read the bridge module at ~/.claude/skills/ivicp/scripts/ipc-bridge.ts
2. Copy it into the IVICP project at src/main/ipc-bridge.ts
3. In src/main.ts, after overlayWindow.registerIpcHandlers() (around line 172), add:

   import { startIpcBridge } from './main/ipc-bridge';
   // ... after registerIpcHandlers()
   startIpcBridge(overlayWindow);
   

4. Restart the app with pnpm start

After setup, verify with curl -s http://127.0.0.1:19847/ping.

3. Call IPC commands

Every IPC channel is available as POST /ipc/<channel> with a JSON body containing an args array.

# Search for invoices
curl -s http://127.0.0.1:19847/ipc/search -X POST -H 'Content-Type: application/json' -d '{"args":["query text"]}'

# Get line items for a record
curl -s http://127.0.0.1:19847/ipc/get-line-items -X POST -H 'Content-Type: application/json' -d '{"args":["record-id-here"]}'

# Reprocess all files
curl -s http://127.0.0.1:19847/ipc/reprocess-all -X POST -H 'Content-Type: application/json' -d '{"args":[]}'

# Get app config
curl -s http://127.0.0.1:19847/ipc/get-app-config -X POST -H 'Content-Type: application/json' -d '{"args":[]}'

Available IPC Channels

Rather than maintaining a static list here, discover available channels dynamically:

1. List all channels: curl -s http://127.0.0.1:19847/ping — returns all registered channel names
2. Read the source: The IPC handlers are registered in src/main/overlay-window.ts in the registerIpcHandlers() method. Read this file to understand parameter types and return values.
3. Read the types: The InvoiceVaultAPI interface in src/shared/types/index.ts defines the full typed API.

Channel Quick Reference

Key Types

SearchFilters: { text?, folder?, docType?, status?, amountMin?, amountMax?, dateFilter? }

FieldOverrideInput: { recordId, tableName, fieldName, userValue }

LineItemFieldInput: { lineItemId, fieldName, userValue }

Workflow Patterns

Search and inspect an invoice

# Search
curl -s http://127.0.0.1:19847/ipc/search -X POST -H 'Content-Type: application/json' -d '{"args":["company name"]}'

# Get line items from a result
curl -s http://127.0.0.1:19847/ipc/get-line-items -X POST -H 'Content-Type: application/json' -d '{"args":["<record_id>"]}'

Reprocess a folder after changes

curl -s http://127.0.0.1:19847/ipc/reprocess-folder -X POST -H 'Content-Type: application/json' -d '{"args":["2024/Q1"]}'

Get aggregate stats with filters

curl -s http://127.0.0.1:19847/ipc/get-aggregates -X POST -H 'Content-Type: application/json' -d '{"args":[{"folder":"2024","docType":"invoice_in"}]}'

Dynamic Discovery

When the user asks for something you're not sure maps to a specific channel:

1. Read src/main/overlay-window.ts to find the handler implementation
2. Read src/shared/types/index.ts for type definitions
3. Check src/core/db/records.ts for database query functions

This lets you construct the right HTTP call for any operation, even ones added after this skill was written.

Error Handling

The bridge returns:

• 200 with JSON body on success
• 404 if the channel doesn't exist
• 500 with {"error": "message"} on handler failure
• Connection refused if the app isn't running

If the bridge is unreachable, remind the user to start the IVICP app (pnpm start from the project directory).