local-upgrade

Automate pulling, rebuilding, and deploying the codex-remote daemon from the repository checkout.

289|39|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/kxn/codex-remote-feishu --skill local-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-upgrade
Source: https://github.com/kxn/codex-remote-feishu/tree/main/.codex/skills/local-upgrade
Command: npx skills add https://github.com/kxn/codex-remote-feishu --skill local-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates updating the locally installed codex-remote daemon by pulling the latest repo, rebuilding, and applying the new binary to the fixed local artifact path.

Core Features & Use Cases

  • Automates repo-bound upgrade workflow: git pull, rebuild, copy new binary, and run the local-upgrade transaction.
  • Handles variations like different base dirs and slot labels, enabling targeted upgrades in multi-install setups.
  • Distinguishes repository tasks from daemon slash-commands and provides guidance for status/debug checks.

Quick Start

From the repository root, run upgrade-local.sh to pull, rebuild, and activate the latest daemon.

Frequently Asked Questions about local-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade a locally installed daemon from a git repository checkout?

To upgrade a locally installed daemon, you run the upgrade-local.sh script from the repository root to pull the latest code, rebuild the binary, and deploy it to the fixed local artifact path.

What is the best way to pull and rebuild a local daemon without interrupting running processes?

The local upgrade process validates the local install state and protects running processes while it pulls the latest repository code and applies the newly rebuilt daemon binary.

Can I target specific upgrades in a multi-install setup with different base directories?

Yes, the local upgrade workflow handles variations like different base directories and slot labels, enabling targeted daemon upgrades across multi-install setups.

Do I need the upgrade-local.sh script to rebuild and deploy the local daemon?

Yes, you need access to the repository, the upgrade-local.sh script, and the fixed local artifact path to pull, rebuild, and activate the updated local daemon.

How do I check the status of a repository-bound daemon after a local upgrade?

The local upgrade workflow distinguishes repository tasks from daemon slash-commands and provides specific guidance for status and debug checks after the daemon update.

What does the local-upgrade transaction do when deploying the updated daemon?

The local-upgrade transaction automates the repository-bound workflow by pulling the latest code, rebuilding the binary, copying it to the fixed local artifact path, and activating the daemon.