Skip to main content
Vireon Dynamics
Vireon DynamicsLiminal AIJaLiminalDemosFSL-1.1-MIT · free to use

Live captures

Real prompts. Real tools. No mockups.

Screen captures of the actual Liminal harness running real turns: same approval gates and session logs as daily use. Desktop recordings show the shipped Flutter app; web captures use the browser UI with the same prompt catalog.

How these were made: npm run marketing:publish at the monorepo root (desktop capture + sync). Session JSONL is archived under assets/marketing/recordings/.

Desktop app

Real Flutter window recordings from liminal_desktop — same harness as the shipped desktop app, captured via liminald over WebSocket.

Desktop capture 01

Plan, ship, and verify code

~2.2 min · real harness run

plan → write_file → run_shell (node:test) — self-healing loop with every step visible in the harness.

Prompt

You are recording a marketing demo. Show how Liminal ships code with verification. 1) Call plan() with exactly 3 steps: implement slugify, add tests, run tests. 2) Create marketing-capture/slugify.ts exporting slugify(input: string): string — lowercase, trim, collapse whitespace to single hyphens, strip characters outside [a-z0-9-]. 3) Create marketing-capture/slugify.test.ts using node:test (import test, assert from node:test / node:assert) with 3 cases: "Hello World" → "hello-world", leading/trailing spaces, punctuation stripped. 4) Run: node --test marketing-capture/slugify.test.js marketing-capture/slugify.test.ts (use whichever path exists after you write the file). If tests fail, fix the implementation once and re-run. End with PASS/FAIL and one example slugify("Foo Bar!") result.

Tools invoked

  • activate_tool_family
  • plan
  • mkdir_p
  • write_file
  • run_shell
Liminal Desktop · Plan, ship, and verify code

Desktop capture 02

Memory that survives the session

~1 min · real harness run

remember, recall_relevant, memory_stats — typed notes with hybrid retrieval, not chat context amnesia.

Prompt

Demonstrate persistent memory (marketing capture — safe to write this note): 1) remember key "marketing:capture-policy" value "Liminal marketing videos must be recorded from real harness runs with session.jsonl proof — never fixture UI." type fact scope workspace 2) recall_relevant query "marketing session jsonl proof" k 5 3) memory_stats Reply in 3 short bullets: the stored value, the top recall_relevant hit text, and total note count from memory_stats.

Tools invoked

  • remember
  • recall_relevant
  • memory_stats
Liminal Desktop · Memory that survives the session

Desktop capture 03

Map the repo, trace the ReAct loop

~1 min · real harness run

repo_map, grep_file, read_file_chunked — orient in a monorepo and explain how tool results close the loop.

Prompt

Read-only repo archaeology for a marketing capture — do not edit any files. 1) repo_map on packages/core/src with depth 2. 2) grep_file path packages/core/src/agent.ts pattern "class AgentHarness" — note the line number of the match. 3) read_file path packages/core/src/agent.ts offset=<that line minus 5> limit=120 line_numbers true — inspect how a turn dispatches tools and consumes results. 4) In exactly 4 bullets, explain the ReAct loop as implemented here: user message → model tool calls → tool results → next model turn → turn_end.

Tools invoked

  • repo_map
  • grep_file
  • read_file
  • think
Liminal Desktop · Map the repo, trace the ReAct loop

Desktop capture 04

Research with receipts

~1 min · real harness run

web_search + web_fetch — cite primary docs with URLs and concrete API field names from the source.

Prompt

Research task for marketing footage: 1) web_search for OpenRouter prompt caching cache_control (official docs first). 2) web_fetch the best official OpenRouter documentation URL from results (not a forum post). 3) Answer in exactly 3 bullets. Each bullet must include: a full https URL you fetched, and one exact parameter or JSON field name for caching copied from that page (e.g. cache_control). Max 90 words total.

Tools invoked

  • web_search
  • web_fetch
Liminal Desktop · Research with receipts

Web UI

Browser harness runs from the same prompt catalog — useful when you want to reproduce captures without the desktop build.

Web capture 01

Plan, ship, and verify code

~1.6 min · real harness run

plan → write_file → run_shell (node:test) — self-healing loop with every step visible in the harness.

Prompt

You are recording a marketing demo. Show how Liminal ships code with verification. 1) Call plan() with exactly 3 steps: implement slugify, add tests, run tests. 2) Create marketing-capture/slugify.ts exporting slugify(input: string): string — lowercase, trim, collapse whitespace to single hyphens, strip characters outside [a-z0-9-]. 3) Create marketing-capture/slugify.test.js using node:test (import test, assert from node:test / node:assert) with 3 cases: "Hello World" → "hello-world", leading/trailing spaces, punctuation stripped. 4) Run: node --test marketing-capture/slugify.test.js (write the test as .js so node:test runs without a compile step). If tests fail, fix the implementation once and re-run. End with PASS/FAIL and one example slugify("Foo Bar!") result.

Tools invoked

  • list_dir
  • activate_tool_family
  • read_file
  • write_file
  • run_shell
Liminal Web · Plan, ship, and verify code

Web capture 02

Map the repo, trace the ReAct loop

~5.2 min · real harness run

repo_map, grep_file, read_file_chunked — orient in a monorepo and explain how tool results close the loop.

Prompt

Read-only repo archaeology for a marketing capture — do not edit any files. 1) repo_map on packages/core/src with depth 2. 2) grep_file path packages/core/src/agent.ts pattern "class AgentHarness" — note the line number of the match. 3) read_file path packages/core/src/agent.ts offset=<that line minus 5> limit=120 line_numbers true — inspect how a turn dispatches tools and consumes results. 4) In exactly 4 bullets, explain the ReAct loop as implemented here: user message → model tool calls → tool results → next model turn → turn_end.

Tools invoked

  • grep_file
  • list_dir
  • read_file
Liminal Web · Map the repo, trace the ReAct loop

Web capture 03

Research with receipts

~2.2 min · real harness run

web_search + web_fetch — cite primary docs with URLs and concrete API field names from the source.

Prompt

Research task for marketing footage: 1) web_search for OpenRouter prompt caching cache_control (official docs first). 2) web_fetch the best official OpenRouter documentation URL from results (not a forum post). 3) Answer in exactly 3 bullets. Each bullet must include: a full https URL you fetched, and one exact parameter or JSON field name for caching copied from that page (e.g. cache_control). Max 90 words total.

Tools invoked

  • web_search
  • web_fetch
  • read_file
Liminal Web · Research with receipts

Web capture 04

Memory that survives the session

~48s · real harness run

remember, recall_relevant, memory_stats — typed notes with hybrid retrieval, not chat context amnesia.

Prompt

Demonstrate persistent memory (marketing capture — safe to write this note): 1) remember key "marketing:capture-policy" value "Liminal marketing videos must be recorded from real harness runs with session.jsonl proof — never fixture UI." type fact scope workspace 2) recall_relevant query "marketing session jsonl proof" k 5 3) memory_stats Reply in 3 short bullets: the stored value, the top recall_relevant hit text, and total note count from memory_stats.

Tools invoked

  • activate_tool_family
  • git_status
  • git_diff
Liminal Web · Memory that survives the session

Overview reels

Animated overviews

Short produced reels that summarize the harness: distinct from the real screen captures above.

Hero~20s · brand intro + install
Capabilities~22s · tools, memory, agents
Transparency~24s · visible tool trace

Watch the full 2-minute reel on the home page →

Ready to run Liminal AI on your machine?

Install free