How should I handle authentication?

Credentials stay outside the agent; authenticate against the Iron Proxy itself if required. Real API tokens remain with the operator who approves connections.

What happens after login expires?

Reconnect the affected upstream service following whatever refresh procedure applies to it. If failures persist, inspect whether the block comes from auth expiry versus policy denial.

Iron Proxy gateway

SkillDev tools

Iron Proxy Gateway is a dev-tools skill that lets you use iron-proxy-gateway style routing for external accounts and APIs from inside an AI agent session. The skill sends outgoing calls such as GitHub access through gh by way of an Iron Proxy instead of handing raw secrets to the model. A human operator connects credentials on the other side of the proxy and approves traffic there.

Use Iron Proxy gateway in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add Iron Proxy gateway and connect your AI. About a minute.

Claude ChatGPT Ahel Desktop

Also: Claude Code · Cursor · Codex

Then ask your AI: use the Iron Proxy gateway skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.

No other account needed.

Have an Iron Proxy reachable from wherever the agent runs.

Iron Proxy gatewayStart free

What your AI can do with it

Route agent HTTP and HTTPS requests through an Iron Proxy
Call GitHub through gh while keeping credentials behind the proxy
Let a human operator approve credential injection per request
Keep the agent seeing only a placeholder token rather than real values
Diagnose blocked 401 or 403 responses without revealing tokens

Getting started

Have an Iron Proxy reachable from wherever the agent runs.
Add the gateway configuration so the agent points its outbound web requests at that proxy.
Connect the needed account (for example GitHub) over the provided connection path used by the setup.
Confirm approvals work end-to-end before relying on them.

What this skill tells your AI

The instructions your AI receives, as published by nanocoai/nanoclaw in .claude/skills/add-iron-proxy/payload/container/skills/iron-proxy-gateway/SKILL.md and read by ahel’s review.

Your outbound HTTP and HTTPS requests pass through your session's Iron Proxy. A policy-selected credential request waits for human approval before the proxy inserts a credential. You receive only a useless placeholder.

Policy failures

A bare 403 does not prove which layer rejected the request. It may be the destination rule, credential grant, human approval, or upstream API. Respect the block, report the hostname and observed error, and request a host-side check instead of guessing that credentials were never injected.

Connect an account

Run the shared command for the API hostname requested by the user:

ncl groups connect --host <API hostname>

Return the exact connect_url and describe its action. An operator_console handoff requires the operator to configure the credential, grant, and destination in the gateway; it is not an OAuth link. Do not invent a connection flow when the result is unsupported. The command does not grant access or change policy.

Use the user's requested CLI or a direct HTTP client. Do not add an MCP server merely to connect an account. Clients requiring local authentication may use gateway-managed as a non-secret placeholder (for example GH_TOKEN for gh). Never use a real token in the client. Never run a local login to store credentials.

Request approval and account connection are separate. A 401 is not proof that injection did not happen: the stored token may itself be invalid. Report the observed result, follow the shared handoff, and verify with a credentialed request after the operator completes configuration. Never claim connected before success.

Rules

Never ask for, print, or store a raw API key or OAuth token.
Never bypass the configured proxy or its CA validation.
Never treat a pending approval as granted.
Never claim a blocked destination is connected.
Treat proxy errors as policy or operator-configuration errors, not as permission to weaken TLS.

Signals

GitHub stars: 31k
Forks: 13k
Last commit: Sep 2026

Questions

How should I handle authentication?: Credentials stay outside the agent; authenticate against the Iron Proxy itself if required. Real API tokens remain with the operator who approves connections.
What happens after login expires?: Reconnect the affected upstream service following whatever refresh procedure applies to it. If failures persist, inspect whether the block comes from auth expiry versus policy denial.

Advanced

Item type: skill
Key: iron-proxy-gateway
Source: github.com/nanocoai/nanoclaw

github.com/nanocoai/nanoclaw