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
- 4:24:30
Exploring Hermes memory mechanisms
The speaker considers memory a strength of Hermes and explores borrowing some of its mechanisms rather than solving the entire memory problem himself. This is a possibility under consideration, not a completed implementation.
- 4:29:52
The importance and limits of harness engineering
The speaker expects harness engineering to become very important, while stressing the need for a strong underlying idea and calling it a double-edged sword without elaborating on the risks.
- 4:33:11
Explaining a temporary coffee example on the website
In response to an audience question, the speaker explains that the coffee image was an illustrative experiment involving an idea, intent, and launch preparation, and says he plans to remove it from the website.
- 4:33:48
Automated comment replies with human approval
The speaker describes a system that automatically reads and replies to Instagram and TikTok comments, with a human approval step. He explains that some followers mistakenly assume he manually passes each comment to AI for a response.
- 4:34:43
An agent control center combining context and project management
The speaker proposes a control center that could replace IDEs and combine automation with context and knowledge graphs. Embedded project management would track roadmaps, while discussion of the core engine should precede interface details.
- 4:39:07
An acquisition as a possible signal of market demand
The speaker discusses an acquisition he believes occurred a week or two before the recording and interprets it as a signal of market demand. Company names and some surrounding details are unclear in the captions and are omitted.
- 4:44:10
How should a voice agent handle a potentially counterproductive instruction?
For a conversational voice interface, the speaker suggests acknowledging explicit instructions while explaining consequences or proposing a better alternative when appropriate, using dropping mobile support as an example.
- 4:45:05
Choosing a real staging environment
The speaker accepts a recommendation to use a real staging environment. This passage does not establish the intended validation scope or report execution results.
- 4:51:59
A mention of an upcoming hackathon in Syria
A brief mention describes a hackathon expected in Syria at the time of recording, with investors reportedly attending. No date or organizer details are provided.
- 4:52:11
A beginner’s question about working efficiently with coding agents
A question asks how to build faster and more efficiently with limited agent experience. The response begins clarifying difficulties using agents and writing prompts, but the captions end before complete guidance is given.
- 4:55:12
Requesting session creation through computer use
Luqman describes using a tool inside the Claude Code app’s GUI and requests session creation through computer use, targeting the correct folder. This passage does not establish that setup was completed.
- 4:57:15
Critiquing bird cutouts and motion in a teaser design
Luqman criticizes the bird’s background removal, awkward entrances, apparently floating branches, and the background. He suggests placing the birds on a ground surface and questions why the assistant can explain its mistakes after criticism without addressing them beforehand. These are his assessments; no successful correction is established here.
- 5:00:47
Taking a break when work becomes frustrating
After criticizing the result, Luqman decides to stop and says that taking a break can sometimes be the best next step.
- 5:01:12
Brief milestone and smoke-test update
Luqman reports completing a project milestone and running a quick smoke test that day, saying he believes the work is functioning well. The passage does not explain the test’s scope or detailed results.
- 5:01:35
Ongoing livestream transcription work
Luqman mentions ongoing background work on livestream transcription, without explaining its implementation in this passage.
Got a question about something in this stream?
Ask in the group