FAQ
FAQ
Do I need to provide IDs for every event?
Sequential thinking: Optional, backend can generate, but still recommended to provide
Parallel thinking: Required, backend cannot generate correct IDs for parallel thinking
Activities: Optional, but recommended for tracking
What happens if I don’t provide a message for activities?
Backend will auto-generate a message:
With types field available: Type-specific message
Not provide any types: Markdown-formatted list of fields
Can I emit thinking events without start/end markers?
No, you must follow the sequence: thinking_start → thinking → thinking_end
Can I reuse the same ID for different thinking streams?
Yes, but only if streams are sequential (one finishes before next starts). For parallel streams, use different IDs.
How do I know if my events are being processed correctly?
Check the database messages.metadata_["events"] field after pipeline completes. Events should be stored with proper structure and merged thinking streams.
Last updated