I built a local web dashboard to run Claude Code and Codex CLI in parallel

May 24, 2026 · 10:00 AM UTC ·3 min read · 0 reactions · 0 comments · 35 views

TL;DR · WeSearch summary

Hiroshi Ishizaka developed a local web dashboard called any-ai-cli to manage Claude Code and Codex CLI sessions simultaneously. The tool allows users to handle approval prompts and monitor multiple coding agents from a single interface. It is designed to enhance productivity by consolidating terminal outputs and providing real-time interaction through a browser.

Key facts

▪The any-ai-cli dashboard wraps AI coding CLIs in a PTY and mirrors their output in real time.
▪Users can approve or reject prompts directly from the browser, keeping the terminal and UI in sync.
▪The tool is built as a single Go binary and prioritizes user privacy by binding to localhost and not sending telemetry.

How this story was covered

2 outlets in our directory ran this story, first to last over 8 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.

Centre · 1

▪ Built a free self-hosted web terminal interface for Claude Code CLI — r/ClaudeAI

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	DEV.to (Top)
Canonical URL	https://dev.to/ishizakahiroshi/i-built-a-local-web-dashboard-to-run-claude-code-and-codex-cli-in-parallel-2coe
Publication time	Sun, 24 May 2026 10:00:25 +0000
Retrieval time	2026-05-24T10:07:32.096Z
Last seen	2026-05-24T10:07:32.096Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	N-GaGxDu6TSj · 2 stories
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3912564) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Hiroshi Ishizaka Posted on May 24 I built a local web dashboard to run Claude Code and Codex CLI in parallel #ai #cli #cloudecode I run Claude Code and Codex CLI side by side a lot. The coding part is great — the annoying part is everything around it. Which terminal is waiting for an approval? Which session is still working, and which one quietly finished ten minutes ago? Tabbing between terminal windows just to hit "yes" got old fast.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed

Discussion

0 comments