Giáo án của Quỷ Vương!

Technology / Product Overview

• Pasio (the “Demon King” name for the model given by its creator) is presented as a control plane / infrastructure for coding agents.

  • It enables users to run, manage, and orchestrate coding agents across devices (a host machine with mobile access).
  • It aims to improve the agent coding experience with features such as:
    • Low latency on handheld/mobile
    • A strong replay protocol
    • Concise, clean SDK-based code

• Mobile management

  • After installing Pasio on a host, users install a Pasio Mobile app.
  • Pair the phone with the host via:
    • a QR code, or
    • a pairing URL/link.
  • The creator emphasizes the mobile experience as a major convenience.

• Multi-provider coding agents

  • Pasio can be configured to use different providers (examples mentioned include Codex, Grok CLI, “OpenSw/OpenRouter”, and Hermies as a reference point).
  • The core goal is to support multiple providers without being locked into one, while coordinating them smoothly.

Key Workflow / Feature Analysis

Orchestration + “Task Handover” Between Agents

• Within a session/thread, agents can communicate, transfer tasks, and handoff work smoothly.
• The intended outcome is to reduce the need for manually juggling many separate agents/providers.
• The presenter argues this can reduce issues such as lag, disconnections, or distractions that may occur when switching models/providers.

Native SDK Approach vs “Hermies” Screen-State Approach

• The creator compares Pasio to Hermies, which reads agent outputs via UI/screen state.
• Pasio is framed as more “native” because it can access provider SDK responses/tool messages directly.
  • This allows more detailed customization than screen-scraping approaches.

Install / Configuration Guide Highlights (Pasio)

1. Download/install the latest Pasio (Pascal)
2. Initialize Pasio Demon during installation
3. Install the Pasio Mobile app
4. Pair mobile to the host via QR code or pairing URL
5. Add/configure providers in Pasio’s configuration
6. Use the configured providers as resources for multi-agent sessions

SLP Framework (Supervisor–Lead–Peer)

Definition

• Supervisor
  • Monitors the project/workflow and can intervene if things drift off scope.
• Lead
  • The main implementer who executes tasks and communicates results.
• Peer
  • Provides support and helps with feedback loops.
  • The presenter suggests they may rarely speak directly to the Peer, since monitoring/checking questions can distract threads.

Architecture Mapping (Inspired by Andrew Nguyen)

• The model positions agent roles as variations of peer/roles depending on scope set by the Lead.
• The Supervisor’s key responsibility is timely reminders/notifications to keep intent and scope aligned.

Rolling Monitoring + Scheduling

• Pasio is described as supporting monitoring using a scheduling tool such as HBIt / Schedule (example: checking workflows every 5 minutes).
• More advanced “correctness/incorrectness” judgments are project-specific:
  • the expected behaviors are captured and documented
  • supervisor agents can reference these documented expectations

Deployment / Implementation Concept (SLP on Pasio)

• Configure SLP inside the Pasio infrastructure using agent profiles/templates referenced in the video description.
• Example configuration flow:
  • Define an agent profile for Supervisor
  • Then define a Lead
  • Then define a Peer
• The author typically communicates most with Supervisor (for progress + explanation), then uses feedback to correct direction.
• Supervisor outputs documentation/learning artifacts so the system can improve over time and reduce human involvement.

“Codex Room” Setup / Repository-Based Generator

• The video introduces “Codex Room setup” (attributed to the “Demon King” naming).
• Purpose:
  • Generate different Codex profiles (Supervisor/Lead/Peer codex) via scripts.
  • Profiles act as runtime configuration presets loaded when Pasio initializes.

Key Technical Points

• Profiles share basic components but can have separate runtime settings, including:
  • separate DB/logging for traces/timings
  • overrides
• Uses an install/repository script to set up:
  • Codex Room environments
  • Pasio installation scripts
• Version referenced:
  • stable enough for the creator at recording time, using ~0.9.2
  • install reference difficulty around 0.8.0 was mentioned

Important Limitations / Controls

• The presenter emphasizes disabling certain default Codex multi-agent/agent configuration features when using Pasio-driven orchestration:
  • If the model spawns sub-agents using its own internal configs, it becomes harder to control which agent does which task under Pasio.
• Argument: Pasio should handle orchestration, so Codex’s multi-agent defaults may interfere with clarity/control.

Review / Discussion Style Mentions

• No formal “reviews” or ratings are provided.
• Instead, the creator offers comparative analysis, especially:
  • Pasio vs “Hermies”: deeper control via native SDK responses vs screen-state reading.
• The creator invites correction:
  • acknowledges the possibility of inaccuracies
  • suggests the Demon King may clarify misunderstandings in follow-ups

Main Speakers / Sources

• Main speaker: the video’s creator/presenter (whose Discord contact is referred to as “Demon King”)
• Named external source/article: Andrew Nguyen (referenced for an SLP/similar supervisor/lead role architecture)
• Creator/source named: “Demon King” (associated with Pasio/Codex naming and repository guidance)