Chat-first code experiments

Building products by texting Codex on Telegram.

This personal project documents a simple question: how far can a chat thread go before it feels like a real development cockpit? Prompts become features, summaries become commits, and Telegram turns into the control panel for shipping software.

See the experiments Open the scope

Ship a landing page for a side project and keep the copy sharp.

Drafting structure, styling, and commit-ready changes. Sending the first proposal now.

Now tighten the message and make the interface feel more editorial.

Updated. Next pass will compare prompt quality, time saved, and how much manual correction was required.

Telegram chat as the main interface for coding requests.

Core signals tracked: clarity, turnaround time, and edit depth.

24/7

A portable workflow designed for quick iteration from anywhere.

Why this exists

A personal playground for remote-first software making.

The goal is not just to generate code. It is to pressure-test a new rhythm of development where planning, implementation, review, and delivery happen inside a conversational loop.

Each session helps answer practical questions: which prompts create stable outputs, when human intervention matters most, and how much product momentum can come from a messaging app.

Current tracks

Prompt to Product

Short natural-language requests turned into interface drafts, page sections, and feature proposals.

Landing pages
Micro tools
Copy iterations

Human in the Loop

Measuring where review still adds the most value: tone, architecture, edge cases, and product judgment.

Prompt refinement
Code cleanup
Release decisions

Portable Workflow

Designing a practical system for creating, updating, and publishing software without opening a traditional IDE first.

Telegram as command layer
Codex as implementation engine
Git as delivery ledger