Skip to content

CoreMan v0.2.0

Latest

Choose a tag to compare

@github-actions github-actions released this 19 Sep 06:07
· 25 commits to main since this release
0eb4be6

CoreMan 0.2.0:扫码即可创建飞书、企业微信机器人;成员可以在私聊里接入自己的飞书或企业微信资料,并直接在聊天里让 AI 员工创建定时任务。README 也围绕第一次使用的人重写了。

CoreMan 0.2.0: create Feishu and WeCom bots by scanning a QR code, let members connect their own Feishu or WeCom data in private chats, and have AI employees set up scheduled tasks from a chat message. The README has been rewritten for first-time users.

Highlights

  • Scan to create bots: when you create an AI employee, scan with Feishu or WeCom and the bot is created and linked for you, with no developer-console setup. The form asks only for an identifier, a name and a runtime. Secrets stay on the server, and WeCom credentials are verified before they are saved.
  • Personal tools in private chats: members send "连接飞书" (Connect Feishu) or "连接企业微信" (Connect WeCom), pick a tier, and the assistant can read (and, at higher tiers, act on) their own messages, meetings, documents, calendar, mail and more. The tools are added on top of the ordinary assistant, never used in group chats, and only the member can view those conversations. WeCom members bind their own authorization bot once on the new "My WeCom" page.
  • Scheduled tasks from chat: "每个工作日 9 点总结我的飞书未读消息" drafts a task that the member confirms on a card. "My scheduled tasks" lists, pauses and deletes them.
  • Feishu app management from the employee page: permissions and approval status, scan to add missing permissions, menus, availability, slash commands (/new, /stop, /sessions, /connect, /help) and releases.
  • Runtime operations: a stable ~/.local/share/coreman-runtime/bin/coreman-runtime command for upgrade, uninstall and re-registration; curl … | sh -s -- --replace to reinstall safely; change a node's team or delete a node from the console; skill installs no longer need the Git host allowlist.
  • Skills: enable, disable or delete skills from the catalog, and see why an installation failed.
  • Security: a per-turn tag on the speaker identity line, credential redaction before model output reaches chat or logs, session history without environment variables, MASTER_KEY rotation without downtime, and business system tokens issued only for users with a unique email prefix.
  • Smaller releases: code-only releases add about 8 MB per image instead of rewriting a 300 MB layer.

See CHANGELOG.md for the full list.

Upgrading from 0.1.0

  1. Build (./deploy/coreman build --tag v0.2.0 on the tag) or pull the images below and retag them, then run ./deploy/coreman upgrade all v0.2.0. It applies database migrations 0029 to 0041.
  2. Upgrade each runtime node with coreman-runtime --upgrade <bundle> (see the runtime README). Older nodes keep answering chat but lack the personal tools, owners viewing their own sessions, session history without environment variables and the newer skill and workspace fixes.
  3. Users without an email, or whose email prefix another account shares, no longer receive business system tokens. Sync contacts with contact:user.email:readonly (Feishu) so members have emails.

Get started

Follow the README quick start (中文:README). CoreMan does not provide model quota; install and sign in to Claude Code or Codex yourself.

Artifacts

  • Container images (linux/amd64, linux/arm64): ghcr.io/wxkingstar/coreman-api:v0.2.0 and ghcr.io/wxkingstar/coreman-runtime:v0.2.0. deploy/coreman only uses local coreman-api:<tag> / coreman-runtime:<tag> images, so retag after pulling; see docs/operations.md.
  • Runtime Daemon bundles are attached below with .sha256 files and SHA256SUMS. Installing through the admin console's install command is recommended.