Penglai 0.6.6

A real assistant, without turning your computer into a project.

Install Penglai, bring the model key you already use, and begin in a Workspace you choose. Memory and messaging integration are installed; channels stay inert until connected, while local voice remains opt-in.

Apple Silicon Windows x64 UOS 20 LoongArch MIT

Penglai first-run welcome: language, appearance, and a seven-step guide
Installed 0.5.5 first-run welcome, kept as a UI reference. This is not a 0.6.6 screenshot.

One official package manager

The exact DSH alpha.2 manager owns mutable profile packages. Penglai supplies its own pinned Node and pnpm; package installation and build-script approval stay separate trust actions.

Let one project remember

Project memory stays in the current Workspace. Personal memory is a separate choice you confirm. Storage stays on this computer.

Keep the conversation close

Weixin, Feishu, and six other channels can join the same official Session. Optional macOS iMessage is private text and default off. WhatsApp is not a product surface.

Add a voice later

Speech recognition and voice generation stay off until you download their models. Ordinary chat still works without them.

One trusted center

One core. No hidden second agent.

Official DeepSeek Harness is the only agent core. It owns models, tools, approvals, Workspace, Session, Turn, and the conversation interface. Penglai owns the installer, first-run, process supervision, updates, uninstall, local paths, and a reviewed plugin set. There is no second Penglai agent and no replacement chat page. Fresh setup lists official deepseek-flash (DeepSeek-V41-Flash) with text and image input. A model you already chose stays in official settings.

Penglai 0.6.6 · DSH 0.1.7-alpha.2 · tag dsh-v0.1.7-alpha.2 · commit 00102833dfaee1da9f48a3a8eae9d34005a75218 · 323 packages

Penglai Plugin Center inside official DSH settings, showing historical Memory, messaging, and voice surfaces
Installed 0.5.5 Plugin Center, running in official DSH settings. UI state is never proof that a plugin is installed or healthy. Not a 0.6.6 screenshot.

Official DSH package management

One manager, one profile, one source of truth.

Penglai Center owns one exact official DSH alpha.2 plugin-manager instance. It exposes the official package UI and tool while binding package operations to application-owned Node 22.23.2 and pnpm 11.11.0. Installing a package does not silently approve its build scripts.

  • Official DSH inventory remains the live activation authority.
  • Memory, IM, ASR and TTS remain app-owned first-party integrations.
  • Office/PDF and LibreOffice are excluded. Budget and Companion are bundled but off by default.
Historical Penglai Plugin Center UI inside official DSH settings

Penglai Memory · on by default

Let this project remember, and only this project.

Project memory stays in the current Workspace. Another Workspace does not see it. Personal memory is a separate choice you confirm. Memory uses your selected model provider to decide which project facts to keep. Storage stays on this computer.

  • You can turn memory off without deleting its package or data, or review candidates first.
  • Authorised folders are indexed without changing the originals.
  • Memory starts on, with the Mnemon 0.2.8 engine packed.
Penglai Memory settings: Workspace scope, graph, correction, and migration

A calm default

More when you want it. Quiet when you do not.

Enabled · unconfigured

Messaging

Weixin, Feishu, DingTalk, WeCom, QQ, Slack, Telegram, and Discord enter one @penglai/im control plane, using each platform's QR, device-registration, or official-token flow. WeChat and Feishu can send files into the bound conversation. If that conversation is missing, the channel keeps a durable error with /projects and /new. Optional macOS iMessage is private text, default off, and needs Full Disk Access plus Messages automation. It is unsupported on Windows and UOS. Native live use is not claimed (LIVE_NOT_RUN). WhatsApp is not bundled.

Opt in

Local voice

SenseVoice handles speech recognition. MOSS-TTS handles voice generation on Mac and Windows. Plugin code ships in the app. Large SenseVoice weights explain themselves before downloading. MOSS-TTS is not available and not enableable on LoongArch. Conversation Read speaks the original reply rather than translating it.

Opt in

Budget and Companion

Both integrations ship disabled. Budget views and proactive actions remain bounded by Workspace, permissions, and the official Session; review their scope before enabling them.

Official manager

Plugin Center

The exact official DSH alpha.2 manager is the sole mutable package backend. Penglai does not impose the historical signed catalog as an ecosystem allowlist. Review package identity and permissions, and approve build scripts only when you trust them.

First launch

No scavenger hunt. Seven clear steps.

Choose language and appearance, read the local-data boundary, pick a provider and model from the official catalog, test your own API key, choose a real Workspace, then send the first message. Fresh setup includes official deepseek-flash. Folder browse stays in the Penglai window; you can cancel or retry. You can go back and resume after restart. A failed API key is never recorded as success. The app data directory and the install directory cannot be Workspaces.

  • Use the matching installer. Do not mix Apple Silicon, Windows, or UOS packages.
  • Fresh install, restart, and default uninstall passed. Installed upgrades from 0.6.3 and 0.6.5 to 0.6.6 preserved owner data.
  • Default uninstall keeps user data. External Workspaces and the Penglai/0.5 generation remain.
Penglai first-run privacy step, explaining local YAML credentials and what is not logged

Nothing hidden in the small print

Clear about what stays here, and what leaves.

Your work stays yours App data is stored locally by default. There is no Penglai account, cloud memory sync, or Penglai telemetry service. Model calls send task context to the provider you choose; connected messaging channels exchange content through their platforms.

Nothing leaves by surprise Plugin installation and build-script approval are separate trust actions. Once you connect a model or messaging channel, it processes tasks and messages under your settings; review permissions and recipients before enabling them.

A community release The code and release bytes are open to inspection. macOS and Windows may still show a security warning because this community build does not carry Apple notarization or Microsoft Authenticode.

One complete UOS installer The LoongArch .deb carries the app, Node, official DSH, the official package manager, Memory, IM, ASR, TTS, Budget, Companion, and Mnemon. It is designed for the same seven-step start; the Owner will verify that experience on a real UOS machine after publication.

Technical release boundaries

Official DSH includes a dormant DeepSeek OTLP endpoint; Penglai hard-disables it. Diagnostics must not contain credentials, chat bodies, QR codes, or private absolute paths. Penglai Ed25519 signatures bind updater and plugin bytes, but are not OS publisher identity. Mac and Windows embed Node 22.23.2 and Electron 43.6.0. UOS uses Loongson Node 22.16.0 and Electron 31.7.7 (Chromium 126), requires libatomic1, recommends bubblewrap, and cannot enable MOSS-TTS or iMessage. That Electron/Chromium runtime is unmaintained. UOS native install, startup, UI, file picker, sleep/resume, and function remain OWNER_POST_RELEASE. Default Defender-on Windows was not verified. This page does not claim a three-target native GUI PASS.

Penglai 0.6.6

Pick your machine. Start there.

The immutable GitHub Release is the authoritative public download source: v0.6.6. All three installers come from source 519a24be3702257bc7b0e0230d19fe3affd0a31b. Check the file against SHA256SUMS on that page. The release is three installers and ten assets. The signed updater covers Apple Silicon and Windows x64. Intel Mac is not a 0.6.6 installer. Linux amd64 and Windows ARM are not targets. Updates are never silent. Published 0.5.10, 0.5.11, 0.5.12, 0.6.0, 0.6.1, 0.6.2, 0.6.3, and 0.6.5 remain immutable. Installed upgrades from 0.6.3 and 0.6.5 to 0.6.6 preserved owner data.

Why Penglai

I spent more than ten years around networking, security, and operations, but I was not a software developer. Penglai began with one stubborn idea: ordinary people should be able to reach a real assistant from the computer they already have.

Computers travelled from command lines to windows and then into everyone's pocket. Agents should make the same trip. If I can send a message, I should be able to reach my own assistant. If it acts for me, I should be able to see what it was allowed to do, what actually happened, and what it cost.

Penglai has been rebuilt more than once. The important decision in 0.5 was to stop building another agent and stand on DeepSeek Harness instead. 0.6.6 keeps that decision, updates the exact official DSH cohort, and adapts the non-Office first-party plugins across three release targets, including UnionTech UOS 20 LoongArch. Older generations remain in Git history; their runtimes are not mixed into this core.

Kevin Chen / 陈克文

FAQ

The useful answers, before you install.

Is Penglai another agent?

No. Official DeepSeek Harness is the only core. Penglai owns install, lifecycle, and first-party plugins. There is no second chat page.

Which version should I download?

This page describes Penglai 0.6.6. Download the matching installer from the immutable v0.6.6 GitHub Release. Intel Mac is not a 0.6.6 installer. Published 0.5.10, 0.5.11, 0.5.12, 0.6.0, 0.6.1, 0.6.2, 0.6.3, and 0.6.5 remain historical and immutable.

Why does Gatekeeper warn?

macOS packages are ad-hoc signed and not notarized; Windows has no Authenticode. That is a stated limitation, not an OS endorsement. Do not turn off system security to install.

What starts on a fresh profile?

Memory and Mobile Messaging are installed and active, while messaging channels and accounts remain unconfigured. ASR and MOSS-TTS stay off. ASR, MOSS-TTS, Budget, and Companion are bundled but off by default. Office/PDF and LibreOffice are excluded.

Does Penglai support iMessage?

Only as optional macOS private text, default off. Grant Full Disk Access and Messages automation first, then enable and bind the exact peer. It is unsupported on Windows and UOS. Native live use is not claimed.

What if the API key fails?

The wizard supports Back, retry, and resume after restart. A failed credential test is never recorded as success.

Does uninstall delete my files?

Default uninstall removes the application and cache while preserving user data. Complete delete uses a separate category plan and must not recursively wipe a Workspace or home directory.

Product contract Architecture Plugin Center 0.6.6 acceptance delta