Frequently asked questions
What happens when an agent gets stuck or asks a question?
Section titled “What happens when an agent gets stuck or asks a question?”The session moves to awaiting-input and surfaces in your Inbox and on Today. Open the session, answer in the HITL console, and the agent resumes from where it paused — the full exchange is kept in the session transcript for traceability.
How do enclaves keep credentials from leaking?
Section titled “How do enclaves keep credentials from leaking?”Every project belongs to an enclave fixed at creation. AI accounts, Git tokens, and nodes are scoped to that boundary, so a public-repo agent can never reach corporate credentials. Enclave membership is enforced at dispatch time, not just in the UI.
Can I run agents on my own hardware?
Section titled “Can I run agents on my own hardware?”Yes — install the Halyard daemon on any machine and register it as a node. It heartbeats to the controller and advertises its capacity; sessions are scheduled onto nodes within the matching enclave. Manage them under Nodes.
How does a task trace back to its requirement?
Section titled “How does a task trace back to its requirement?”Halyard maintains the lineage PRD → requirement → issue → task → session → PR. The Coverage matrix shows it at a glance, and every session and review surfaces the chain. Nothing ships without a line back to why it exists.
Is the AI review draft posted automatically?
Section titled “Is the AI review draft posted automatically?”No. The draft is generated for you to read and edit; you copy it into your provider’s review or post it yourself. You stay the human in the loop for every approval.