---
title: "JAY TANK (@jaytank) | Hashnode"
description: "Engineering insights on building and scaling modern software. Read the latest articles by JAY TANK on Hashnode."
url: "https://hashnode.com/@jaytank"
---

@jaytank

# JAY TANK

@jaytank · Joined July 2026

Engineering insights on building and scaling modern software.

### [The duplicate key that eats your config - and the 180-line CLI that catches it](https://jaytank.hashnode.dev/dupekey?utm_source=hashnode&utm_medium=feed)

A repeated key in a dict literal or a JSON object is not an error in Python - it silently keeps the last value and drops the rest. Here is dupekey, a tiny offline CLI that finds that quiet correctness bug in both your Python source and your JSON, and fails CI before it ships.

6 min read · [jaytank.hashnode.dev](https://jaytank.hashnode.dev/dupekey?utm_source=hashnode&utm_medium=feed)

[Nov 2](https://hashnode.com/posts/dupekey/6ae80268fecdcea9fd4a0136)

### [Your AI coding agent's dev container is not a sandbox: docker.sock, --privileged and ~/.ssh mounts](https://jaytank.hashnode.dev/boxescape-devcontainer-docker-sock-ai-agent-sandbox?utm_source=hashnode&utm_medium=feed)

Running Claude Code, Codex or Aider in a dev container feels safe, until the container gets privileged mode, the host Docker socket, the host network or your ~/.ssh and ~/.aws folders. Here is what the Docker and Dev Container docs say about each setting, how to fix them, and BoxEscape, a free VS Code extension that flags them in devcontainer.json, Compose files and docker run scripts.

10 min read · [jaytank.hashnode.dev](https://jaytank.hashnode.dev/boxescape-devcontainer-docker-sock-ai-agent-sandbox?utm_source=hashnode&utm_medium=feed)

[Oct 30](https://hashnode.com/posts/boxescape-devcontainer-docker-sock-ai-agent-sandbox/6ae411027f0f5a17e833e5b5)

### [OpenAI API key exposed in the browser: NEXT\_PUBLIC\_, VITE\_ and dangerouslyAllowBrowser explained](https://jaytank.hashnode.dev/browserkey-openai-api-key-exposed-next-public-vite?utm_source=hashnode&utm_medium=feed)

One prefix on an environment variable is enough to put your OpenAI or Anthropic key into the JavaScript every visitor downloads. Here are the five ways AI API keys reach the browser, how to move the call to the server, and BrowserKey, a free VS Code extension that catches each of them before you deploy.

9 min read · [jaytank.hashnode.dev](https://jaytank.hashnode.dev/browserkey-openai-api-key-exposed-next-public-vite?utm_source=hashnode&utm_medium=feed)

[2](https://hashnode.com/posts/browserkey-openai-api-key-exposed-next-public-vite/6ae16d1e93e5da56b943869a) [Oct 28](https://hashnode.com/posts/browserkey-openai-api-key-exposed-next-public-vite/6ae16d1e93e5da56b943869a)

### [\--dangerously-skip-permissions in CI: where AI agent YOLO flags turn prompt injection into full access](https://jaytank.hashnode.dev/yologuard-dangerously-skip-permissions-ci-security?utm_source=hashnode&utm_medium=feed)

Claude Code, Codex CLI, Gemini CLI and friends all ship a flag that switches every approval off. That flag is fine in a throwaway container and a disaster in a CI job with secrets that reads issue text. Here is how to tell the two apart, and YoloGuard, a free VS Code extension that does it for every workflow, script and devcontainer in your repo.

10 min read · [jaytank.hashnode.dev](https://jaytank.hashnode.dev/yologuard-dangerously-skip-permissions-ci-security?utm_source=hashnode&utm_medium=feed)

[Oct 26](https://hashnode.com/posts/yologuard-dangerously-skip-permissions-ci-security/6aded47882f424404f1fdb29)

### [docker compose depends\_on does not wait for your database: fix "connection refused" on startup with healthchecks](https://jaytank.hashnode.dev/readywait-docker-compose-depends-on-connection-refused?utm_source=hashnode&utm_medium=feed)

Your app crashes with ECONNREFUSED or "could not connect to server" on docker compose up, then works on the second try. Why depends\_on only waits for the container to start, the healthcheck fix, the service\_healthy trap, and a free VS Code extension that flags it.

10 min read · [jaytank.hashnode.dev](https://jaytank.hashnode.dev/readywait-docker-compose-depends-on-connection-refused?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/readywait-docker-compose-depends-on-connection-refused/6ad58c3e9d03041a783b3468) [Oct 19](https://hashnode.com/posts/readywait-docker-compose-depends-on-connection-refused/6ad58c3e9d03041a783b3468)
