Connect your Nomi to Chaster with confidence.

KeyLink is a bridge, not a new companion and not a second lock platform. Your selected Nomi supplies the personality and decision. KeyLink supplies authenticated context, interpretation, permission checks, replay protection, execution, and an audit trail. Chaster remains the authority for the lock.

PersonalityYour Nomi

Checks and bridgeKeyLink

Lock authorityChaster

The supported decision path

1. Join the KeyLink Community.
2. Open #apply-for-testing and run /apply.
3. Complete the private form with your exact Chaster username and the requested testing details.
4. Wait for an administrator to approve the application and add the username to Chaster’s KeyLink tester list.
5. Use the community bot or KeyLink extension to check the application status.

1. Create or sign in to your Nomi account.
2. Choose the companion whose established personality, memories, and relationship dynamic should inform lock decisions.
3. In Nomi, open Profile → Integration and create or copy your API key.
4. Keep the key private. Do not post it in Discord, screenshots, a Mind Map, or a support ticket.
5. Talk with the Nomi in ordinary chat about expectations, limits, tone, and how much initiative you want it to take.

1. In Chaster, create a short self-lock for the first test.
2. Choose Add more extensions, find KeyLink, and add it to the lock.
3. Open the KeyLink configuration panel embedded by Chaster.
4. Review every permission and schedule setting before accepting the lock contract.

Guarded settings

• Allow or deny adding time, removing time, freezing, unfreezing, timer visibility changes, and supported tasks.
• Set the maximum time the Nomi may add in one action and the cumulative daily add limit where shown.
• Review the final list again in the running extension because actual availability can change with the lock state and installed Chaster features.

Scheduled follow-ups

• Starting cadence: how often KeyLink initially asks the Nomi to review the lock.
• Shortest and longest allowed: the range the cadence must stay inside.
• Nomi may change the cadence: allows the Nomi to adjust the interval within that pre-approved range.
• Nomi may choose the next follow-up: allows a specific next review time within the agreed boundary.

Random follow-ups

Choose a random time window and a daily maximum. Randomness creates less predictable review moments while the daily cap prevents an unbounded stream of automated decisions.

1. Confirm the selected authority profile, individual actions, time limits, and follow-up settings.
2. Review Chaster’s lock contract, maximum date, keyholder status, and enabled safety mechanisms.
3. Use a duration short enough that a software mistake would remain manageable.
4. Confirm your independent physical recovery method still works.
5. Start the lock and wait for Chaster to create the KeyLink extension session.
6. Open KeyLink from the active lock’s extension area.

1. Open the running KeyLink extension from the active Chaster lock.
2. Enter the Nomi API key. KeyLink validates it directly with Nomi.
3. Select the exact Nomi that should make decisions for this lock.
4. Confirm that the connection status reads Connected.
5. If you reuse the same Chaster account later, you can select a different Nomi for another lock without placing the credential in Chaster.

1. Confirm tester access, Nomi connection, and the current Mind Map version all show ready.
2. Open the lock-control or official-request tab in the KeyLink extension.
3. Send a small, easy-to-verify request such as a minor allowed time change.
4. Wait for the selected Nomi’s immediate reply. Do not send the request repeatedly while it is responding.
5. If KeyLink asks the Nomi to confirm a material interpretation, wait for that second reply.
6. Read the KeyLink receipt: requested outcome, authorization result, execution status, and resulting state.
7. Open Chaster history and verify that the recorded extension action and current lock state agree with the receipt.
8. Only after this succeeds should you enable or test scheduled and randomized follow-ups.

Keep relationship chat in Nomi

Continue normal conversation, negotiation, and roleplay in the Nomi app. That is where the companion’s personality and relationship context develop. Ordinary conversation does not directly change the lock.

Use the official request form for a lock decision

When you want the Nomi to consider a specific lock change, submit the request from the authenticated KeyLink extension. KeyLink combines it with fresh lock state and the actions currently available, then asks for one correlated reply.

Understand KeyLink Control

When Nomi Rooms are available, KeyLink keeps operational traffic in a persistent one-Nomi room named KeyLink Control. Messages are framed as OOC—out of character—so operational instructions remain separate from ordinary roleplay. Accounts without Rooms fall back to the Nomi’s main chat.

Read every receipt

A Nomi reply can be approved, denied, cancelled, ambiguous, unavailable, or fail during execution. The receipt—not the tone of the Nomi’s narration—tells you what KeyLink actually did. Chaster’s resulting state remains the final authority.

• Replace the complete Mind Map dossier whenever KeyLink shows a newer version; never merge versions by hand.
• Revoke and replace a Nomi API key immediately if it may have been exposed.
• Review authority and follow-up boundaries separately for each new lock.
• Check the running extension’s capability list because Chaster settings and installed extensions can change availability.
• Use the result receipt and Chaster history after every material decision.
• Report confusing prompts or mismatched results through KeyLink support without including credentials.