Yes! There are multiple ways to accomplish this, though all of them rely on the Workspace’s API key.
The easiest way is just to add flags to the embeddable:push command, like this:
npm run embeddable:push -- --api-key [key] --email [email]
This will bypass the Workspace select screen (if you aren’t seeing that screen, don’t worry, it just means you’re only a member of one workspace) and push directly to the Workspace associated with that API key.
If you want a more permanent solution that doesn’t require copying the API key whenever you want to push, you can modify embeddable:push in package.json as it’s just an alias. You can rewrite it however you might want. For example, you can create two separate aliases for sandbox or prod and then use embeddable:push-sandbox or embeddable:push-prod
You’d want to do that securely, and not hardcode the API key into your package.json, of course. We recommend setting it up so it would read api key from an env file
"embeddable:push": "dotenv -e .env -- embeddable push --api-key $EMBEDDABLE_API_KEY --email $EMBEDDABLE_EMAIL"
That way the workspace is implicitly hardcoded, so there’s no interactive prompt and no risk of accidentally pushing to the wrong workspace