Getting started

What is OfficeCubs?

Choose Crew for AI teammates in your desktop office, or Familiar Chat for a configured role that someone else uses through a chat app.

OfficeCubs · · 3 min read

OfficeCubs has two usage scenarios. Crew helps you direct AI teammates in your own desktop office. Familiar Chat lets a developer configure an AI role that someone else can use through WeChat, Feishu / Lark or Telegram.

Crew: build your own AI team

Choose teammates with useful specialties, give them working guides and skills, and configure a supported engine such as Codex or Claude Code. Assign a task with its source files, follow progress, and review the delivered work. You can ask for revisions and pass reviewed output to another teammate yourself.

For example, ask a research teammate to summarize supplied meeting notes, then give the checked summary to a writing teammate for a weekly update. Begin with your first desktop task.

Familiar Chat: help someone through their chat app

The developer selects a work engine, supplies a role’s instructions and resources, and connects the intended person’s private conversation. That person asks questions or assigns tasks in their chat app, without having to configure the AI tools themselves.

Three separate choices

  • Role: the job, working guide, skills and source material. For example, a role that answers questions from approved onboarding notes.
  • Work engine: the supported AI tool that executes the role’s tasks. The developer can configure the teammate to use Codex, Claude Code or DeepSeek Harness.
  • Chat connection: where the intended user sends questions and receives replies. It routes requests to a selected teammate.

The same role can be configured with a different supported engine. Its behavior still depends on the selected tool, model access and available resources.

Who sets up Familiar Chat?

The developer runs OfficeCubs on the host computer, authorizes the AI tool, chooses the workspace and tests the role. The intended user completes the relevant chat pairing or authorization and then writes normal messages. They do not need a command line or their own copy of the work engine to use that configured connection.

Familiar Chat example

A developer prepares a product knowledge role and supplies an approved guide. A colleague asks in Feishu, “What should I do when a shipment is delayed?” The role uses its configured engine to answer from the guide. It should say when the source does not contain an answer rather than inventing a policy.

Check the Familiar Chat setup

Test from the intended user’s conversation, using a question with a known answer and another with no answer in the source. Verify the selected teammate, source references and reply destination. See the complete handoff walkthrough.

Current limits

The host must stay awake and online. The operator handles tool approvals, and connected AI providers may receive task content. Private-chat pairing and file delivery differ by provider; the integrations are not an unrestricted group-chat service. Public signed installers are still listed as coming soon on the download page.

Keep exploring

Practical workflows from the blog