codex-remote-auth

Deploy Codex CLI auth.json to remote machines via scp and SSH.

2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/tankygranny05/agent-box --skill codex-remote-auth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-remote-auth
Source: https://github.com/tankygranny05/agent-box/tree/main/agent-box/seed/codex-skills/codex-remote-auth
Command: npx skills add https://github.com/tankygranny05/agent-box --skill codex-remote-auth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the secure deployment of Codex CLI authentication credentials to remote machines, enabling seamless command-line access and execution without manual credential transfer.

Core Features & Use Cases

  • Secure Credential Transfer: Uses scp to copy the auth.json file to the remote machine's ~/.codex/ directory.
  • Remote Command Execution: Verifies the deployment by executing a simple command via SSH on the remote machine.
  • Customizable SSH: Supports specifying custom SSH ports and user credentials.
  • Use Case: You need to run Codex CLI commands on a staging server to test a new feature. This Skill ensures your local Codex authentication is securely mirrored on the staging server, allowing you to run commands remotely.

Quick Start

Copy your local Codex authentication file to the remote host 'your_remote_host' using SSH port 22222.

Frequently Asked Questions about codex-remote-auth

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

FAQPage Schema
How do I deploy Codex CLI authentication credentials to a remote server?

To deploy Codex CLI authentication, use secure copy to transfer the `auth.json` file to the remote machine's `~/.codex/` directory. This automates credential mirroring, enabling non-interactive remote command execution via SSH.

Can I use a custom SSH port when copying Codex credentials to a remote machine?

Yes, you can specify a custom SSH port when transferring Codex credentials to a remote machine. This ensures secure, non-interactive authentication for remote CLI operations on servers using non-standard SSH configurations.

What is the best way to verify remote Codex CLI authentication after transferring the file?

The best way to verify remote Codex CLI authentication is by executing a simple command via SSH on the target system. This confirms the deployed `auth.json` file is functional and the remote CLI operations are working correctly.

Does copying the auth.json file via SCP allow non-interactive Codex commands on staging servers?

Yes, copying the `auth.json` file via SCP allows non-interactive Codex commands on staging servers. It securely mirrors your local Codex authentication to the remote machine, enabling seamless command-line access without manual credential entry.

Why do I need to copy auth.json for remote CLI operations instead of logging in manually?

You need to copy `auth.json` for remote CLI operations to ensure secure, non-interactive authentication. Manually logging in breaks automation, whereas deploying credentials allows seamless remote execution and testing on staging servers.