New — Introducing Yaju Software Factory — Try the tool for free
Explore nowPlatform
Functionalities
Use Cases
Deployment
By Industry
Explorations
Initiatives
CLI
You should not have to log into a UI to control your agents. With the open-source Yaju CLI, under the MIT licence, you do not have to.
Deploy and inspect
Deploy agents, inspect activity in real time and retrieve audit trails without opening a dashboard.
Credentials and integrations
Manage credentials and integrations from the terminal. The CLI never stores a secret locally.
Triggers and schedules
Configure triggers and schedules, and apply policies, in the same place you already write code.
Full parity with the dashboard
Anything you can do from the Yaju dashboard, you can do from the CLI.
CI/CD pipelines
Run it inside your existing pipelines. No IDE change and no CI/CD rebuild.
An Agent Orchestration System should not slow down the people using it. The CLI is how governance reaches engineers without changing the way they work.
Governance standards get adopted when they arrive in the terminal rather than in a policy document nobody opens.
Agents built outside Yaju still reach credentials and cost data through the same CLI.
Provision an agent securely from the first run, instead of retrofitting controls once it is already in production.
The Yaju CLI brings deployment, inspection and governance of your agents into the terminal. It talks to the same Agent Orchestration System as the dashboard.
No. Anything you can do from the Yaju dashboard, you can do from the CLI, including audit trails, credentials and policy.
Yes. Running the CLI inside CI/CD pipelines is an explicit use case, and it needs no change to how your pipelines are built.
Secrets are never written to your machine. The CLI attaches credentials at runtime from the Yaju vault, so the value never lands in local configuration, in your shell history or in your code.
Yes. Agents built outside Yaju reach credentials, cost data and audit trails through the same commands as agents built on it.
Yes. Policies are applied from the CLI and enforced by the runtime at the moment the agent acts.
No. The CLI is one surface onto the Yaju Agent Orchestration System. The runtime, the vault and the audit trail sit underneath it and are shared with the dashboard and the SDK.
The CLI is one way in. These are the others.
Browse, run and share production-ready agents, then deploy them from the same terminal.
Read more
Find the waste in an agent and cut its cost without losing quality on your own evals.
Read more
Connect agents to tools, APIs and models through one governed gateway, with credentials resolved at runtime.
Read more
