Daily Tech Digest: Skills Ops, Dev.to Publishing, and Codex WebUI Debugging

Date: February 14, 2026

Overview

The last 24 hours focused on tightening the Codex skills workflow, standing up reliable Dev.to publishing, and debugging the Electron-based Codex WebUI. There was also exploratory work on flight-deals scraping targets and CLI options.

What Shipped

• Skills repo hygiene and syncing: Work centered on the local skills directory, updating ignore files, checking git status, and preparing a sync path to https://github.com/FriunsHome/Skills.git. There was also a request to create a skill to synchronize skills and clarify GitHub org permissions.
• Dev.to publishing pipeline: Multiple steps around Dev.to API usage: locating API keys, verifying published articles and view counts, creating a “hello world” draft, and formalizing the publish-articles skill. The intent shifted toward automating daily and weekly digests with --published true.
• Codex chat mining for content: Requests to search Cursor/Codex chat logs for Dev.to API references and blog-posting scripts indicate the digest pipeline will be built from chat history rather than manual notes.
• Codex WebUI debugging: Investigation into Electron launch issues, missing UI, renderer-guard patch failures, and WebUI startup scripts (launch_codex_webui_unpacked.sh). Follow-up items included checking logs, fixing WebUI, and keeping documentation in guide format.
• Oracle Cloud ops: Used oracle-cloud-cli guidance to connect to an A1 instance, verify Codex installation, and locate skill directories for replacement.
• Flight data reconnaissance: Targeted GitHub code searches for Skyscanner and Google Flights batch endpoints, plus exploration of gflights and a request for non-stop one-way deal links from Ho Chi Minh City.

Notable Decisions

• The Dev.to pipeline should be driven from local chat history plus structured markdown generation, with publish handled by scripts/devto_publish.sh.
• WebUI fixes should preserve guide-format documentation while focusing on launcher scripts and patch anchors.

Next Steps

• Finalize a daily automation that collects the last 24 hours of Codex sessions into a digest and publishes it.
• Stabilize the Electron WebUI launch path and confirm codex binary discovery.
• Decide whether flight-deal scraping should proceed via gflights CLI or direct endpoint integration.