Feature Guide

A quick orientation block that answers the essential questions: what this feature does, how it works, why it matters, and the key concepts behind it.

What this does

Use the Semitexa AI console as a command translation surface over real operator commands.

Alternative CLI Path

Use intent first, not command recall

If you roughly know what you need but do not remember the exact command, open `bin/semitexa ai` and describe the job in plain language. The workflow is already practical, but still experimental enough that teams should treat it as a guided operator layer, not magic.

Step 1

Open the assistant entrypoint

Start from the Semitexa CLI instead of a separate external tool. This keeps the assistant close to the real runtime and command surface.

bin/semitexa ai

bin/semitexa ai

Step 2

Describe the intent in plain language

You do not need the exact command name first. Ask for the operation you want, then let the assistant map that intent to the relevant CLI workflow.

Flush all cache please.

Flush all cache please.

Restart the local runtime and verify routes.

Restart the local runtime and verify routes.

Show me the commands for inspecting tenant configuration.

Show me the commands for inspecting tenant configuration.

Step 3

Review the translated action

The point is not to hide the real command forever. The point is to get to the correct Semitexa operation faster, with less memory tax and less grep-driven guessing.

cache:clear

cache:clear

server:restart

server:restart

routes:list

routes:list

Quiet Caveat

This path is experimental: useful today, but still not the only workflow you should rely on.
Use it to reduce command-memory burden, not to stay ignorant of the real operator surface.
For repeatable team runbooks, keep documenting the concrete Semitexa commands underneath.
When you need the full machine-readable AI surface, continue to the CLI page about AI Tooling Surface.

bin/semitexa ai natural-language prompts command translation experimental

Verified against Semitexa Ultimate 2026.09.19.1020

AI Console

The AI console is not a separate operator world. It is a natural-language surface over real Semitexa commands and workflows.

Canonical flow

Treat the AI console as an assistant entry point, not as a replacement runtime.
Keep the real commands visible and reviewable.
Use it where command discovery or orchestration benefits from guided translation.

What to preserve

commands stay concrete
outcomes stay inspectable
the runtime remains operator-legible even when AI assists the flow

Why this matters

AI features are only useful when they remain grounded in real framework actions rather than hiding the actual operational surface.

Good Use

Where this helps most

The AI console is strongest when intent is obvious but exact syntax is not. It is a convenience layer over the CLI, not a replacement for operational discipline.

Use it when you know the task but do not remember whether the command is `cache:clear`, `server:reload`, or something else nearby.

Use it for onboarding so new engineers can ask the framework what they mean instead of memorizing everything on day one.

Prefer direct commands in scripts, CI, and team docs where exact repeatability matters more than conversational entry.

If the request is risky or ambiguous, slow down and verify the concrete command before running it.