PIPO FOR EVERY OS

Pipo is an always-on workflow engine for your connected computer.

It keeps context over time, watches for the work that repeats, and acts through the tools you already use — while your authority stays in the loop.

Install Pipo ↗See the product ↗

START HERE

Before you deploy Pipo

Pipo is not a tab-bound chatbot. It is a persistent system with a brain, a computer control surface, and workflows that can keep running after you close the window.

01Authority & safetyDefine what Pipo can read, change, send, and block.↗02Cross-platform setupConnect the sidecar, permissions, and workspace you trust.↗03TroubleshootingFind the signal when a workflow needs attention.↗

01 / GET READY

Installation

Install the Pipo daemon on macOS, Windows, and Linux. The daemon keeps the brain online; the connected sidecar gives it carefully-scoped hands and eyes on your computer.

Terminal

# install the Pipo CLI
pipo install

# enroll this computer with your workspace
pipo enroll

# launch the local sidecar
pipo sidecar start

Pipo opens your operating system privacy settings when a workflow needs a protected capability. Grant only what your approved workflows need.

02 / FIRST RUN

Quick start

Install the Pipo runtime.Run the installer for your operating system and sign in to the workspace you want this computer to serve.
Enroll your computer.Name the machine, select its workspace, and confirm the sidecar connection.
Set the boundary.Allow reading first. Require approval for sending, editing, and anything that changes external state.
Ask for a repeat.“After every meeting, draft the follow-up for me to approve.” Pipo turns the outcome into a workflow draft.

03 / MAKE IT YOURS

Configuration

Pipo’s configuration is designed around intent rather than plumbing. Set a goal, connect sources, choose an authority level, and keep the workflow inspectable.

Workspace

The shared context, goals, and workflows Pipo can use.

Desktop sidecar

The local bridge to approved desktop, browser, terminal, file, and screenshot actions.

Authority

The rules that allow, ask, or block each class of action.

Memory

The durable context Pipo can use to make future runs more relevant.

04 / WHERE IT RUNS

Platform support

Pipo is designed around a persistent hosted brain and local sidecars. The dashboard works in any modern browser, while connected sidecars run across macOS, Windows, and Linux.

Hosted brainRuns continuously in Pipo’s managed environment or your approved server.

Desktop sidecarNative companion for macOS, Windows, and Linux. Connects over an authenticated channel.

Browser dashboardWorks on macOS, Windows, Linux, and mobile browsers as the cross-platform control plane.

Other sidecarsLinux and Windows sidecars can be added when your workspace needs another machine.

05 / UNDER THE HOOD

High-level architecture

Pipo has three layers: a hosted brain, a dashboard, and sidecars connected to the machines where work happens.

01Hosted brainGoals · memory · judgement

↕

02DashboardWorkflows · authority · logs

↕

03desktop sidecarApps · browser · terminal

06 / THE BRAIN

Hosted brain

The hosted brain is the always-on layer that keeps Pipo useful after the prompt is gone. It owns the durable context and coordinates judgement with programmed execution.

Context & memory

Conversation history, workspace context, goals, preferences, and approved memory entries.

Workflow engine

Triggers, schedules, deterministic steps, retries, run history, and versioned workflow definitions.

Judgement loop

AI reasoning inside a bounded step, with the inputs and output contract visible to you.

Authority engine

Runtime checks that allow, ask, or block an action before it crosses into an external system.

Realtime transport

Secure connections for dashboard updates, sidecar health, workflow events, and approval prompts.

07 / CONTROL SURFACE

Dashboard

The dashboard is the full control plane for Pipo. It keeps the ambient feel of a desktop utility while giving you a clear place to inspect what happened and what happens next.

HomeWorkflowsMemoryToolsAgentsAuthorityLogsCalendarGoalsTasksWorkspacesUsageSettings

08 / THE REPEAT

Workflows

A workflow has a trigger, programmed steps, AI judgement where it is useful, and approval points where you want to remain the decision-maker.

TRIGGERA meeting ends

PROGRAMMEDRead the notes

AI JUDGEMENTDraft the follow-up

YOUR APPROVALReview before sending

PROGRAMMEDSend through Gmail

Test modeRuns the workflow with external side effects disabled so you can inspect inputs and outputs.

VersionsEvery enabled change is versioned, so you can compare or roll back a workflow definition.

Run historyEach run records its trigger, steps, judgement, approvals, and final outcome.

09 / PRODUCT SURFACE

Core capabilities

Pipo’s product areas are designed to work together. A goal informs a workflow; memory gives it context; authority decides how far it can go.

ConversationStreaming answers with tool use and workspace context.

Persistent memoryCapture durable facts and preferences with a reviewable memory vault.

Browser & desktop controlRead pages, fill fields, and work in approved desktop applications.

VoiceUse voice input and realtime spoken output for hands-free moments.

Goals & accountabilityConnect recurring work to outcomes your team has chosen.

Delegated agentsAsk specialist agents to research or prepare work under your authority rules.

WorkspacesBuild and operate projects from a shared context instead of isolated chats.

Usage & logsUnderstand activity, tokens, workflow runs, and authority events.

10 / YOUR BOUNDARY

Authority & safety

Authority is not a setting you configure once and forget. It is the runtime boundary every workflow encounters before it can make a meaningful change.

ALLOWRead connected sourcesLet context flow into the workflow.

ASKSend an emailPause and show the exact draft first.

BLOCKDelete dataKeep destructive actions unavailable.

11 / CROSS-PLATFORM

Cross-platform setup

Keep the daemon hosted and use your connected computer as a deliberate sidecar. That gives Pipo a persistent brain without turning every app on your laptop into an open door.

Install the Pipo CLI with your package manager or signed installer Enroll this computer to the right workspace Grant the minimum desktop permission only when needed Set approval rules for external actions Run one test workflow end-to-end

12 / CROSS-PLATFORM

Desktop sidecar

The connected sidecar is the local companion that lets Pipo operate on this computer. It authenticates to the hosted brain and exposes only the capabilities you choose.

Desktop automation for approved applications
Browser control for reading pages and filling fields
Terminal access with explicit workspace scope
Filesystem and clipboard access under your rules
Screenshots and awareness capture when enabled

13 / TERMINAL

CLI commands

pipo statusShow daemon, workspace, sidecar, and authority status.

pipo enrollPair this computer with a Pipo workspace.

pipo sidecar startStart the local desktop companion.

pipo workflow testRun a workflow in review mode without external side effects.

pipo logs --followStream recent workflow and authority events.

14 / WHEN SOMETHING FEELS OFF

Troubleshooting

The sidecar is offline +

Open Pipo from your system tray or app launcher, confirm the workspace name, then run pipo sidecar start. If the operating system paused a permission, revisit its privacy and security settings.

A workflow stopped for approval +

That is expected when the next step crosses an Ask boundary. Review the draft in the dashboard and approve it, edit the authority rule, or leave it paused.

Pipo used the wrong context +

Check the workflow’s connected sources and Memory entries. Tighten the input list before raising the workflow’s autonomy.

A run is repeating unexpectedly +

Open the workflow’s run history and inspect the trigger event. Use test mode, add an idempotency guard, or pause the workflow before reconnecting the source.

15 / TRUST

Privacy & data

Pipo’s usefulness depends on context, so every connected source should have a reason to exist. Keep data access narrow, review what is stored, and remove a connection when the workflow no longer needs it.

Connected sourcesOnly sources you explicitly connect are available to the workspace. A workflow receives the inputs declared in its steps.

Desktop captureScreen, clipboard, files, and app activity are off until you grant the relevant system permission and enable the capability.

Memory controlsReview, edit, or delete saved context. Do not store secrets, credentials, or data you would not want in a durable workspace.

Audit trailWorkflow runs and authority decisions are recorded so you can understand what Pipo saw and why it paused.

16 / READ CAREFULLY

Disclaimer & liability

Pipo can act in connected applications and on your connected computer. Review permissions, workflow definitions, generated outputs, and approval prompts before relying on them for business-critical work.

You are responsible for the boundary.

Do not give Pipo unrestricted access to accounts, files, or systems. Start in test mode, use least-privilege permissions, keep destructive actions blocked, and maintain backups for important data.

This documentation describes the intended product model, not legal, security, financial, or operational advice. Your workspace owner and your organization’s policies determine what you may connect and automate.

READY WHEN YOU ARE

Turn one repeat into a system.

Choose your Pipo plan ↗