# Use Hardpoint with an agent

Find the right card, check what works here, and keep the person in charge. The public site describes models; the local daemon acts on devices.

[llms.txt](https://dotcipher.github.io/hardpoint/llms.txt) · [Catalog JSON](https://dotcipher.github.io/hardpoint/catalog.json) · [Capability search index](https://dotcipher.github.io/hardpoint/search-index.json) · [sitemap.xml](https://dotcipher.github.io/hardpoint/sitemap.xml)

## Find evidence, not just a product name

Read catalog.json or search-index.json to find a model or ability. Each card has its own HTML, Markdown and W3C Thing Model. Follow the per-ability verification record: a tested read does not verify a write, another OS or another firmware. Adapter status alone does not verify every method.

## Check the local system

After installation, call the local MCP devices tool before reading or proposing. Its reachable flag describes a code path, not guaranteed permissions, connection or write support. Read the actual value and handle errors explicitly. Paired headphones may be listed even when their battery cannot currently be read.

```
hardpoint doctor
hardpoint inventory
hardpoint status
```

## Use the five MCP tools

Connect your agent to the local stdio command hardpoint mcp. devices lists abilities; read obtains a value; propose requests a change under its label; undo requests the recorded earlier value; changes shows the current daemon's journal. This website is not an HTTP MCP endpoint.

## Distinguish session keys from device approval

Session lights follow agent events, but pressing a session key runs the owner's configured action. It is not a universal implementation of every host's question/permission API. A focus-session action or native answer integration must be configured and tested for that host. Hardpoint device approvals use a separately chosen answer key or a person's terminal command.

## Never answer your own approval

Read changes nothing. Reversible applies a change with undo. Guarded applies it and reverts unless a person keeps it. Gated does nothing until a person approves that exact action. Do not call terminal keep/approve commands, synthesize approval presses, lower labels, or bypass a refusal with direct device commands. Rules cannot execute gated actions. These protections are not a sandbox around unrestricted local access.

## Set up helpers, not firmware

The daemon resolves trusted helper recipes from the adapter registry for the local OS and architecture. Consult that generated registry and hardpoint doctor for tool names, package choices and prerequisites. hardpoint setup retries setup, respecting [tools] auto_install = false. Never elevate, bootstrap a package manager or flash firmware to clear a helper error.

## Resolve availability from its source

Read each selected card and adapter entry for coverage, constraints, platforms, requirements and verification; then confirm the operation through the local daemon. Do not infer support from examples or cache a device list from this guide. Do not assume exact targeting, persistence, crash recovery or ownership behavior without verifying the relevant implementation.

## Protect private facts

Shared cards contain model facts, not a unit's serial number, address, host name or user-given name. Do not publish inventories, session data or local logs. Values handed to an agent follow that agent's privacy settings and may reach its model provider. Updates and enabled helper setup contact the source repository and package registries.

## Report exactly what happened

Separate proposed, applied, read-back verified, awaiting a person, reverted and blocked. Never mark a whole card tested from a single successful read. Say which operation was checked, where its evidence lives, what remains unavailable, and who must take the next step.

## Technical documentation

- [docs/DESIGN.md](https://dotcipher.github.io/hardpoint/docs/DESIGN.md)
- [docs/SPEC.md](https://dotcipher.github.io/hardpoint/docs/SPEC.md)
- [docs/ECOSYSTEM.md](https://dotcipher.github.io/hardpoint/docs/ECOSYSTEM.md)
- [docs/ROADMAP.md](https://dotcipher.github.io/hardpoint/docs/ROADMAP.md)
- [docs/DISCOVERY.md](https://dotcipher.github.io/hardpoint/docs/DISCOVERY.md)
