Building AI Apps Live from Cairo 🌙
Want to back the stream? The «داعم» membership on YouTube is EGP 60 a month: badges, emoji, and I answer your questions first on stream. Become a supporter
The gist
A long practical stream documenting a website being built in public with coding agents, from preparing files and specifications and creating logo variants in Canva to reviewing the interface, contrast, responsiveness, Arabic text direction, and links. Luqman discusses organizing instructions, skills, and permissions across Codex and Claude, keeping instruction files compact, and preserving documentation for continuity between sessions, while leaving open questions about context-window consumption, autonomy, and assistant reliability near its limits. In a direct comparison, he felt Codex produced the stronger interface in that attempt—an attributed impression, not a general verdict. The work then moves through GitHub and Cloudflare, encountering Pages-versus-Workers confusion, static-asset, preview, authentication, and DNS issues. The site eventually worked after a JSON configuration change, though the reason remained unclear, and domain propagation still needed later verification. The stream also covers his vision for an Egyptian vibe-coding community, the value of a manifesto and roadmap, and a pre-review checklist for Shopify apps. It ends as an early-stage record requiring further polish and follow-up, not as a confirmed completed project or launch.
52 moments from the stream
- 0:00:32
Why He Builds Projects Publicly on Livestream
Luqman explains that he thinks aloud while coding and speaks to AI agents by voice. He chose to show the building process live because, in his view, full practical build streams were uncommon. This records his motivation and workflow, not a claim of a successful outcome.
- 0:04:49
Scoping the Project Explorer to One Folder
After recovering previously lost files, Luqman describes a Warp project-explorer problem: it shows files from across the computer instead of only the selected project. He formulates the practical question of how to scope the view to the project folder, but the excerpt does not contain a confirmed solution.
- 0:09:08
Preparing Project Files Before Building a Website
Luqman opens the project folder in preparation for building a website, then notices that required Markdown files are still missing. He identifies finding and adding those files as a prerequisite before continuing; this section does not record the website as completed.
- 0:12:54
Reviewing Website Specifications Before Building
A review of the documents and specifications for a website intended to be hosted on Cloudflare, including available assets, social links, and email-capture configuration. The missing action would remain a placeholder while the site was inspected for gaps before refinement.
- 0:15:35
Dated Review of the Agent Environment and Project Permissions
A request to review the AI-agent work environment against best practices as of March 9, 2026, including possible improvements to memory, functionality, and subagent organization. The review also covers project permissions to reduce repeated execution approvals, with a discussion of proposed changes before implementation.
- 0:17:20
Using Codex to Refine the Website UI
A plan to build the website first and then use Codex to improve its interface formatting. The motivation is an attributed opinion from others that Codex is strong at UI design; the version number shown in the captions is unclear and is not asserted.
- 0:18:18
A Whiteboard for Tracking Project Progress
The display and camera setup is tested alongside a whiteboard, which is intended to be improved over time because it is important for tracking project progress.
- 0:19:36
Attempting a Local Website Preview
After a build stage finished, the website preview was opened on localhost port 3000, but it was not loading by the end of the page; the source provides no diagnosis or resolution.
- 0:22:37
Structuring Coding-Agent Settings and Permissions
The discussion covers project setup with a build command and configuration files, tightening global permissions while keeping project rules narrowly scoped, and adding skills and custom agents. It also requests concrete sub-agent ideas, while leaving unresolved the tension between reducing permission prompts and broadly auto-allowing commands.
- 0:26:58
Initial Review of the Site Interface and Missing Links
A quick site review begins with the observation that the interface feels very dark and a check of what it still needs. The structured review then identifies missing links, but the page ends before any changes or outcomes are shown.
- 0:28:12
Investigating a Localhost Loading Problem
After the site worked locally once, localhost stopped loading when reopened. The discussion asks whether the development command must be run each time, then postpones diagnosis to inspect the site’s appearance and missing elements; no confirmed resolution is shown.
- 0:30:27
Improving the Landing-Page Design
The landing-page review identified outdated information, a missing navigation menu, and a background that was too dark for the text to blend or contrast well. A mix of dark and off-white colors was suggested, with attention to these visual nuances.
- 0:32:09
Agent Safety Controls and Automatic Skill Triggering
The discussion proposes preventing the coding agent from pushing to Git or force-deleting files without consent, then adding skills to the project. The preference was for the agent to select and trigger skills automatically from their descriptions, the prompt, or the task instead of always relying on manual activation.
- 0:37:46
Presenting Links and the Technology Stack on a Project Site
The site was asked to present social links and the technology stack alongside a general view of the work. Clearly named tools included Shopify, Gemini, ChatGPT, Claude, Codex, Cloudflare, and Railway, and the content was requested as a Markdown file; unclear or private names were omitted.
- 0:41:31
Updating Website Links from a Markdown File
The agent was asked to store an attached Markdown file in the documentation section, then use its information to replace outdated links on the website.
- 0:42:53
Why Keep an Agent Instructions File Compact?
The discussion explains that an agent reads the project's instructions file at the start of each session, consuming tokens and context-window space. It therefore recommends keeping the file compact while retaining the information the agent must consistently know.
- 0:45:09
Agent Autonomy Settings and Restarting
When another agent still requested permission to run a Bash command, the speaker questioned whether the autonomy settings had fully taken effect and noted that the agent had not been restarted after those settings were added.
- 0:47:53
Preparing Logo Variants in Canva
A practical brand-asset update began in Canva, including preparation of square and horizontal logo variants and an attempt to export an asset with a transparent background; some format and filename details are unclear in the captions.
- 0:52:02
Replacing Website Logos and Integrating the New Branding
A discussion of placing new logo files in the appropriate folder, removing the previous logos, and creatively integrating the new assets into the website to evaluate their appearance.
- 0:57:29
Reviewing Landing-Page Mobile Friendliness and Empty Space
The start of a Codex-assisted landing-page review covering mobile friendliness, links, and an improvement prompt, with excessive gaps and empty space above the fold identified as a design issue.
Got a question about something in this stream?
Ask in the group