ACAgentic Craft

Part 3 of 8 · Design a Production Agent Runtime

Advanced~15 minHazelJS

Runtime Core: Execute, Tools, Timelines

AgentRuntime.execute via chat APIs, real tools against the demo store, Inspector timelines, and eval smoke.

Authors
editorial-team
Published
Last reviewed

You will leave with

  • Call support chat and see a real tool name
  • Open Inspector and correlate executionId
  • Know when DemoLLM vs OpenAI matters
On this page

Runtime core (F1, F2, F15, F16)

Agents as backend jobs (F1)

Product entrypoints call AgentRuntime.execute — see src/chat/chat.service.ts — not a free-floating chatbot process.

Lab — track an order (F1–F2)

bash
curl -s localhost:3060/api/support/chat \
  -H 'content-type: application/json' \
  -d '{"message":"Where is my package for ORD-1001?"}' | jq .

Expect a real lookupOrder / tracking path against the in-memory commerce store.

DemoLLM vs OpenAI

  • Empty OPENAI_API_KEY → DemoLLM (fine for wiring labs)
  • Set a key when you want realistic tool selection

Inspector + timeline (F15)

Open http://localhost:3060/__hazel. Correlate executionId with .hazel/timeline.jsonl (or configured timeline file). Lesson: /learn/agentic-development/observability-signals-for-agent-decisions.

Eval smoke (F16)

Meridian runs Jest / agent tests in-repo. Craft path: /learn/agentic-development/golden-tests-with-describe-agent and /guides/build-an-evaluation-harness.

Checkpoint C

Timeline (or response metadata) shows a real tool name from support-desk — not a CLI stub.

Artifact: Checkpoint C: timeline shows real tool, not a stub

Sources

  • Meridian Ops READMEhazeljs-meridian-ops/README.md — mental model + quick start
  • Meridian TOUR.mdF1–F22 curl walkthrough
  • Flagship project plan (21)docs/agent-os/21-flagship-project-plan.md
  • HazelJS Agent OS guide
  • HazelJS Agent package

Continue