section · guides
Inspect running agents
Capture session feedback and trace which specialists ran for a task.
construct reflect captures a session insight or learning and writes it to your knowledge base. Use it after any session where you discovered something worth preserving.
Basic usage
construct reflect --summary="Jira webhook auth requires HMAC-SHA256, not HMAC-SHA1"
This writes a timestamped markdown file to .construct/knowledge/internal/ and records an observation in the observation store.
Specify a target subdirectory
# Internal knowledge (default)
construct reflect --target=internal --summary="..."
# Decisions
construct reflect --target=decisions --summary="Chose Postgres over SQLite for multi-user support"
# How-to guides
construct reflect --target=how-tos --summary="Steps to reset a stale sync lock"
# External signals (customer feedback, market notes)
construct reflect --target=external --summary="Customer asked for Linear integration"
# Reference material
construct reflect --target=reference --summary="Embed authority boundary definitions"
Both shorthand (internal) and full form (knowledge/internal) are accepted.
Add detail
construct reflect \
--target=decisions \
--summary="Chose typed .construct/knowledge/ layout over flat product-intel/" \
--content="Reasoning: typed subdirs enable automated routing, cleaner MCP tool descriptions, and future ACL per type. Migration: no backward compat needed (pre-launch)."
What gets written
-
A timestamped markdown file in the target subdirectory:
~/.cx/knowledge/internal/reflect-2026-04-29T14-32-00.md -
An observation in the observation store with:
category:insightrole:constructsummary: your--summarytexttags:['reflect', '\<target>']
View recent reflections
construct knowledge index
Or search:
construct ask "what did we learn about Jira?"