5f98df530c
Ship weknora-shared and weknora-rag-search Agent Skills (SKILL.md plus references) so an agent driving the CLI learns the auth flow, output contract, exit codes, and the chat vs session-ask vs search distinction without scraping help text. Add CI drift guards that keep the skills honest: every ```weknora``` block must reference a live command/flag (skillparity), and every MCP tool named in a skill must exist in the registry (skill_tool_parity).
2.2 KiB
2.2 KiB
chat and session ask — streaming RAG
Both stream an NDJSON event log (one JSON object per line) by default. They share
the same event vocabulary; chat does plain KB RAG, session ask invokes a
custom agent.
Commands & flags
weknora chat "<query>" --kb <name-or-id> [--session <id>]
weknora session ask "<query>" --agent <agent-id> [--session <id>]
--kb(chat) is required name-or-id.--agent(session ask) is required.--session <id>continues an existing conversation; omit to start a new one.--format textrenders a human transcript instead of NDJSON;--format json/--format ndjsonboth produce the NDJSON stream (identical here).
Event stream
The CLI emits an init line first, then passes SDK events through verbatim:
{"event":"init","session_id":"sess_abc","message_id":"msg_xyz","profile":"prod"}
{"response_type":"thinking","content":"…"}
{"response_type":"tool_call","tool_calls":[…]} // agent only
{"response_type":"tool_result","content":"…"} // agent only
{"response_type":"references","knowledge_references":[…]}
{"response_type":"answer","content":"partial text…"} // streamed in pieces
{"response_type":"complete","done":true}
- Accumulate
response_type:"answer"contentpieces for the final answer. knowledge_referencescarry the grounding chunks (source attribution).- Keep
init.session_idandinit.message_id:session_idcontinues the chat (--session);message_idis needed tosession stoporsession continue-streamthat specific message. - On failure mid-stream you get
response_type:"error"; a transport/HTTP error surfaces as the normal error envelope on stderr with a typed code.
Recovery
- Stop server-side generation:
weknora session stop <session-id> --message <message-id>. Ctrl-C only closes your local connection — the server keeps generating (and billing) until told to stop. - Re-attach after a dropped connection:
weknora session continue-stream <session-id> --message <message-id>. The server replays the event log from index 0 then tails new events, so dedupe by message_id if you already consumed some events. Buffer TTL is ~1h (redis) or process-lifetime (memory).