Package Exports

@scramble-cloud/lurus-code-cli
@scramble-cloud/lurus-code-cli/dist/cli.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@scramble-cloud/lurus-code-cli) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Lurus Code CLI

Autonomous AI coding agent for your terminal. Plan, implement, review and ship — directly from the command line.

GDPR-compliant. Zero Data Retention. Made in Germany.

Installation

npm install -g @scramble-cloud/lurus-code-cli

Quick Start

# Authenticate
lurus login

# Start an interactive coding session
lurus chat

# Run a one-shot task
lurus chat -p "Add input validation to the user registration endpoint"

# Batch process multiple files
lurus batch "Add JSDoc comments" --include "src/**/*.ts"

# Security scan
lurus security-ci --format sarif

# AI-powered code review
lurus review-ci --output html

Features

AI Agent — 4 modes, 19+ tools, extended thinking
Code Review — Automated reviews with HTML/JSON export
Security Scanning — 4 scan skills, SARIF output, inline diagnostics
Multi-Agent — Autonomous planning with quality gates
Git & GitHub — Automated commits, PRs, and issues
Testing & TDD — Test generation and TDD workflows
MCP Integration — Model Context Protocol server support
Sessions — Resume, recall, rewind, and export

AI Models

Switch between Claude, GPT, Gemini and open-source models. All providers are bound by Zero Data Retention agreements and a DPA under GDPR.

Configuration

Project-level instructions via LURUS.md in your repository root. Custom rules in .lurus/rules/. MCP servers in .mcp.json.

Enterprise Proxy Support

Lurus Code respects standard HTTP(S) proxy environment variables for CLI-owned network requests:

export HTTPS_PROXY=http://proxy.company.com:8080
export HTTP_PROXY=http://proxy.company.com:8080
export NO_PROXY=.company.local

Local loopback targets (localhost, 127.0.0.1, ::1) are bypassed defensively even when they are not listed in NO_PROXY. Keep using NO_PROXY for internal company domains that should not go through the proxy.

If your organization uses TLS inspection (for example Zscaler, Netskope, or CrowdStrike), set the corporate root CA before starting the CLI. Node.js loads this file at process startup:

export NODE_EXTRA_CA_CERTS=/path/to/corporate-root-ca.pem

Proxy credentials can be provided in the proxy URL for CLI-owned network requests. URL-encode special characters and avoid storing passwords in shell history or scripts:

export HTTPS_PROXY=http://user:pass@proxy.company.com:8080

BrowserAction launches Chrome as a separate process. Lurus passes a credential-safe proxy server to Chrome when possible, but credentials embedded in proxy URLs are not forwarded in Chrome command-line arguments to avoid leaking secrets through process listings. Use a proxy that does not require browser-level authentication or configure Chrome/OS proxy authentication separately for BrowserAction.

Run lurus doctor to diagnose proxy and connectivity issues without logging in. SOCKS, ALL_PROXY, NTLM/Kerberos, PAC/WPAD, and mTLS client certificates are not supported by the built-in proxy integration.

Security & Privacy

Zero Data Retention with all model providers (DPA-backed)
Source code is never stored on our servers
All data is discarded immediately after processing

Requirements

Node.js >= 20
A Lurus Code account — Sign up at code.lurus.ai

Documentation

Full documentation at https://code.lurus.ai/en/docs/cli-commands/

License

Proprietary — see LICENSE for details.