Action Builder
Schema v1 templates Generates plain .sheevactions JSON using keyed source objects, nested source maps, flat placeholders, and an explicit execute.type. Packaged libraries can place the completed manifest at the root of a .sheevactionszip file.
Step 1 of 8

How does your app communicate?

Choose how SheevChat will talk to the app you want to control.

Step 2 of 8

How does SheevChat find the app?

Choose the runtime's connection or discovery pattern. All file paths remain inside approved local roots.

Step 3 of 8

Do your actions need dynamic dropdowns?

Dropdowns let users pick options fetched live from the app — like a list of scenes, models, or hotkeys.

Step 4 of 8

What WebSocket message style does your app use?

This only applies to WebSocket connections. Different apps format their messages differently — this affects how SheevChat maps responses.

Step 5 of 8

Does your app require authentication?

Some local apps require a token or session handshake before dropdowns and actions will work.

Step 6 of 8

What should the library be called?

These values become the manifest identity shown in SheevChat. You can change them later.

Required fields must be completed before continuing.

3–64 lowercase letters, numbers, hyphens, or underscores.
Included in the AI handoff so it can locate adjacent developer resources.
Step 7 of 8

Where does SheevChat connect?

Provide the connection or safe discovery details selected in Step 2.

Required for the selected connection pattern.

Use the complete local HTTP or WebSocket base URL.
Relative directories resolve beneath the user's home directory.
Step 8 of 8

What should the starter action do?

Name the first action and provide its request target. Dropdown list endpoints and response mappings remain marked TODO because they depend on the target API.

Required fields define the starter action.

HTTP path, WebSocket channel, or message type.
Generates required query sequencing and typed output metadata.
Use when greetings or unrelated WebSocket events can arrive first.

Your Skeleton Manifest

Draft Review the generated fields below.

Guided fill-ins

Unresolved template values

Sources and response lists

Actions, payloads, and results

Advanced JSON editing

Live manifest preview

Drafts may be downloaded with unresolved values for AI-assisted completion. A manifest is marked ready only when required TODO values and schema errors are gone. See the AI-friendly Action Library Wiki for the full schema.