Efficiency recommender
The IDE flags heavy commands and suggests a sandbox run so the app stays fast.
AI
Preview — early access.
Overview
Creytix Dev keeps everything in one app for convenience — you shouldn't have to hop between tools for routine work. But some commands are heavy: a big dependency install, a full build, spinning up a dev server, or running a complete test suite. Running those in-app can slow things down for everyone in the session. The efficiency recommender notices when a command is about to be heavy and offers a lighter path, without getting in your way.
How it works
- As you or an agent prepares to run a command, Creytix Dev checks whether it's the kind of operation known to be resource-heavy — large installs, builds, dev servers, full test runs.
- If it is, a non-blocking hint appears recommending you run it in a sandbox or external environment instead.
- The hint includes a copy-command button, so moving the command out to run elsewhere takes one click.
- You're never stopped from running it in-app if that's what you want — the hint is a suggestion, not a gate.
Steps
- •
Kick off a command as usual
Run a command in Creytix Dev the way you normally would.
- •
Watch for the efficiency hint
If the command is flagged as heavy, a non-blocking hint appears alongside it.
- •
Copy the command with one click
Use the copy-command button to grab the exact command for running in a sandbox or external terminal.
- •
Run it outside, or ignore the hint
Run the heavy command externally to keep the app responsive, or dismiss the hint and continue in-app — your call.
Capabilities
- Heavy-command detection — flags large installs, builds, dev servers, and full test runs as they're about to run.
- Non-blocking hints — a suggestion appears inline; nothing stops or gets rejected.
- Copy-command button — one click to grab the exact command for running elsewhere.
- Responsiveness by default — the goal is keeping the Creytix app fast for you and everyone else in the workspace.
Limits & honest scope
The efficiency recommender is advisory — it recommends, it never blocks.
- It flags known heavy patterns; unusual or custom commands that are just as resource-intensive may not be caught yet.
- It doesn't run the sandbox for you — moving the command outside is still a manual step.
- It optimizes for app responsiveness, not for cost or infrastructure planning.