---
title: "What the temple controls will control"
description: "SPECS 01 lists buttons and touch controls on both temples."
slug: "temple-controls"
category: "hardware"
language: en
editorial_status: published
capability_status: development
reviewed_at: 2026-10-13
keywords: ["SPECS 01 temple touch","wearable controls","glasses voice shortcut"]
---

# What the temple controls will control

SPECS 01 lists buttons and touch controls on both temples. CueSpec’s recording and conversation-control mapping is still being integrated, so a specific tap or press is not yet a guaranteed app action.

## Planned interaction scope
The intended workflow includes starting or stopping spoken input and moving between conversations from the wearable. Deleting recently spoken text is an earlier product idea that needs its own behavior definition and acceptance.

The interaction needs to distinguish recording, editing and sending. A convenient gesture should not accidentally send a half-finished request or apply to the wrong conversation. It also needs visible feedback so you can tell whether a gesture was received.

## Current alternative
Use the released Mac recording route and review the resulting draft. Fn hold/release has documented real-user acceptance, while the reply-field hold-to-record route is described in release material. Neither establishes glasses gesture equivalence.

A finished wearable guide should specify the exact gesture, applicable context, feedback, cancellation and recovery behavior. Until that mapping is published and tested, do not infer that a touch can delete text, change a model or send instructions automatically.

## Related reading

- [SPECS 01 integration: the complete route to validate](/glasses-integration-roadmap/)
- [Wearable text deletion and conversation controls](/wearable-edit-controls/)
- [Bluetooth connection is not the whole AI input path](/bluetooth-input-path/)
- [SPECS 01 hardware specification reference](/specs-01-specification/)