Who is Foo?

Help / Connect through Executor

Connect through Executor

Add SayWhat to Executor’s tool list so your coding agent can request a Preflight plan.

Think of Executor as a switchboard. It connects your agent to tools, including SayWhat. SayWhat prepares a clear plan; your coding agent follows it. Adding this tool does not install a Preflight rule in your agent.

1. Get ready

  1. Open Executor and follow its setup guide for your version.
  2. For a licensed connection, get an activation code from Account → Setup. Use the activation step in the setup prompt to receive a license token. Save that token in Executor’s secret store. Do not paste it into chat or shared code.

The activation code is a one-use ticket. The license token is the key you keep after activation. The setup page gives you the code; it cannot show an old token again.

2. Add SayWhat to the tool list

An OpenAPI file is an instruction manual for a tool. It lists the requests the tool accepts and the results it sends back. In Executor, add an integration and paste this address:

https://saywhat.foo/openapi/preflight.json
  • Namespace: saywhat. This is the name used to group the tools.
  • Base URL: https://saywhat.foo. This is the service address.

Some versions call this Add Source. If you use the terminal version of Executor, the command is:

executor call executor openapi addIntegration '{
  "spec": "https://saywhat.foo/openapi/preflight.json",
  "namespace": "saywhat",
  "baseUrl": "https://saywhat.foo"
}'

Tool names can vary by version. If addIntegration is missing, check for addSpec in your version’s tool list. Use the same OpenAPI address.

3. Add your license key

Create a connection for SayWhat. In Executor’s secret store, save the token as SAYWHAT_LICENSE_TOKEN. Set the connection to send this request header:

Authorization: Bearer <token>

Replace <token> in the private connection settings. A header is a small note attached to a request. This note proves the request can use your license. Configure Executor to add it from the secret store, so the agent does not need to see the key.

4. Check the license and try Preflight

  1. Run the checkLicense tool. It calls GET /api/health/license. Look for preflight: ready.
  2. Run preflight with your request in instruction. Set targetAgent to the agent that will write the code, such as cursor, codex, or claude-code. Do not use executor as the agent name.
  3. Show receiptText to the person making the request. Pass agentInstruction to the coding agent. The receipt is the short summary; the agent instruction is the full plan.

How this fits your workflow

Executor carries the request to SayWhat and brings the result back. Your agent still needs to be told to run Preflight before coding. For the built-in SayWhat setup paths, choose your agent from Install SayWhat.

Common problems

  • The tool will not import: check the OpenAPI address and the import tool name used by your version of Executor.
  • The license check fails: check the saved token and its request header. If the install was revoked, visit Account → Setup for a fresh activation code.
  • The request rejects the agent name: use the name of your coding agent. Executor is the connection tool, not the agent that writes code.

Still stuck? Contact us with the step that failed and its error message. Leave out activation codes and license tokens.