Capture One Observation
This is an expansion path, not the main quickstart lane. Use it after you already have a working daemon. The capture runtime is host-local and lives in the siblingkheish-capture repository.
If the daemon is not already working, start with Run Kheish first.
What you need first
- one running
kheish-daemon - Rust and Cargo
- the sibling
kheish-capturerepository cloned locally
../kheish-capture.
This quickstart uses one deterministic fixture source, not live microphone capture. That keeps the first success independent of OS media permissions or device setup.
All commands below are meant to be run from the kheish-daemon repository root so that the daemon CLI and the sibling capture repo paths stay consistent.
1. Create one minimal capture config
From thekheish-daemon repository root, create a one-source config in the sibling kheish-capture repository:
replace-me-screen-upload-token with one strong token string before you run the next steps.
If your daemon requires bearer auth, also uncomment admin_bearer_token and set it to one valid control-plane token. That is required for doctor and sources apply, because both operations hit admin daemon endpoints.
You do not need to pre-create the daemon observation source for this quickstart. sources apply will create or rotate it remotely because remote.ensure_exists = true.
2. Validate the local config and daemon reachability
doctor verifies:
- the config parses
- the fixture source can be instantiated
- the spool can be opened
- the daemon is reachable
3. Ensure the remote observation source exists
screen-fixture-quickstart.
4. Run one one-shot capture
5. Verify the observation from the daemon
If your daemon requires bearer auth and you are using the host-built CLI, export one control-plane token first:What this quickstart proves
You are proving that:- the host-local capture runtime can reach the daemon
- one local source can provision its remote observation source
- one real media artifact can be uploaded into daemon-owned observation storage
Important scope note
This path is intentionally conservative:- it uses one fixture image
- it does not require live microphone, screen, or webcam permissions
- it does not require Docker
kheish-capture, but it is a later step. Screen and webcam fixture ingestion are the current deterministic bring-up path in this repository layout.
Next steps
Once the first observation exists, continue with:- Capture and observations for the model
- Observations and derivations API for source management, upload, and materialization
- Tasks and schedules if you want automated follow-up work after materialization
