Building Mission Control for 10 Autonomous AI Employees
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
The stream centers on shaping Mission Control as a shared environment for specialized AI agents handling research, content, programmatic SEO, prospecting, outreach, installation monitoring, and performance analysis. Luqman works through each agent’s identity, operating contract, system prompt, and dependencies; recurring loops and schedules; always-on hosting; and an interface that distinguishes current, completed, and upcoming work while preserving human approval gates. He also explores metrics connecting agent activity to traffic and leads. The system remains under refinement and testing: neither the swarm’s effectiveness nor full automation has been proven, and open questions include alternatives to Kanban, whether a full agent harness or LangGraph is necessary, resource usage, metric validity, and the reliability of browser or API access. The wider discussion moves beyond coding into distribution and market validation. The speaker argues that traffic and sufficient data should precede firm conclusions about the product, pricing, trials, or conversion problems. Topics include trials versus limited free plans, differentiation through social media, SEO and AEO, channel and market selection, and building an audience before excessive technical polish. Practical questions cover prospect qualification, email validation, and responsibility boundaries between sourcing and closing agents, while the ethical and legal limits of competitor-data extraction and unauthorized access remain unresolved. The stream also stresses reviewing pull requests and AI-generated changes, avoiding blind trust in model advice, and using independent review without treating it as a guarantee. Concrete Burnish UI, onboarding, and performance work is discussed, but the performance audit, swarm activation, and growth outcomes remain planned or incomplete rather than demonstrated successes. The stream also contains useful topics not detailed in this overview, including learning in public and practical AI learning, freelancing and video editing, product ideation, and choosing between local and international markets. Shorter tangents address community-platform choice, a focus-music experiment with Suno Studio, conversation-context compaction, an inconclusive observation about Codex weekly renewal timing, and qualified personal opinions about hardware and AI models.
125 moments from the stream
- 1:19:40
An Observation About Codex Weekly Renewal Timing
The speaker criticizes how Codex appears to handle increases or resets, saying the weekly renewal date seemed to move with them. The automated captions are unclear, so this passage does not establish a specific service policy.
- 1:21:10
Turning User Feedback into Parallel Work and Reconsidering Kanban
He explains that outside feedback gives him a fresh view of the application and that he wants Codex to handle the resulting work in parallel. He also considers whether the system truly needs a Kanban board despite his personal familiarity with one.
- 1:25:15
Manually Compacting an AI Session to Preserve Context
He prefers manually compacting the conversation over automatic compaction, using a brief instruction intended to retain the important context.
- 1:26:31
Learning in Public and Growing Alongside AI
He presents the stream as documentation of a building and learning journey with AI and gives his view that people of varied ages and backgrounds can benefit from it. He connects personal growth with following a field whose tools and news change daily or weekly.
- 1:29:06
Mission Control as a CEO View of AI Employees
He defines the interface goal as tracking what AI employees are doing, with the user acting like a CEO overseeing a company. He considers giving each agent a name and personality to make the complex system clearer, while noting that parts of the interface concept remain unsettled.
- 1:31:24
An Experimental Understanding of Graph Engineering Through Connected Loops
He says he is still learning graph engineering and trying to apply it, tentatively describing it as combining connected loops while asking practitioners for a clearer explanation.
- 1:31:54
Clear Agent Identities and Performance Indicators for Mission Control
He accepts the suggestion to add scorecards, KPIs, and targets so agent activity is easier to understand. He also explains that he wants a firm grasp of the interface and Mission Control model before resuming testing, while acknowledging his focus on visual polish.
- 1:33:31
The Problem of AI Explanations Without References
A participant raises a practical problem: AI produces explanations they do not understand, and requests for sources do not yield useful references, leaving them unsure of the solution.
- 1:33:47
Peer Learning and Video-Editing Opportunities
He encourages beginners to discuss their problems in a peer community where members exchange expertise. He also views video editing as a skill that can be developed and offered through freelance platforms such as Upwork, without guaranteeing financial outcomes.
- 1:35:29
Acknowledging the Risk of Merging a Fix Without Reviewing the PR
After merging what he characterizes as a small fix without inspecting the pull request, he explicitly acknowledges that the action is wrong and attributes it to wanting to focus elsewhere. The moment provides a practical example of knowingly bypassing code review.
- 1:36:26
AI’s Rapid Development and Its Uncertain Consequences
He encourages keeping up with AI because of its rapid development, while balancing that enthusiasm with personal uncertainty and concern about where the technology may ultimately lead.
- 1:49:15
Evaluating Competitors by Price, Features, and Value
The speaker views attracting traffic as a shared market challenge and suggests evaluating competitors by their pricing, features, and delivered value. He expresses a preference for offering genuine value instead of relying on a low-price strategy.
- 1:52:27
An Identity and Operating Contract for Each AI Employee
The speaker describes giving each AI employee a name, persona, and job title, while exposing its schedule and the system prompt that serves as its “contract.” The aim is to make the system tangible and understandable, while ensuring that this organizational layer supports real work rather than becoming a gimmick.
- 1:54:21
Visualizing Current, Completed, and Upcoming Work
The speaker wants an interface that visually distinguishes work in progress, completed work, and work expected in the near future, while questioning what should replace a Kanban board. He also considers a future organizational structure with agents acting as department managers and HR-like roles, though implementation details remain unresolved in this excerpt.
- 1:56:42
A Practical Visual Interface for Mission Control
A visual mock was requested to show where work is now, where it goes next, and what happened previously. A virtual office with moving employee characters and task handoffs was discussed, but the stated preference was for a clear, polished interface without excessive simulation or animation.
- 1:58:21
LangGraph or LangChain for a Non-Sequential Workflow?
Asked about LangGraph and LangChain, the speaker said he was not currently using either, but would lean toward LangGraph if choosing because the discussed stage needs a non-sequential workflow. The technical explanation remained brief and incomplete.
- 2:01:13
Traffic First to Understand Conversion Problems
The speaker argues that increasing traffic should precede conversion optimization because a small number of installs does not provide enough data points to identify why people do not buy. In this view, even a lack of sales becomes more diagnosable with more traffic and data points.
- 2:04:08
Keyword-Based Shopify Ads
Shopify ads were described as keyword-based, with a general comparison to Google Ads; spending may vary depending on the keywords. A comparison with Facebook began but was not completed.
- 2:06:20
Designing a UI to Monitor AI Employees
He describes a UI for seeing what the employees are doing over time. The backend logic, workflows, and instructions were presented as provisionally prepared but still requiring testing and refinement, so the current focus was on making the interface clear and comfortable to use.
- 2:07:58
Fixing the Manifesto Regression and Onboarding Discoverability
The discussion traces a manifesto regression to renaming the Intelligence page as Market Scout and relocating the manifesto, leaving an outdated settings version without the intended refinement flow. The proposed sequence is to inspect the pull request, fix the manifesto first, and later consider placing it in onboarding because beta feedback indicated that users were not discovering it easily.
Got a question about something in this stream?
Ask in the group