Home / Blog / Show HN: CliTimes - Times lives on your CLI (with Claude…
Tech News

Show HN: CliTimes - Times lives on your CLI (with Claude Code)

A developer going by howieyoung published CliTimes to GitHub, a command-line tool that renders a Times-style world clock display directly inside a terminal.…

By Dillip Chowdary • Aug 10, 2026 • Source: HN Claude/Codex/Fable

Show HN: CliTimes - Times lives on your CLI (with Claude Code)

What happened

A developer going by howieyoung published CliTimes to GitHub, a command-line tool that renders a Times-style world clock display directly inside a terminal. The project surfaced on Hacker News under the Show HN tag, accumulating 2 points and 3 comments at the time of writing. The author credits Claude Code as a collaborator in building the project, framing it explicitly as an AI-assisted build rather than a solo effort from scratch.

The core mechanic is straightforward: CliTimes takes one or more time zones as input and renders them in a formatted, readable layout inside the terminal, mimicking the kind of world-clock panel you might see in a newsroom or trading floor display. The CLI paradigm means no browser tab, no app switching, and no latency from a web request — the display lives in whatever terminal session you already have open. The implementation is hosted on GitHub, and the project name plays on the double meaning of "times" as both time zones and the newspaper aesthetic it emulates.

The technical detail

Show HN: CliTimes - Times lives on your CLI (with Claude Code)
Illustration · Pexels

For engineers, the interesting part is not the feature itself but the workflow signal. Using Claude Code to ship a self-contained, aesthetically deliberate CLI tool points to a growing pattern where AI assistants handle the scaffolding, boilerplate, and layout logic while the human contributor focuses on the concept and the taste decisions. CliTimes is small enough that its entire surface area is visible — it is the kind of project where you can read the whole codebase in under ten minutes — which makes it a clean case study in what AI-assisted greenfield work actually looks like at the small end of the scale.

Advertisement

Tech Pulse Daily

Get tomorrow's pulse first

Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.

Why it matters for builders

The competitive context is thin but instructive. Tools like tzclock, world-clock-cli, and even simple one-liners using the date command with TZ= prefixes have existed for years. What CliTimes adds is visual intentionality — the "Times" framing suggests a deliberate typographic or layout sensibility rather than a raw data dump. Whether it meaningfully differentiates from existing solutions depends on execution details that the repository would need to surface, but the positioning is clear: this is a display-first tool, not a utility-first one.

The Claude Code attribution is worth noting separately from the tool itself. Anthropic has been positioning Claude Code as a terminal-native coding agent, and projects like CliTimes are exactly the kind of real-world artifacts that validate or challenge that positioning. A small, finished, published project is a stronger signal than a demo — it means the agent completed a full loop from idea to working code to public repository, even if the human contributor guided that loop heavily. The Show HN post is itself a form of documentation for that process.

Market and competitive context

What to watch next is whether the project accrues contributions or forks that extend it beyond the single-developer use case. A world-clock tool becomes more interesting the moment it supports configuration files, team-specific zone presets, or integration with shell prompts. The current state — 2 points, 3 comments — suggests it has not yet found its audience, which is common for Show HN posts that solve a narrow personal problem. If the author ships a follow-up with a config layer, it enters a different competitive tier.

What to watch next

The risk inherent in AI-assisted projects of this size is maintenance orphaning. When the original implementation is generated rather than hand-written, the author's mental model of the code may be shallower than in a fully manual build, making it harder to triage issues or extend features without re-engaging the AI assistant. That is not a fatal flaw — it is a new kind of authorship relationship — but it does raise the question of what happens when Claude Code's output does something unexpected and the human maintainer needs to debug without a full mental map of the internals. CliTimes is simple enough that this is unlikely to matter in practice, but the pattern will matter more as AI-assisted projects grow in scope.

Advertisement

🔎 More interesting news

5-min tech signal

Weekday briefing for engineers who skip the noise.

No spam · Unsubscribe anytime

Advertisement

✈️ CareerPilot

Your AI job-search copilot

Match your resume against live Ashby, Greenhouse & Lever openings — fit scores, job-specific resume optimization and email alerts.

Find matching jobs →

Free Tools

Browse all tools →