piskie
GitHubDownload

Open-source desktop AI agent

Command real browsers.Turn every task into capability.

Isolated fingerprints and persistent sessions give every account its own identity. Verified web workflows become Browser Skills, ready to call on demand.

Download PiskieStar on GitHub
Environment
Operations
Seed
0x3F9A21
Timezone
Asia/Hong_Kong
WebRTC
Locked

MIT license · macOS (Apple silicon), Windows, Linux

  1. 01Ask

    One sentence is enough. Pick a model, a workspace, and whether it asks before each step.

  2. 02Choose

    Each environment is a separate identity with its own logins. Piskie reads what each one is for.

  3. 03Local

    It reads the code, edits the file, and runs the tests, showing every step.

  4. 04Browser

    Signed in as Operations, it clicks through the admin like a person would. You can watch live and take over.

How a skill gets made

  1. Scout

    A scout agent maps the site’s pages, forms, and risks, within ten minutes.

  2. Plan

    You approve the list of tools and the test scenarios before any code is written.

  3. Build

    A builder writes each function against the live site and calls it for real. Logins and CAPTCHAs come to you.

  4. Verify

    A separate verifier tests every function in a fresh context. Only a full pass is published.

Skills compile in a sandbox: no network calls of their own, no eval, no file system. Only the browser API Piskie gives them.

Chat and schedules

Connect Feishu, WeCom, QQ, or a personal WeChat account. Piskie replies in the same chat with results and screenshots. New senders pair with a one-time code first.

  • Feishu
  • WeCom
  • QQ
  • WeChat

Browser environments

Fingerprints from the kernel

Canvas, WebGL, and hardware signals come from a fingerprint build of Chromium. Nothing is injected into pages.

Same identity every restart

Each environment keeps its fingerprint and cookies, so sites see the same device each time.

A proxy per environment

HTTP or SOCKS5 per environment. Timezone, language, and location can follow the proxy’s exit IP.

WebRTC locked down

WebRTC is restricted in every profile, so your real IP stays hidden.

Watch it, take over

See the agent’s browser live inside Piskie and step in with your own mouse and keyboard.

One run per environment

An environment in use is locked, so two runs never fight over one account.

On your machine

Models and tools

Models

Any OpenAI- or Anthropic-compatible API. A signed catalog covers 780+ models from 15 providers.

MCP

Local and remote servers with OAuth. Project servers need your approval to run.

Skills & plugins

Install from a folder, Git, or zip. Reads Claude Code and OpenAI plugin marketplaces.

Images

Your own ComfyUI workflows, plus Gemini, DashScope, OpenRouter, and Baidu.

Under the hood

Cache-preserving compaction

At 85% context, Piskie summarizes with the exact prefix the model already saw, so cached tokens stay cached.

MCP capped at 5% of context

Tool schemas share a fixed budget. The rest load on demand through tool search.

Paused before the first script

Every page, iframe, and worker waits on the DevTools protocol until locale, timezone, and UA are set.

1.4 billion fingerprints

Seeds come from each environment’s ID, aligned to values the kernel reports consistently.

Signed model catalog

Updates are Ed25519-signed and hash-checked, with rollback protection.

Skills that can’t drift

Publishing checks the source still matches the build that passed verification.

FAQ

  1. Is Piskie free?

    Free.

    Piskie is open source under the MIT license. You only pay your model provider for the API usage you choose.

  2. Which models can I use?

    Any compatible API.

    Anything OpenAI- or Anthropic-compatible, such as OpenAI, Anthropic, DeepSeek, Gemini, OpenRouter, Qwen, and Zhipu. Each sub-agent can use a different model.

  3. Do I need to install a browser?

    No.

    On first launch, Piskie downloads and verifies its fingerprint Chromium in the background.

  4. Does it work on Intel Macs?

    Not yet.

    The macOS build is for Apple silicon. Windows and Linux builds are x64.

  5. Where is my data stored?

    On your computer.

    Everything lives in ~/.piskie. Model requests go straight to the provider you configure.

  6. Does it run when the app is closed?

    No.

    Schedules and chat bots run while the app is open. A missed schedule runs once when it’s back.

Open source on GitHub

  • MIT licensed
  • Pull requests welcome
  • Data stays in ~/.piskie
  • Your own model keys, no account
Star on GitHubDownload from Releases

macOS (Apple silicon) · Windows x64 · Linux x64 · Report an issue or open a pull request →