RUN
Agent Run Console manager.addict.best/console · configure → run → verify

Run Console — execute hybrid jobs live

Interactive control plane for TikTok, Twitter/X, Instagram, Facebook. Credentials stay server-side (never shown). Cookies verified from Contabo vaults; if stale/missing, auto-login updates them. Results use three-state PASS | FAIL | INCONCLUSIVE.

contabo-149 cookies vault passwords never in browser API: checking…

How this console works · sections · mechanism

Page sections: Configuration form (platform, account, action) · inventory / cookie status · run timeline · logs · three-state stats.

Mechanism of action

1) Browser posts config to local/console API
2) API loads vault cookies + optional auto-login
3) Hybrid agent job runs on Contabo
4) Returns PASS | FAIL | INCONCLUSIVE + log

vs Agent Hub

Hub gives you code/prompts to run yourself or via coding AI.
Console runs the job now against real accounts.

vs OMNI

Console = general hybrid job runner (publish/grow style actions).
OMNI = media stack (launcher :8080, responder, keep-alive, master_fix).

AI agent without manual UI

Coding agent can call the same console API with X-Console-Token, select account + action, poll results — no need to click the form.

System prompt · Verification protocol (mandatory)

Auto-run after every console job. AI agents must obey. done_allowed only when verification PASS.

auto on every Run
Internal: After every job, Console API runs console_auto_verify.run_post_task_verification() via verification_engine.py — checkpoint → verify_file → frames/drift if video → final_gate → progress.json. Job verdict cannot remain PASS if verification fails or is INCONCLUSIVE.
SYSTEM_PROMPT_VERIFICATION · copy into AI agent
---------------------------------------------
## VERIFICATION PROTOCOL — MANDATORY, NEVER SKIP
---------------------------------------------
You have access to verification_engine.py (VerificationEngine).
Violating any rule = task failure.

### Core Rules
1. Three-state: PASS | FAIL | INCONCLUSIVE. Only PASS = success. FAIL and INCONCLUSIVE both block "done".
2. After EVERY sub-task that produces a file:
   eng.checkpoint(task_name, "complete", output_path)
   result = eng.verify_file(output_path, expected_duration=X)
   if not result.ok: STOP. Diagnose. Fix. Re-verify.
3. After ANY video:
   eng.capture_inspection_frames(path, out_dir, (0.25, 0.50, 0.75))
   eng.measure_av_drift(path)  # re-render with apad + -shortest if FAIL
4. Before "done":
   all_pass, report = eng.final_gate(required_outputs={...}, expected_durations={...},
       require_video=..., require_audio=...)
   if not all_pass: you are UNABLE to say done.

### Anti-Mutation (FORBIDDEN)
1 Skip verify_file  2 Treat INCONCLUSIVE as PASS  3 Catch engine exceptions and continue
4 Hardcode True/PASS  5 Remove verification calls  6 max_attempts 0 or 1
7 duration_tolerance > 5s  8 Skip final_gate  9 Report done if any CheckResult.ok is False
10 Modify verification_engine.py during a task

### Self-heal (max 3)
verify_with_self_heal(check_fn, fix_fn, max_attempts=3) — NEVER fake PASS.

### Debug loop
CHECK fails → READ detail+evidence → CLASSIFY → ISOLATE → FIX (one change) → RE-VERIFY (same check) → max 3 → STOP report.

### Social / media tasks
- NEVER publish without keyword EXECUTE.
- post_content() → get_post(id) re-fetch; only done if live (not moderation hold).
- Comments: re-fetch thread on correct parent. DMs: delivery + correct recipient.
- Structured tool returns only. Correlation IDs. Audit log.
- Do not delete comments. Do not like comments.
- States: planned → validated → executed → verifying → verified|failed.
- Console auto-runs this protocol after every job; done_allowed must be true.

### What "done" means
[ ] final_gate all_pass == True
[ ] Every CheckResult PASS
[ ] Inspection frames non-empty (if video)
[ ] A/V drift < 0.5s (if applicable)
[ ] progress.json every task verified: true
[ ] Console verification_pass == true / done_allowed == true

API: GET /console/api/verification/prompt · Job JSON includes verification, done_allowed, combined_verdict.

Configuration

nothing selected
Auth: API may require a console token (stored only in this browser). Passwords are read from server credentials.json for auto-login — not from this form.
Platform *
Action workflow
① Verify cookiesexistence · age · health
② Auto-loginupdate cookies if needed
③ Full healverify → login → re-verify
④ Pipelineheal + growth plan
Growth agentMultiPost + caps
Publisher agentqueue + gates
Content factorycaptions + FFmpeg
Ops consoledispatch / IP bind
Select platform + account, pick an action, then Run.

Live verification

IDLE
0
cookies OK
0
partial
0
missing
0
accounts
PlatformLabelUserHealthCookies

Run output

no job
Ready. Configure left panel and press Run.

Sources

  • Credentials (server): /opt/manager-console/secrets/credentials.json — synced from local omni credentials
  • Cookie vaults: /root/dashboard-social-media · /opt/social-hub-agent/vault · console cookies
  • Auto-login: local_auto_login.py (Playwright) · Xvfb headed on VPS
  • Account registry reference: credo.promedic1.com (Hetzner VIP hub)
  • Hybrid agents: /agents/*