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
- 3:18:16
Assuming users arrive with an existing project
The speaker assumes that most users will arrive with projects they already have. This is a target-audience assumption; the page provides no validation of it.
- 3:25:04
Is the goal a demonstration to check feasibility?
A question asks whether the intended goal is simply a demonstration to check whether an idea is possible. The passage provides no clear answer or test result.
- 3:25:55
Naming a tool: brevity, memorability, and domain availability
An audience discussion considers a tool name and the difficulty of finding an available short domain. One comment argues that easy pronunciation does not guarantee memorability and may require marketing; Luqman argues that shorter brand names are stronger and more valuable.
- 3:29:11
Teaser review: a simpler headline and animated bird characters
Luqman critiques the design direction and requests brainstorming for a more striking headline with less text. He rejects the birds-flying-toward-the-sun concept and proposes including and animating the remaining bird characters. These are requested changes, with no completed implementation established.
- 3:32:32
Intent-driven IDEs: graphs and memory
Luqman outlines a vision for future IDEs that understand user intent and goals with less verbal guidance through agent harnessing and knowledge and context graphs. He envisages systems that both accomplish and manage goals, and considers memory an important area for innovation.
- 3:33:48
AI memory and learning from open-source memory tools
The speaker considers memory a major challenge and suggests researching a tool he describes as open source with strong memory management, while explicitly stopping short of calling the problem solved. The tool’s name is unclear in the captions.
- 3:34:47
Short domain names and domain trading
An audience discussion explores domain-name suggestions and availability checks, with the speaker favoring a single-letter naming element. It also touches on domain trading and possible interest in SI domains associated with superintelligence; claims about that trend remain unverified.
- 3:45:12
AI memory: context, graphs, and RAG
Luqman considers memory an unresolved challenge and asks for deeper design exploration using knowledge graphs, context graphs, and RAG, questioning how the proposed capabilities differ from existing assistants. He also references a study he describes as roughly a year old about performance declining as context fills; its details are unclear in the captions.
- 3:50:17
Local 4K recording for higher-quality shorts
Luqman explains that he keeps local 4K recordings to improve the quality of short clips, while reporting a lower streaming-resolution limit in his setup. This connects to the page’s earlier discussion of the storage demands of stream recordings.
- 3:53:16
Trying an existing tool before building your own
A suggestion is raised to use an existing tool temporarily to understand how it works before building a custom alternative. This follows an audience tool recommendation whose name is uncertain, with Luqman acknowledging limited firsthand experience with the tools mentioned and considering integration if needed.
- 3:56:00
Custom building versus ready-made skills
The speaker prefers building ideas himself when he can, while acknowledging that he uses many ready-made skills, particularly for things he cannot implement.
- 3:58:39
Clarifying an idea through questions before implementation planning
A “Grill me” session is directed toward understanding the intended idea first, before coordinating further work on a project roadmap and implementation plan.
- 3:59:13
An open-source resource for tech news and tools
An audience contribution describes a site being polished that collects tech and AI news and features skills, tools, and open-source apps. The discussion touches on monetization and making the project open source for everyone, without enough clarity to establish a revenue model.
- 4:05:53
When should an agent keep trying or ask for help?
A question weighs trying alternative approaches within approved time and resources against involving the user early to conserve them. Luqman views exploring alternatives as part of the purpose, while emphasizing that the decision depends on the problem.
- 4:08:42
An Arabic font change for the website
An audience suggestion proposes an Arabic font they consider more suitable for the site's identity and more professional. Luqman agrees to try replacing the current font and formulates a request; the font name and outcome are unclear on this page.
- 4:11:22
Exploring the feasibility of an open-source tool
Luqman outlines an early idea for a tool intended to be open source and connected to his vision for AI's future. Its name remains undecided, and he is still exploring whether he can build it, without detailed technical explanation here.
- 4:12:34
Agent updates and splitting milestones into sessions
A question considers updates only when a user decision is needed versus brief milestone updates. Luqman then proposes a separate session for each task instead of running an entire milestone at once, with checks for overlap and dependencies; the page does not establish the proposal's outcome.
- 4:15:08
Splitting coding sessions by mission
Proposes running a coding session for each mission rather than an entire milestone, then comparing resource usage. No comparison result is reported here.
- 4:17:54
Choosing a name for an open-source project
Discusses candidate names with the audience, weighing brevity, brand strength, spelling and domain availability. He personally favors a shorter name while considering spelling variations and more time to decide; no final choice is announced.
- 4:22:16
A brief reference to context graphs, knowledge graphs and harnessing
References an earlier discussion of context graphs, knowledge graphs and harnessing in connection with a project vision whose feasibility remains uncertain. This is a brief reference rather than an explanation of the concepts.
Got a question about something in this stream?
Ask in the group