القائمة
Nested lingtai-portal-guide reference for portal lifecycle-state interpretation, heartbeat staleness, recording, and tape reconstruction behavior.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Official-source-led manual for the TUI `claude` template.
Base URL / API-compat / provider / model / capability declaration shape versus credentials and live probes; includes proven Codex OAuth quota inspection with exact agent query routing and dated official-vs-measured context-window evidence.
Thin dual-axis router for preset questions: which of the 12 TUI-shipped built-in preset templates (provider axis), and which cross-cutting preset lifecycle mechanic (operation axis) — saving, checking availability, activating/refreshing, endpoint/capability facts, or troubleshooting. Read a child only when it is relevant; this does not describe arbitrary saved presets.
Anything you need to know about LingTai TUI. Read this first for the stable mental model, major-feature map, interface and slash-command help, or the correct source/manual route for a TUI question. It stays thin: exact command prose lives in the localized help assets, precise Go structure lives in `lingtai-tui-anatomy` plus the repository ANATOMY graph, and independent domains such as presets, Portal, tutorials, updates, and addons keep their own top-level skills.
Nested tutorial-guide reference for lessons 10–12: TUI commands, lifecycle exercises, addons, external connections, and graduation.
The 12-lesson tutorial curriculum for teaching a human how Lingtai works. Router for orientation, agent runtime, communication, memory/molt, capabilities, operations, addons, and graduation. Invoke this skill when the human is ready to begin or continue the tutorial.
| name | portal-guide-lifecycle-and-recording |
| description | Nested lingtai-portal-guide reference for portal lifecycle-state interpretation, heartbeat staleness, recording, and tape reconstruction behavior. |
| version | 1.0.0 |
| last_changed_at | 2026-07-18T00:00:00Z |
| maintenance | If you find stale or incorrect information here, use the lingtai-issue-report skill to assemble evidence and obtain per-issue human consent before filing an issue. Never include secrets, credentials, tokens, or private paths. |
This is a nested lingtai-portal-guide reference. It covers how the portal interprets agent lifecycle states and how it records/rebuilds topology history.
| State | Meaning |
|---|---|
ACTIVE | Agent is running and processing |
IDLE | Agent is running but waiting for input |
STUCK | Agent encountered an error or is unresponsive |
ASLEEP | Agent is in sleep mode (.sleep signal or explicit lifecycle transition) |
SUSPENDED | Agent process is not running (no heartbeat) |
Heartbeat is the portal's liveness ground truth. BuildNetwork() currently calls IsAlive(..., 2.0), so if an agent has a state in .agent.json but its .agent.heartbeat is older than about 2 seconds, the portal reports it as SUSPENDED regardless of the stored state.
The portal starts recording immediately on launch: a background goroutine calls BuildNetwork() every 3 seconds and appends the result as a JSONL line to topology.jsonl. This tape grows indefinitely.
On startup, if the tape needs reconstruction (missing, empty, or old format), the portal rebuilds it from replay chunks. While that runs, .lingtai/.portal/reconstruct.progress may contain a transient current/total progress string, which the /api/topology/progress endpoint parses and exposes to the browser UI.
A manual POST /api/topology/rebuild instead reconstructs from source data and rewrites the replay chunks. The topology-and-api reference documents both endpoints' exact response shapes.
