Skip to content
OPC-Fellows中文

v0.7.3 · macOS Apple Silicon

OPC-Fellows

A local-first workbench for a one-person company — kernel plus occupation plugins.

OPC-Fellows

What it is

Keep the todos, projects, skills, and sessions of a one-person company in one local window.

One window for the work

Todos, projects, skills, and sessions live together, so you are not hopping across a pile of tools.

Occupation plugins on demand

Turn notes, mail triage, growth experiments, and other occupation modules on only when the work needs them.

Data stays on the machine

Business data lives in local userData. There is no first-party backend holding it for you.

Download

Only macOS (Apple Silicon) builds are available. Windows and Linux are not available yet.

macOS (Apple Silicon)Available
WindowsNot available yet
LinuxNot available yet

You must allow it on first launch

This build is not Apple-signed or notarized. macOS will block the first open until you run the command below, then launch the app.

Terminal
xattr -cr "/Applications/OPC Agent Team - Solokit.app"

About the app display name After install, Dock and Applications still show “OPC Agent Team - Solokit”. Renaming it would migrate the data directory, so that waits for a later release.

latest-mac.ymllatest-mac.yml is this release’s macOS update manifest.

How it works

The Cordis kernel owns the session and permissions. Occupation modules plug in through a contract and cannot call past it.

CordisKernelModule AModule BModule CModule Dcapabilitycapabilitycapabilitycapability
  1. 01

    A module declares the capabilities it needs in its manifest.

  2. 02

    Calls outside that grant are rejected by the kernel.

  3. 03

    High-risk permissions are confirmed when the module is installed.

Built-in occupations

This is the real module list from the project README — nothing added or removed.

Notes

Local notes

Companion

Standalone reminder window; due todos jump to screen center

Project monitor

Repo / site posture; optional GET /api/stats

Social ammo

Multi-platform copy from product capabilities

Micro sourcing

Public-forum pain points clustered into product ideas

Growth hacker

Experiments, loops, and channels; no copy, no traffic refresh

Creator accounts

Domestic-platform accounts and day logs (manual data)

WeChat intel

Local read-only bridge to WeChat Intelligence Hub; never sends WeChat, chats stay on device

Mail triage

Local Mail.app + iCloud / Gmail / QQ IMAP; triage and drafts only, no sending

Payments

Local ledger; optional Creem sync

DeepSeek Harness

Center-pane chat and Local API share one SDK session

Security & data

Permissions follow a capability allowlist. Chats, mail, and secrets stay on this machine by default.

01

No first-party backend

Business data stays in local userData. There is no first-party backend.

02

WeChat stays on device

WeChat intel is a local read-only index: chats are not uploaded, secrets never leave the machine, and the app never sends WeChat messages.

03

Mail is not sent

Mail only reads the inbox and writes local drafts. The app does not send mail.

04

High-risk grants need confirmation

Third-party modules go through a capability allowlist. High-risk permissions are confirmed at install time.

FAQ

Why macOS only?+

The published installer is macOS (Apple Silicon) only. Windows and Linux are not available yet.

It will not open after install. What now?+

The build is not Apple-signed or notarized, so the system blocks the first launch. Run xattr -cr "/Applications/OPC Agent Team - Solokit.app" in Terminal, then open the app.

Where is the data stored?+

Business data stays in local userData. There is no first-party backend. WeChat chats and secrets do not leave this machine; mail drafts are local too.

Can I use it commercially?+

Yes. The project is MIT-licensed, which allows commercial use. The LICENSE file in the repo is the source of truth.

How do I write my own module?+

See CONTRIBUTING in the public repo. Modules declare capabilities in a manifest; the kernel rejects out-of-grant calls; high-risk permissions are confirmed at install time. Read CONTRIBUTING