Home

Field SOP

Scenario-based tutorials with real screenshots, prompts, workflow templates and pitfalls.

Put an agent on your phone: two routes, one red line

A hands-on SOP for putting a phone AI agent onto real hardware, offering two routes side by side. The first section decides whether it is worth doing at all: it fits a spare handset used to test whether a phone can genuinely run errands, and it does not fit a daily driver, an unattended long task, or anything involving payment, password changes, sending messages or account settings. Route A is OmniBot's on-device app form: install the APK from Releases, then configure AI capability, provider and scene models in settings, where Memory embedding strictly needs an embedding model and other scenes are best served by multimodal or vision models; the Alpine environment initializes on startup; sending a skills repository link to the assistant installs skills; scheduled tasks run subagent flows while alarms only remind; an optional Remote Codex bridge lets the phone scan a code to borrow a computer's Codex; and an optional WebUI takes an address and token from the in-app local service, defaulting to port 8899 with no trailing path. Development requires Flutter 3.47.2+, JDK 17+, Node.js 20.19+ or 22.12+ and pnpm 10.28.0. Route B is OpenGUI's framework form reached through DeepSeek Harness: the hard prerequisites are an Android 11 (API 30) or newer device or emulator plus USB debugging and accessibility permission; the shortest path is pasting the official install prompt to Codex, after which the installer verifies SHA-256, installs only the OpenGUI plugin and preserves unrelated plugins and settings; version discipline supports DSH 0.1.0-rc.7, 0.1.0-rc.8, 0.1.1-rc.1 and 0.1.1-rc.2 with new installs defaulting to 0.1.1-rc.2, does not support 0.1.2-alpha.4, and refuses a downgrade from a 0.1.1 RC to a 0.1.0 RC. Once a real device is connected, a single prompt verifies the setup. The safety section covers a spare device, least privilege, a hard rule of per-action human confirmation, trusted LAN only, tokens that never leave the machine, retained logs for audit, and short tasks before long ones, backed by a pre-flight checklist and a seven-row pitfall table. Licence boundaries get their own section: OmniBot requires a commercial licence for commercial use since AGPL v3 covers only non-commercial and personal, educational or research use, while OpenGUI is BSL 1.1 for non-production use only. The article also notes it does not overlap with the site's desktop computer-use build SOP, and invents no pricing or limits absent from the official docs, writing instead that the vendor governs.

No app switching: JianYing Hub from storyboard to final cut

A hands-on SOP for JianYing Hub that starts with a fitness check, giving three cases where it fits (you need a full asset-to-final-cut chain, you want batches of the same storyboard for A/B tests, or you dislike repeated export and import across apps) and four where it does not (you only lack one generated shot, you need fine multi-cam editing, your assets and data must stay local, or your budget must be precisely predictable), and noting that if data-on-premises or avoiding ecosystem lock-in is the priority you should look at an open-source route instead. It then walks the official 14-step onboarding path all the way to multi-track refinement: confirm the entry and asset source (keeping the same JianYing account so Jimeng and Xiaoyunque assets import in one click), generate key assets and a storyboard script, wire assets to script, let asset management auto-complete characters, props and scenes, batch-generate storyboard prompts (with two copy-ready prompt templates, one for product ads and one for talking-head video), pick models such as Seedance 2.5 to generate each storyboard clip, preview the assembled cut, use "More Editing" to jump straight into JianYing's multi-track timeline, apply local edits, AI extend, and AI post-editing (upscaling, frame interpolation, color grading, removal, vocal separation), call Skills through the JianYing Assistant in text, and import ByteDance assets back in. It adds three batch-production methods (deriving multiple versions from one product for A/B, a talking-head batch pipeline, and size and platform adaptation), a line-by-line pre-launch checklist and a six-row pitfall table covering script drift, local edits breaking consistency, audio-video desync after AI extend, human review of proper nouns in subtitle fixes, version and font mismatches after import, and rigid pacing from over-reliance on auto-assembly. Pricing, free quota, concurrency, credits, regional availability and duration or resolution limits are all unpublished and stated as following the official app, and JianYing Hub is noted as a closed-source commercial product that is neither open source nor free.

Same voice, 2.3s lag: ship Qwen3.8 live-translate in your app

A deployment SOP for Qwen3.8-LiveTranslate that starts with a fitness check: if you need a conversation to be understood as it happens, use simultaneous interpretation, and if you can translate slowly afterwards, start with offline. It then pins down the two most commonly misused figures, that 2.3 seconds is average lag (LAAL) rather than end-to-end first-packet latency, and that 60 is recognition input while 29 is speech output, two different units with the remaining 31 text-only. Credentials and environment come next: keys belong only in environment variables, never in source, repositories or front-end bundles, since committing one puts it into version history and the shipped bundle, and the only correct response to a leak is to revoke the old key immediately and rebuild and rotate it. It also warns up front about the trap that a browser cannot set an Authorization header during a WebSocket handshake, so the front end must never connect directly and the correct shape is a server holding the secret. The article then walks through a minimal streaming loop and an event-driven WebSocket skeleton, opening a long connection, receiving session.created, pushing audio and draining events, covering speaker diarization with voice reproduction, same-frame bilingual output and long-context disambiguation, and closes with concurrency limits, cost accounting, observability, failure fallbacks and a pre-launch checklist. Pricing, rate limits, concurrency and regional availability that are not public are all marked as following the Qwen AI platform and Alibaba Cloud Bailian documentation rather than invented.

One Sentence to a Live App With a Database: Qoder Sites SOP

A hands-on SOP for building and shipping with Qoder Sites from a single sentence: version checks (desktop v0.3.3 or newer, CLI v1.1.54 or newer) and the /sites entry, a five-part prompt template (goal, data model, interaction, style, deploy now) with two copy-ready build prompts, first publish covering preview, sharing and permissions, three post-publish permission checks, three persistence checks for the auto-provisioned database plus a checklist form, then binding Cloud Agents in one sentence to give the page agent ability (including when to bind and when not to). It closes with three landing scenarios (prototypes, dashboards, campaign pages), four boundaries to avoid, and a four-pitfall quick check. Database type, capacity, billing and regional rules that are not public are all marked as following the client interface and official announcements rather than invented.

Qwen3.8-Omni-Flash API SOP: Three Multimodal Workflows

A hands-on SOP for the Qwen3.8-Omni-Flash API: activating Alibaba Cloud Bailian and getting a DashScope API key (Beijing and Singapore endpoints keep separate keys), preparing an openai-SDK compatible environment, then three scenarios step by step, one-hour meeting audio-video to minutes and action items, Video2Note turning hours of video into timestamped illustrated notes, and controlled Caption asking on demand (prompt templates that specify target, time range, granularity and format), plus cost control (flat omni-modal 0.8 CNY per million input tokens, agentic coarse-to-fine evidence saving about 45.7% tokens, segmentation and on-demand questioning) and a pitfall table (media only in user messages, SDK version floors, duration and file limits per console). Five sample code blocks; unverified details are marked as per official docs.

Qoder Free Credits Claim and Usage Management SOP

A hands-on SOP for claiming and managing Qoder's double promo: download and install (international qoder.com or China qoder.cn, across desktop, mobile, IDE, JetBrains plugin and CLI), sign up (the two editions keep separate accounts and quotas), confirm the free window works (selecting Qwen3.8-Flash in the model picker bills at a 0x coefficient, nothing to claim), then the daily 100 Credits rhythm (opens 10:00 daily, one claim per cycle, no carryover of missed days, each grant valid 30 days and stackable), usage management (check burn in the usage panel, let Qwen3.8-Flash carry routine work and save Credits for hard tasks), deduction rules (earliest-expiring credits are consumed first, in-plan before add-on packs on the same day), and a closing plan for when the window ends on September 30. UI details follow the actual client.

Octop Self-Hosted AI Assistant Deployment SOP

A hands-on SOP for deploying Octop: it starts with a decision framework on whether to self-host at all, then walks four install paths (one-line script, Windows PowerShell, Docker Compose, and the Tencent Cloud Lighthouse or CVM official image marketplace), runs octop init and octop run verbatim from the official README (default port 8088), changes default credentials on first login (the README hardcodes none, third-party reviews report admin/octop, and Docker init generates a random one), then configures models (OpenAI-compatible, Ollama, nearly 20 providers), experts with MBTI personas, connectors (Tencent Docs, OAuth, MCP) and IM channels, and closes with Docker Compose and PostgreSQL productionization plus a six-item pitfall table and a ten-item pre-launch checklist.

Intern-S2 in practice: from free API to scientific workflows

A hands-on SOP for accessing Intern-S2: for individuals and small teams the realistic path is the free API (chat.intern-ai.org.cn for online use, internlm.intern-ai.org.cn/api/strategy for quota), while institutions with compute can run the HuggingFace weights at internlm/Intern-S2-397B. It gives a three-way access comparison table, a minimal runnable Python call for the free API, an HF inference skeleton, two copy-paste prompt templates for scientific long-horizon tasks (molecule binder design, materials structure generation), plus Memory Decoder mounting notes and a ten-item pitfall list (free-tier rate limits, 397B out-of-memory, long-context truncation, the Preview model's 2026-10-31 shutdown and migration). Bottom line: start free on the API, do not jump straight to self-hosting a 397B model.

Wiring diagram-design into Claude Code: a hands-on SOP

A hands-on SOP for wiring the diagram-design diagram skill pack into a daily coding workflow, with commands taken verbatim from the project's official README. It runs in seven steps: first what the pack does and does not solve; then a per-host install and update command table (Claude Code's /plugin marketplace add and /plugin install, Codex's codex plugin marketplace add and plugin add, the copilot plugin family for GitHub Copilot, the droid plugin family with --scope user for Factory Droid, pi install plus /reload for Pi, a subdirectory URL import for Kiro, and a directory copy or symlink for OpenCode); then the first-run gate, which stops to ask when the default skin is untouched, and brand onboarding, which reads your site for palette and fonts, maps them to semantic tokens, checks WCAG AA contrast and emits a fidelity receipt; then drawing and self-check, with three copy-paste natural language prompts, the official six criteria for it working, and self_check.py printing OK as the pass condition; then export and import, covering the four dials, the diagram-only boundary, and what a fidelity ledger looks like; and multi-client brand isolation via named profiles plus a .diagram-design marker file. The seventh section is a ten-item pitfall table with symptom and cause for each: Claude Code disables auto-update by default for third-party marketplaces, Factory Droid tracks plugins by commit rather than manifest version, Pi has no auto refresh and needs pi update --extensions, Kiro copies rather than links, OpenCode copied installs never self-update, a legacy standalone npx skills add copy will not follow the Codex marketplace, a customized style-guide.md can be overwritten by package updates, the first PNG export fails without Playwright and Chromium, readers assume exports include the full layout, and motion HTML screenshots capture an intermediate frame. The core claim: the real barrier is not installation but update paths and output boundaries, and the fact that the official README spells out update commands per host is itself the signal that cross-host skill distribution and upgrades still have no unified answer.

LingBot-World 2.0 Local Small Model Deployment SOP

A hands-on SOP for running LingBot-World 2.0's 1.3B causal-fast locally: environment and dependencies (torch 2.4.0 or newer, flash-attn and the rest, commands taken verbatim from the official requirements.txt), then weights download (the 1.3B package ships DiT weights only, while T5, VAE and the tokenizer are shared with 14B, so you must point assets_dir at a 14B directory or it will not start), then a first successful clip (torchrun or the official run_fast.sh), then parameter tuning (frame_num must be 4n+1, local_attn_size 18, sink_size 6, chunk_size, base_seed, save_dir), and finally production and deployment paths (the official team releases no deployment code, so reference the SGLang cookbook or NVIDIA flashdreams), closing with eight pitfalls and a ten-item launch checklist. Key pitfalls: the hardware bar has three conflicting versions (README 1.3B example uses 4 GPUs, run_fast.sh reference says 2, media claim consumer single-card real time), so trust the repo, treat 2 GPUs as the reproducible floor, and mark single-card real time unconfirmed; ulysses_size must divide the attention head count (12 for 1.3B, 40 for 14B) and equal nproc_per_node; choose between causal_fast (4 steps per chunk, no CFG) and causal_pretrain (40 steps per chunk, with CFG); and the CC BY-NC-SA 4.0 license is non-commercial, so confirm authorization before any productization.