Sentra Prompt is a standalone Electron desktop workspace for prompt development, template-assisted authoring, optimisation, and provider-backed evaluation.
It is an active SAFRS capsule. The application can be cloned, installed, built, tested, and run without a parent monorepo.
- Node.js 22 or later
- pnpm 11.21.0
- A supported desktop platform for Electron
pnpm install --frozen-lockfile
pnpm run startstart builds and launches the Electron desktop application. No database or LLM
provider is required to open the shell. Optimizer and Evaluator actions require a
configured provider credential.
Copy .env.example to .env.local and set only the values required for the
features being used. Never commit .env.local.
| Capability | Required configuration |
|---|---|
| OpenAI provider | OPENAI_API_KEY |
| Anthropic provider | ANTHROPIC_API_KEY |
| xAI / Grok provider | XAI_API_KEY |
| PostgreSQL operations | DATABASE_URL and DIRECT_URL |
See Data and environment for the full boundary and provider selection behaviour.
| Purpose | Command |
|---|---|
| Install dependencies | pnpm install --frozen-lockfile |
| Lint | pnpm run lint |
| Type-check | pnpm run typecheck |
| Run tests | pnpm run test |
| Build Electron | pnpm run build |
| Launch desktop application | pnpm run start |
| Run smoke test | pnpm run desktop:smoke |
| Validate capsule structure | pnpm run verify:structure |
| Validate a clean extraction | pnpm run verify:extraction |
| Run the complete local gate | pnpm run verify |
| Validate deploy artifacts only | pnpm run deploy:dry-run |
db:generate uses a process-local placeholder URL when database variables are
absent. It generates the Prisma client and never opens a database connection.
- SPDS Read First
- Architecture
- Local operations
- Data and environment
- Testing and verification
- Release procedure
- Prompt quality standard
- Contributing
- Security policy
- Code of conduct
The application contains desktop IPC, provider-key, billing, and data-access surfaces. Do not run database migrations, payment callbacks, provider requests, or production deployment commands as part of routine verification. Changes to those boundaries require designated review.
See LICENSE.