Skip to content
شغّال
Back to the library

Chill Build: Automation & Traffic

Stream 716:14:10

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 building a controllable automation system that organizes AI agents as a graph and turns research into content, short clips, and multi-platform posts, supported by a calendar, analytics, reports, and Telegram-based coordination. Practical work included checking the publishing pipeline, correcting topic relevance, refining tone and calls to action, and dividing reasoning tasks from deterministic local scripts. Luqman repeatedly emphasized that quality, measurement, and human review should precede scaling or unattended operation. In his view, the larger challenge is no longer software construction alone but acquiring and measuring traffic through tools such as Search Console and Google Analytics, then improving the product and pricing once enough evidence exists. Audience questions covered coding tools and plans, Codex versus Claude, learning through Micro-SaaS, agent tools, e-commerce platforms, SEO, editing, and AI video generation. Other discussions covered opinions on AI safety and the software industry’s future, beginner and freelancing advice, creator-platform monetization, payment-platform choices, the risk of exposed API keys, and the ethics of AI-altered product images. Claims about unidentified models, agent security, usage limits, and tool costs were treated cautiously rather than as established facts. The automation, publishing, and traffic outcomes remained unresolved: some tests and refinements looked promising, but several workflows stalled or were still being configured, and there was not yet enough performance data to call the system successful.

  • AI tools
  • hallucination claims
  • model architecture
  • evaluation
  • +4

131 moments from the stream

  1. 5:44:00

    Monetization Varies by Platform and Season

    One participant said Facebook had performed well for monetizing this type of content and that results varied by season, while local TikTok monetization options were limited in his experience.

    • Facebook
    • TikTok
    • seasonality
    • creator monetization
  2. 5:44:12

    Measuring Organic Traffic Beyond Search Console

    The discussion recommended using Google Analytics 4 alongside Search Console to measure organic traffic more accurately, and also identified programmatic SEO as an important topic for further research.

    • SEO
    • Google Analytics 4
    • Google Search Console
    • organic traffic
    • +1
  3. 5:47:05

    Designing Voice Interaction That Matches the User’s Language

    An experiment with an interaction that accepts Arabic or English voice messages and replies in the same language, including a preference for immediate voice-only responses when voice is used. The model or product identity is unclear in the captions, so the project is left unnamed.

    • voice interaction
    • multilingual UX
    • Arabic
    • English
    • +1
  4. 5:51:44

    Command Center vs. Graph Engineering for Agents

    The discussion describes Command Center as organized around continuously running agents and structuring work with a Kanban board and swimlanes, while the newer graph-based approach lets agents interact to pursue a shared goal such as traffic acquisition. In the speaker’s view, the two differ in architecture and purpose and should not be treated as direct substitutes.

    • agent orchestration
    • graph engineering
    • multi-agent systems
    • Kanban
    • +2
  5. 5:56:15

    Moving Agents from Code Auditing to Marketing

    The speaker explains that a group of agents had been used to review code coherence and cleanliness on large tasks, but was later reassigned to focus on marketing rather than coding.

    • AI agents
    • code audit
    • marketing
    • وكلاء الذكاء الاصطناعي
    • +2
  6. 5:58:22

    Manually Testing the Automation Flow End to End

    The speaker proposes triggering the workflow manually once and asks for a walkthrough from activation through production and posting before resuming its regular schedule.

    • automation
    • end-to-end testing
    • manual trigger
    • scheduling
    • +3
  7. 5:59:12

    A Conditional Plan to Open-Source the Automation Tool

    Responding to an audience request, the speaker says he may polish the tool and publish it on GitHub because it could be adapted to several uses, but only after activating it and confirming that it produces results; he does not claim it has already been released.

    • open source
    • automation
    • GitHub
    • conditional release
    • +2
  8. 6:00:18

    Building a Competitive Start on Upwork

    The discussion recommends assessing poor results by looking at the trial period, niche, and what specifically failed. It recommends building a portfolio, being patient, studying competitors’ rates, starting slightly below the market to win initial clients, and raising rates as experience and the portfolio grow.

    • freelancing
    • Upwork
    • portfolio
    • pricing
    • +4
  9. 6:04:04

    Designing a Brief Voice Update with Personality

    The speaker criticizes a voice message that literally recites the time and date, asking instead for a short, personable brief that delivers the important information without an unnecessarily long daily update.

    • voice interface
    • briefing
    • UX writing
    • AI personality
    • +3
  10. 6:10:30

    Accessing the Automation System Through Telegram and Its Runtime Constraint

    The speaker summarizes an unexpected outcome of the experiment: he can communicate with the automation system by voice and reach the agents through Telegram. He notes that the current limitation is having to keep his computer running and prevent it from sleeping.

    • Telegram
    • automation
    • remote access
    • voice control
    • +4
  11. 6:13:47

    Observing Automated Posting After the Build Phase

    The speaker says he is eager to test the system over the following days, when it is expected to create posts automatically, and views that period as the point when the prior build work will begin to show its effect; no outcome had yet been demonstrated.

    • automated posting
    • monitoring
    • automation test
    • content workflow
    • +3

Got a question about something in this stream?

Ask in the group
Chill Build: Automation & Traffic · شغّال