CC Codex Gemini Companion Starter banner
d-wwei d-wwei

CC Codex Gemini Companion Starter

Development community

Description

Single-repository bootstrap framework for Claude Code, Codex, and Gemini with memory, IM bridge, and catalog-guided MCP/skills onboarding.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

CC-Codex-Gemini Companion Starter

Turn Claude Code / Codex / Gemini from capable CLI agents into better long-term personal assistants.

[中文说明](./README.zh-CN.md)

Why This Repository Exists

What many people actually like about OpenClaw is not a single feature. It is the feeling of a long-term assistant:

  • reachable from IM
  • able to remember context
  • able to use tools and move work forward

But if you want to place that kind of system into a real workflow, safety, stability, boundaries, and control quickly matter more than novelty.

This repository is not about cloning OpenClaw. It is about migrating the most valuable parts of that experience onto more mature hosts:

  • Claude Code
  • Codex
  • Gemini

In practice, Claude Code and Codex are usually the main path.

The Three-Part Upgrade

This is not a single prompt and not just a memory patch.

It is a three-part upgrade:

  1. Memory
  2. IM bridge
  3. Tooling layer

1. Memory

Claude Code / Codex / Gemini are strong by default, but still tend to behave like single-session agents.

This starter adds a more durable collaboration layer with:

  • global memory
  • project memory
  • temporary daily context
  • runtime state and resume checkpoints

The design is inspired by OpenClaw-style durable memory, but rebuilt for Claude Code / Codex / Gemini workflows instead of copied directly.

2. IM Bridge

A real assistant should be easy to reach.

This repository integrates IM bridge setup so the host can be reached from real communication surfaces, especially Feishu / Lark style workflows.

The goal is not just “message delivery works”, but a smoother day-to-day assistant experience:

  • easier entry point
  • better session continuity
  • fewer rough edges around attachments, voice, and background runtime
  • isolation across multiple hosts on one machine

Core integration:

With thanks to the upstream open source bridge work:

  • [`op7418