Run any Skill in Manus with one click

cc-settings-api

Stars93

Forks11

UpdatedJune 27, 2026 at 07:28

Read and write CC Director app settings (screenshots location, gateway connection, any config.json key) by calling a running Director's Control API. Triggers on "/cc-settings-api", "set the gateway", "connect this director to the gateway", "set screenshots location", "configure cc-director settings".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

thefrederiksen

thefrederiksen/devthrottle

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	cc-settings-api
description	Read and write CC Director app settings (screenshots location, gateway connection, any config.json key) by calling a running Director's Control API. Triggers on "/cc-settings-api", "set the gateway", "connect this director to the gateway", "set screenshots location", "configure cc-director settings".

CC Director Settings API Skill

Configure CC Director's config.json programmatically through a running Director's Control API. Writes are round-trip-preserving (only the keys you set change; every other section is kept) and gateway changes apply live - the Director re-registers with the gateway with no app restart.

Use this when the user asks to set the screenshots folder, connect a Director to a central gateway, or change any cc-director setting from the agent side.

How it works

A running Director exposes GET /settings and PUT /settings on a loopback port. The script configure_settings.py discovers the newest live Director from its instance files at <config>/director/instances/*.json (reading ControlEndpoint + checking the Pid is alive) and calls those endpoints.

<config> is %LOCALAPPDATA%\cc-director\config on Windows, ~/.local/share/cc-director/config on macOS/Linux, or $CC_DIRECTOR_ROOT/config if that env var is set.
Auth is OFF by default (single-user trust boundary), so no token is needed. If a Director has auth enabled, pass --director-token or the script reads it from <config>/director/gateway-token.txt.

Commands

Run from the repo root (the script needs no dependencies beyond the standard library):

# Read / write
python .claude/skills/cc-settings-api/configure_settings.py show
python .claude/skills/cc-settings-api/configure_settings.py get screenshots.source_directory
python .claude/skills/cc-settings-api/configure_settings.py set-screenshots "/Users/you/Desktop"
python .claude/skills/cc-settings-api/configure_settings.py set-gateway --url http://GATEWAY-HOST:7878 --advertised http://THIS-HOST:7879
python .claude/skills/cc-settings-api/configure_settings.py set <dotted.key> <value>

# Detect (add --apply to write the detected value straight into config.json)
python .claude/skills/cc-settings-api/configure_settings.py detect-gateway [--apply]
python .claude/skills/cc-settings-api/configure_settings.py detect-public-url [--apply]
python .claude/skills/cc-settings-api/configure_settings.py detect-screenshots [--apply]

# Test a gateway URL's reachability (/healthz)
python .claude/skills/cc-settings-api/configure_settings.py test-gateway --url http://GATEWAY-HOST:7878

The detect/test commands run the SAME logic as the Settings dialog buttons (via POST /settings/detect/{gateway|public-url|screenshots} and POST /settings/test/gateway) - so you never need to open the GUI to view, change, or auto-detect settings from a session. Without --apply, detect commands only report the found value; the agent then decides whether to write it. detect-gateway --apply is the one-shot "find and connect to the gateway".

Connecting a Director to a gateway (the main use case)

To make a Director on ANY network show up on a central gateway, set two things:

--url - the gateway's base URL, reachable from this machine (e.g. http://gw-host:7878).
--advertised - THIS Director's own URL, reachable from the gateway's machine. This is required whenever the gateway runs on a different machine. Without it the Director advertises loopback (127.0.0.1), which the gateway cannot call back to. On a Mac this is mandatory (the Tailscale auto-detection is Windows-only).

Example - connect a Mac Director (control port 7879) to a gateway on gw-host:

python .claude/skills/cc-settings-api/configure_settings.py set-gateway \
  --url http://gw-host:7878 \
  --advertised http://mac-host:7879

After this the Director re-registers immediately. Verify it appears in the gateway's GET /directors, or re-run show to confirm the gateway block on disk.

Notes

Do NOT hand-edit config.json while a Director is running and also use this API - go through the API so the live gateway re-apply happens. (cc-devthrottle settings is the offline path and is also round-trip-preserving.)
If no Director is running, the script fails loudly telling you to start CC Director. It does not silently write the file - starting the Director is the fix.
Output is ASCII-only.

More from this repository

same repository

move-session

thefrederiksen/devthrottle

Relocate a live session to another cc-director slot or Director - approval-gated handover through the GATEWAY, the seed identifies itself as a moved session, the TARGET keeps the source's original name, the source is renamed "[MOVED]" and put on hold so the user can close it. Triggers on "/move-session", "move session", "migrate session", "transfer session".

2026-07-1693

agent-expert

thefrederiksen/devthrottle

INTERNAL reference, NOT shipped with the installer. The in-repo expert on every coding-agent CLI CC Director can run (Claude Code, Codex, Gemini, OpenCode, Grok, Copilot, Cursor, Pi). Knows each agent's command line, config files, context-injection points, lifecycle hooks and events, SDK/API/server mode, transcript format, session semantics, and how CC Director drives it. Triggers on "agent-expert", "agent expert", "how does <agent> inject context", "<agent> hooks", "<agent> events", "<agent> CLI reference", "which agents support X", "agent capability matrix".

2026-07-1593

mission

thefrederiksen/devthrottle

How a mission is RUN in this repository - the Architect, the Manager, the Workers, and the independent Inspector, plus the four standing laws (ask up front then run alone, and NEVER guess - bring the owner in when something is genuinely undecidable; the mission branch holds the work and only the Architect lands it on main; a different agent family inspects before anything reaches main; merged to origin/main is the only done). Read this BEFORE starting or seeding any mission, and before writing any mission brief. Triggers on "/mission", "start a mission", "run a mission", "seed an architect", "write a mission brief", "mission brief", "who merges", "mission roles".

2026-07-1593

dev-throttle

thefrederiksen/devthrottle

DevThrottle - "Mission Control for Claude Code". A desktop app (binary cc-director.exe) that runs and supervises multiple Claude Code sessions and ships cc-* CLI tools on PATH. Agents drive the fleet through the cc-devthrottle command, not by calling the Director over HTTP. Triggers on "/dev-throttle", "/devthrottle", "/cc-director", "what cc tools", "list tools", "available tools", "devthrottle api", "session manager", "mission control".

2026-07-1493

fleet-comms

thefrederiksen/devthrottle

Talk to other DevThrottle sessions across the fleet. Use when you want to list running sessions, rename this session, message another session, ask another session a question and get its answer, or open a new session - from inside a session. Triggers on "/fleet-comms", "message another session", "talk to another session", "ask another session", "rename this session", "rename session", "list sessions", "what sessions are running", "open a session", "spawn a session", "cc-devthrottle", "fleet messaging", "session intercommunication".

2026-07-1493

release-manager

thefrederiksen/devthrottle

Guided run-book for cutting a DevThrottle release - assemble the changes, write the release notes, coordinate the internal docs site, cut the tag, and announce it. Triggers on "/release-manager", "cut a release", "prepare a release", "ship a release", "do the release".

2026-07-1493

name	cc-settings-api
description	Read and write CC Director app settings (screenshots location, gateway connection, any config.json key) by calling a running Director's Control API. Triggers on "/cc-settings-api", "set the gateway", "connect this director to the gateway", "set screenshots location", "configure cc-director settings".

CC Director Settings API Skill

Use this when the user asks to set the screenshots folder, connect a Director to a central gateway, or change any cc-director setting from the agent side.

How it works

<config> is %LOCALAPPDATA%\cc-director\config on Windows, ~/.local/share/cc-director/config on macOS/Linux, or $CC_DIRECTOR_ROOT/config if that env var is set.
Auth is OFF by default (single-user trust boundary), so no token is needed. If a Director has auth enabled, pass --director-token or the script reads it from <config>/director/gateway-token.txt.

Commands

Run from the repo root (the script needs no dependencies beyond the standard library):

# Read / write
python .claude/skills/cc-settings-api/configure_settings.py show
python .claude/skills/cc-settings-api/configure_settings.py get screenshots.source_directory
python .claude/skills/cc-settings-api/configure_settings.py set-screenshots "/Users/you/Desktop"
python .claude/skills/cc-settings-api/configure_settings.py set-gateway --url http://GATEWAY-HOST:7878 --advertised http://THIS-HOST:7879
python .claude/skills/cc-settings-api/configure_settings.py set <dotted.key> <value>

# Detect (add --apply to write the detected value straight into config.json)
python .claude/skills/cc-settings-api/configure_settings.py detect-gateway [--apply]
python .claude/skills/cc-settings-api/configure_settings.py detect-public-url [--apply]
python .claude/skills/cc-settings-api/configure_settings.py detect-screenshots [--apply]

# Test a gateway URL's reachability (/healthz)
python .claude/skills/cc-settings-api/configure_settings.py test-gateway --url http://GATEWAY-HOST:7878

Connecting a Director to a gateway (the main use case)

To make a Director on ANY network show up on a central gateway, set two things:

--url - the gateway's base URL, reachable from this machine (e.g. http://gw-host:7878).
--advertised - THIS Director's own URL, reachable from the gateway's machine. This is required whenever the gateway runs on a different machine. Without it the Director advertises loopback (127.0.0.1), which the gateway cannot call back to. On a Mac this is mandatory (the Tailscale auto-detection is Windows-only).

Example - connect a Mac Director (control port 7879) to a gateway on gw-host:

python .claude/skills/cc-settings-api/configure_settings.py set-gateway \
  --url http://gw-host:7878 \
  --advertised http://mac-host:7879

After this the Director re-registers immediately. Verify it appears in the gateway's GET /directors, or re-run show to confirm the gateway block on disk.

Notes

Do NOT hand-edit config.json while a Director is running and also use this API - go through the API so the live gateway re-apply happens. (cc-devthrottle settings is the offline path and is also round-trip-preserving.)
If no Director is running, the script fails loudly telling you to start CC Director. It does not silently write the file - starting the Director is the fix.
Output is ASCII-only.