What Happens If This Works?
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
Luqman explores an early open-source tool concept that starts with user goals and coordinates agent teams to build and operate projects, potentially through voice. Discussion covers agent harnesses, memory, knowledge and context graphs, RAG, and custom development versus learning from existing tools such as Hermes. Feasibility and the eventual interface remain unresolved. Practical work includes repeated reviews of a bilingual teaser page, clearer messaging, bird animation, and audience polls to choose a name, without a final naming decision. Domains are discussed separately, with availability checks reflecting the time of recording. Blogging and SEO agent work includes requests to review articles while keeping daily publishing paused. A comment-reply system is described as retaining human approval. The discussions do not establish completion of these improvements. Audience questions examine token limits versus quality and when agents should retry or seek help. The discussions also examine Luqman’s requests for clearer roadmaps and verification before approval, practical evaluation of Codex and Claude, model-intermediary privacy, sustained use as demand validation before monetization, branding, marketing, and web-service pricing. Luqman reports that a Shopify app competitor was acquired within the two weeks preceding the stated recording date, October 16, 2026. He interprets this as a possible demand signal; no confirmed acquisition price is provided. The discussion includes a simplified explanation of IPOs and financial disclosure, using a hypothetical Anthropic listing as an example. Predictions about future interfaces and AI pricing after IPOs are explicitly uncertain, while some privacy and performance questions remain unverified. Luqman encourages proactive self-directed learning and asking questions, mentioning courses as a structured option without recommending a specific platform. An audience contribution describes a site being polished that collects tech and AI news and features skills, tools, and open-source apps. Discussion touches on making the project open source and monetization, without enough clarity to establish a revenue model. The discussion also covers disk space repeatedly filling after cleanup, keeping local recordings for higher-quality short clips, and ongoing background work on livestream transcription. No storage diagnosis or fix is established, and the transcription implementation is unexplained.
115 moments from the stream
- 0:41:36
Requesting a Telegram poll test
Requests opening Telegram and preparing a poll in a test group with a short Egyptian Arabic message. The page ends during the instructions and does not establish an execution outcome.
- 0:41:56
Drafting an Arabic product-naming poll
Directs an assistant to draft a community post that briefly explains the product and previews its website, preferably with animation if possible, then discusses candidate names for a poll.
- 0:44:13
A landing page that visually explains the AI-team mission
Requests a single page with at most two sections that visually communicates giving goals to teams that work toward them. The brief emphasizes the mission over terminal or interface details and calls for brainstorming before implementation.
- 0:45:23
A bilingual name and an Arabic-first launch
Discusses choosing a name that works in Arabic and English and supporting both languages because the Arabic-speaking community will be the first audience. Making English primary later is presented as a possibility if the product gains traction.
- 0:48:54
Agent-tool recommendations and learning memory harnessing
Among agent-tool recommendations, the speaker points to Hermes as a useful example for learning memory harnessing and praises its design. This is the speaker’s assessment; several other tool names are unclear in the captions.
- 0:49:35
Domain flexibility when choosing a product name
Argues that domain availability need not block the preferred product name, suggesting alternatives such as adding go or try before the name.
- 0:50:10
Validating value and usage before monetization
Proposes postponing monetization until the product demonstrates practical value and sustained use. In the speaker’s view, brief interest in a gimmick is insufficient, and competing tools or AI advances could reduce the idea’s usefulness.
- 0:53:37
Trying an idea with a web app
Luqman suggests trying an idea through a web app because it is somewhat easier to start, while acknowledging that a native app is also possible.
- 0:55:00
How can startups adapt as AI platforms advance?
A discussion considers AI platforms such as Anthropic and OpenAI absorbing capabilities offered by startups. Luqman argues for understanding the market’s direction, building around it and adapting quickly, citing an unclearly named product-image service that he says pivoted.
- 1:00:10
Polling the audience to name a tool
Luqman invites the audience to a Telegram poll about naming the tool being built. The captions do not clearly establish the proposed names’ spelling.
- 1:01:06
Comparing website pricing in France and Egypt
Luqman uses hypothetical website fees and currency conversion to explain his impression of pricing differences between France and Egypt.
- 1:03:10
Preparing a naming poll on Telegram
Luqman prepares a poll to gather audience feedback and discusses allowing additional name suggestions. He objects to preparing the poll manually because of the time involved.
- 1:06:04
What is needed before milestone sign-off?
Luqman requests a precise, concise account of completed work, exactly what he would approve, and what he should inspect and test before signing off on the first milestone. The captions do not establish that those tests were performed.
- 1:06:34
Reviewing a goal-based demo and preparing a handoff
He explains an example that starts with a request to prepare a coffee-brand launch, then expresses dissatisfaction with the result. He asks to discuss the strategy and prepare a handoff to try an alternative, and proposes displaying “AI employees” in the demo.
- 1:07:57
An audience view on France’s web development market
An audience contribution describes strong demand for websites and web apps in France and asks about exploring French companies when one speaks French. This is a discussion claim, without supporting market data.
- 1:09:26
Comparing two models with identical instructions
Luqman describes an earlier comparison that he says used identical prompts and instructions. He prefers one output’s livelier presentation and zooming, while describing the other as slow and containing errors. He cautions against inferring overall superiority and considers the models broadly close.
- 1:12:42
A reaction to the Tesla Roadster and technological progress
Luqman expresses amazement at the Tesla Roadster and general unease about rapid technological progress. This is a personal reaction, without specifications or verification of the car’s capabilities.
- 1:14:16
Evaluating coding tools through practical use and value
Luqman argues for judging a model through work on a real project with users and clients. The discussion includes comparative opinions about Codex and Claude for frontend work and design, alongside value for cost; these are expressed preferences rather than documented test results.
- 1:15:38
Following up on the naming poll and sharing its link
He requests a direct link to the existing poll, then awaits audience feedback and discusses his impressions of suggested names. No final naming decision is established here.
- 1:16:58
Requesting step-by-step verification guidance
Luqman asks the assistant to walk him through checking the work one step at a time. The request does not establish that the review was completed or that checks passed.
Got a question about something in this stream?
Ask in the group