SkillsAdd

smithery/tankygranny05

codex-app-server-persisted

This skill should be used when building a low-latency, long-lived Codex controller using `codex app-server` (JSON-RPC over stdio) to keep one PID alive across turns while preserving `sse_lines.jsonl` observability.

Installation

$ npx skills add smithery/tankygranny05 --skill codex-app-server-persisted
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from smithery/tankygranny05 · top by installs.

npx skills add smithery/tankygranny05
tmux-enter-key-handling 0 soto-config 0 repl-friendly-import-patching 0 ram-consumption-verification 0 investigation-codex-vscode-extension 0 fine-grained-tool-streaming 0 document-skills:xlsx 0 debug-session-documenter 0 compute-token-stats-rust-ultra 0 claude-usage-meter 0

Browse all from smithery/tankygranny05

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents codex

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,834 B
  • docs SUMMARY.md 248 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Codex App Server Persisted

[Created by Codex: 019b74f5-a7d5-7121-ac48-8e66cd2bdc92]

Purpose

Provide a repeatable workflow to keep a single Codex process running in memory via codex app-server, and drive multi-turn interactions by sending thread/start once and turn/start repeatedly on the same threadId.

When To Use

  • Need a warm, long-lived Codex PID to minimize turn-to-turn latency
  • Need programmatic control over turns (JSON-RPC over stdio) instead of a TUI
  • Need built-in observability via sse_lines.jsonl (works with app-server, not with mcp-server)

Workflow

1) Confirm requirements

  • Identify whether the goal is: single-controller (one process drives Codex) or multi-client daemon/broker.
  • Identify whether approvals must be supported or bypassed (risk/permissions).
  • Identify desired observability target: centralized ~/centralized-logs/codex/sse_lines.jsonl or isolated --log-dir.

2) Start a long-lived app-server process

  • Spawn codex app-server as a subprocess with stdin=PIPE and keep stdin open for the lifetime of the controller.
  • Read stdout line-by-line and parse each line as JSON (JSON-RPC-like).
  • Treat stderr as inherited or actively drained to avoid deadlocks.

3) Create a thread once, then reuse it

  • Send initialize.
  • Send thread/start and store threadId.
  • For each user prompt, send turn/start with the same threadId.

4) Stream events and detect completion

  • Expect notifications interleaved with responses on stdout.
  • Print/collect assistant output using codex/event/agentmessagecontent_delta.
  • Consider a turn complete when either:

- notification method codex/event/task_complete arrives, or - notification method turn/completed arrives.

5) Handle approvals if enabled

  • Detect server→client JSON-RPC requests (messages that include both method and id but no result).
  • For V2 approval requests, handle at least:

- item/commandExecution/requestApproval - item/fileChange/requestApproval

  • Reply with a JSON-RPC response { "id": <same>, "result": { "decision": "accept" | "decline" } }.

6) Validate observability logging

  • Prefer to run codex with --log-dir when isolation is needed (creates sse_lines.jsonl under that directory).
  • Otherwise, verify the centralized ~/centralized-logs/codex/sse_lines.jsonl changes while the app-server PID stays alive.

Bundled Resources

  • Reference guide: references/codex-app-server-persisted-process.md
  • Starter script: scripts/appserverpersisted_repl.py