TALKSTORE PIVOT
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 follows TalkStore’s public build after Shopify rejected its storefront domain: related code and references were removed, documentation and the roadmap were revised, and the app began repositioning around product operations. Proposed directions include an assistant that can act on Shopify tasks, understand product images and text, improve content in bulk, and potentially support GEO; these remain unproven ideas, while the product’s replacement advantage, defensibility, and market demand still require research and validation. In practical work, Luqman experiments with a command center that distributes tasks across Codex, Claude, and other tools while tracking dependencies, activity, and reviews. Unresolved issues include task-status synchronization, usage limits, and the cost of parallel agents; his tool comparisons are time-specific impressions rather than controlled tests. He also discusses separating engineering from debugging, QA, and manual pre-submission review, and establishing an adaptable billing foundation while plans and pricing remain provisional. Audience questions broaden the discussion to validating demand before building, software economics, distribution and B2B adoption, and dependence on platform rules. The main supported conclusion is that coordination, market validation, and distribution matter as much as build speed, while the product, workflows, and tool experiments remained works in progress rather than completed successes.
68 moments from the stream
- 3:14:54
A personal assessment of Gemini’s UI and CLI
He says he likes Gemini’s user interface but found its command-line tool difficult or impractical to use during this session. This is presented as a personal, time-specific assessment rather than a systematic test.
- 3:20:24
An uncertain outlook on rising AI token costs
He speculates—explicitly framing it as a feeling—that easy access to AI tokens and services may become much more expensive in the future, and views today’s relative availability as an opportunity worth using.
- 3:22:45
The Cost of Parallel Coding Agents
Luqman argues that running many agents in parallel may make compute and token availability a limiting factor, with available resources affecting the scale of work a developer can attempt. This is presented as an expectation and opinion, not a documented test result. He also suggests separating task and token budgets and routing work across multiple models, while noting pricing and usage constraints.
- 3:28:25
Billing UI and the Pre-Submission Review Workflow
The work covers a plan name, billing configuration key, and free-tier card, while leaving design details for later review. Luqman also describes creating a debugging agent and a debugging or review milestone, followed by polishing and a dedicated pre-submission review workflow before installing the app.
- 3:30:23
Connecting an Agent Manager to Project Context
Luqman discusses directing Cursor’s agent manager using workflow context already stored in the project. He says the idea appears workable but needs further thought; the filename mentioned at the end is unclear in the captions.
- 3:31:48
A Unified Agent Activity Log
An explanation of logging micro-task steps in the Talkstore tracker, including timing, agent, task, tools, and related areas such as webhooks and billing. The aim is to preserve project context so Codex and Claude can understand each other’s work and recall earlier changes.
- 3:37:20
Reviewing App Changes and the Draft Plans Section
A move into the app to review implemented changes, including a newly visible plans section. The walkthrough makes clear that the plans interface is still a draft and the task remains unfinished, so it is not presented as a completed or tested feature.
- 3:44:31
Learning from Each Stream and Addressing Token Limits Incrementally
The speaker explains that each stream reveals new lessons and that token limits disrupt continuous work, requiring an incremental, collaborative solution.
Got a question about something in this stream?
Ask in the group