Cici Web & CLI

Cici Web answers inside your browser workspace. Cici CLI is a separate terminal workflow on your computer. Use the links below to jump directly to the guide you need.

Cici CLI is available to current Max subscribers, active Enterprise owner/engineer seats and currently assigned admin/facilitator roles. Installing a client or keeping an old terminal token never bypasses the server’s per-action entitlement check.

Analysis costs one shared credit and Capacity three for Max. Admin/facilitator and activated Enterprise seats have unlimited processing. Review inputs, warnings and the exact output folder before confirming execution. CLI AI retains a separate 20-successful-replies-per-UTC-day allowance for ordinary users. Service-wide limits still apply. VDT stays on Web.

Open Cici from the workspace. Start with KPI, coverage, handover, or throughput shortcuts, or ask a question about the current dataset. Responses follow the active interface language.

Cici's cloud mascot stays sleepy and blinks slowly. Hover wakes it briefly; click or press Enter/Space to open the assistant. Hover never sends a question or starts processing. Motion stops for reduced-motion and Save Data preferences, and pauses in background tabs.

State the segment or metric you want to investigate. Ask Cici to separate observed evidence, possible causes, and the next validation step.

When you send a question, Cici uses a summary of session metrics and your question. Raw log files and detailed route coordinates are not included in the generated summary. Do not enter confidential identifiers in a question unless you intend to share them.

Cici can help organize an investigation but can be wrong. Check its conclusions against charts, events, and field evidence. When extended analysis is unavailable, it can provide a local metric summary; this is not equivalent to a full diagnosis.

CAKRA opens Account security after sign-in, before the workspace. Set up an authenticator, scan its private QR and enter the current six-digit code. Never share the QR or code. The page also verifies a code from an existing authenticator; use this when CAKRA requests a fresh verification.

Review connected Cici devices at /cli. Revoke devices you no longer recognize or use. Do not approve a login code sent by somebody else. For a lost authenticator, contact CAKRA through the official support channel; do not share passwords or approve another device to recover access.

Cici Web answers inside the browser workspace. Cici CLI runs user-selected local RF workflows in your terminal, using the same CAKRA account and RF/parser source. Conversations and daily allowances are separate. The CLI does not control arbitrary shell commands or network equipment.

CLI execution requires an active Max subscription, an owner/engineer seat in an activated Enterprise organization, or a currently assigned admin/facilitator role. Old one-time payments, profile labels and saved terminal tokens do not unlock execution.

Max analysis costs one shared credit and Capacity three. Authorized Enterprise/admin/facilitator processing is unlimited. Ordinary Max and Enterprise seats retain 20 successful CLI AI responses per UTC day; failed/fallback responses do not count. Web AI allowances are separate. Removing a subscription, role or Enterprise seat removes protected access; a retained terminal token cannot preserve it. Global provider capacity and security rate limits still apply.

Cici CLI is installed on your own computer, not inside the browser. You need an internet connection, Node.js 22+ and PowerShell/CMD on Windows or Bash/Zsh on Linux/macOS.

An authorized Enterprise owner/engineer seat or a currently assigned admin/facilitator role is needed for CLI execution. The CLI service must be enabled. VDT remains on Web.

Ordinary accounts need a current owner/engineer seat in an explicitly activated Enterprise organization. Installing the public client, holding an old device token, changing browser state or retaining a past purchase does not grant server access. Viewer seats are read-only.

Assigned admin/facilitator roles keep their existing unlimited access while active. The server checks the current role, purchase expiry, verified account and ban status at authorization. Revoking the role or downgrading removes usage access; listing/revoking your devices remains available for safety.

Open Resources → Cici CLI in the navbar, or use Cici CLI in the footer. On mobile, open the navigation menu and find it under Resources. The link opens account connection and installation; sign in if requested. Opening the page does not authorize a terminal or spend credits. Server access rules still apply.

Open Start, search PowerShell or Command Prompt, and open it as your normal user. Windows Terminal is also fine: select a PowerShell or CMD tab.

In step 2, select PowerShell if you opened PowerShell, or CMD if you opened Command Prompt. Paste into the terminal prompt, not the browser address bar, developer console or Cici interactive prompt.

Open Terminal with Bash or Zsh, then select Linux / macOS in step 2. Run as your normal user, not with sudo.

WSL is a separate Linux environment: install Node and Cici inside WSL if that is where you want to work. WSL, containers and other OS accounts need their own login.

Use the terminal selector below. Copy command gives the compact official installer. The first wrapper is trusted through official HTTPS; it checks the installer and CLI SHA-256. Advanced verification also pins the first script before executing it. These hashes are integrity checks, not publisher signatures.

Close the terminal used for installation and open a new one so the updated user PATH is loaded. Run these commands one at a time.

cici --version should print 0.8.10. cici doctor checks your local setup without an AI call or processing charge. A not-signed-in result is normal before step 4.

Installation is needed once, not each session. Later, open your normal terminal and run cici directly. The launcher uses the Node location saved during installation; if you move or remove that runtime, repair the installation after installing Node again.

Run cici login below, or choose Connect account inside cici. The browser is used only for account approval; your RF workspace stays in the terminal tab. Your password is entered only on the CAKRA website, never into the CLI.

Run cici to open a dedicated Cici workspace through your OS terminal. Choose EN or ID first, then use the main menu. Windows uses Windows Terminal with a CAKRA profile; Linux needs a desktop terminal and macOS uses Terminal. If a separate session is unavailable, cici falls back to this tab. cici --current-tab or cici tui explicitly stays here; no browser workspace or local HTTP server is created.

Home, Help and Guide reuse one application screen rather than adding new homes to scrollback. Use arrows/Enter, numbers and Escape; long Help has Next/Previous pages. / opens the command prompt. /home or /reset returns to home without deleting outputs or credentials. TERM=dumb uses ordinary numbered output instead of screen control.

Choose browse files, browse a folder, or typed/dragged paths. Use Space to select files and Enter to continue. Choose the source timezone with arrows/Enter: WIB, WITA, WIT or UTC, or enter another IANA timezone manually. This declares the log clock; Cici does not infer it from your device or city.

Review the inputs and output destination. Existing output folders receive a unique child; the default is ~/Cici Results. The final confirmation shows the exact destination and execution scope. Type y then Enter to authorize, or n/empty Enter to cancel; other input asks again without starting execution. Max uses one shared credit for analysis or three for Capacity; active Enterprise/admin/facilitator access is unlimited. VDT remains on Web.

Login tokens last 30 days and can be revoked from CAKRA /cli. Run cici logout to remove local credentials and attempt server revocation. If offline, revoke the device on Web once connected.

Windows protects credentials with your Windows-account DPAPI. Linux/macOS keep an owner-only file in ~/.cakra-cici, not an encrypted Keychain. Never copy or share credential files.

Match the message to the next step below. Do not disable TLS, skip a checksum check or change a company security policy to make installation work.

Cici checks official release metadata when an interactive workspace starts and every 5 minutes while open. When a newer stable release is available, it downloads and verifies the official installer and CLI checksum, installs into the existing managed directory, then continues with the new version. Choose Update Cici or run cici update to install immediately. No credentials, RF files, AI calls or credits are involved. Offline, timeout, downgrade and invalid metadata do not block the current workflow or claim the client is up to date.

Automatic installation applies only to the official managed Cici installation and interactive launches. CICI_AUTO_UPDATE=0 disables automatic installation while leaving manual cici update available; CICI_NO_UPDATE_CHECK=1 disables update checks. Scripts and --json invocations do not silently install updates.

Website deployment alone cannot add self-update capability to an already-installed older client. Users on 0.8.0 or earlier need to run the official installer once after 0.8.1 is deployed; later stable updates install automatically. Historical release bundles, login and results are preserved. If a workflow was interrupted, recover it with its original CLI version before switching versions.

Set the source timezone once, or supply --timezone for each run. A saved setting is your clock declaration, not automatic receiver verification. --lang en|id overrides the selected help/AI language; shared parser messages are not fully localized.

doctor is offline and read-only by default. doctor --online explicitly checks account access without processing a dataset or making an AI call. config show contains preferences, not your token. config set server changes the next login preference only; existing credentials stay bound to their original origin. Logout before switching accounts or servers.

Choose 1–30 explicit TXT/CSV/KML paths, or one immediate folder, at most 100 MB total and 100,000 normalized samples. UTF-8 and UTF-16 LE/BE with BOM are supported; JSON files must be UTF-8. Folder scanning is not recursive and skips hidden files/symlinks. Extract ZIP first. Use --root to narrow the allowed directory. Quote paths with spaces; ~ or ~/ expands your home directory.

Analysis and capacity require an explicit IANA timezone declaration through --timezone or saved config, such as Asia/Jakarta. Explicit source offsets are preserved. Offset-free clock interpretation uses your declaration, not an inferred city or verified device clock.

Inputs are checked before processing. Execution asks you to review warnings and confirm analysis 1 / capacity 3 shared credits. --yes confirms only the invoked action; it does not bypass account, access or access checks.

VDT stays exclusively in CAKRA Web: configuration, prediction, calibration, ray/channel review and all virtual experiments. There is no CLI VDT execution.

Capacity needs complete canonical KPI columns and network-reviewed thresholds. cici template capacity creates a synthetic CSV; cici template criteria exports default threshold JSON for review. Pass --thresholds for your criteria. Missing core KPIs are rejected, not silently replaced by zero; classifications remain hypotheses, not proven causes.

After completed analysis or capacity diagnostics, use cici ask with its result.json and --share-summary. Only the question, selected language and numeric summary are sent; no automatic raw log, source filename, coordinate or full report upload. Do not put confidential raw data in the question. CLI AI explains analysis and capacity summaries, not arbitrary documents or VDT datasets.

Each successful model response counts once. The displayed request ID makes a retry with identical input idempotent; changed input with the same ID is rejected. If the global provider gate is busy, the CLI waits with bounded backoff before a small number of retries. This is not a durable background job queue.

Each authorized run creates result.json, results.csv, report.html and a manifest with original-byte hashes, parser/engine version, clock policy, criteria and the server receipt. Open report.html locally, then Print → Save as PDF. Outputs contain sensitive measurements and source rows: keep them in an authorized location. The HTML export follows the CAKRA journal-style A4 layout; complete evidence remains in result.json and results.csv.

Choose a new output directory for every new run. After interrupted execution, repeat the exact inputs and --out with --retry. The same run ID cannot authorize changed inputs, and existing artifacts are not silently overwritten. Save manifests before sharing results.

The official CLI checks access and current server authorization before releasing reports. Because the RF engine runs locally, a modified client can bypass local code. Strong tamper-proof per-run computation would require a controlled server solver; this local client does not claim that protection.

Keep manifest.json, result.json, results.csv, report.html and run-state.json together. cici inspect checks the four artifact hashes against the completed run state without network access. ask also checks this bundle before AI; altered or missing artifacts are rejected.

Local SHA-256 consistency is not a server signature, independent receipt verification or field-truth certification. For interrupted older runs use the original CLI engine/version; the 0.2 update will not silently reuse a 0.1 engine receipt.

Run cici without arguments for an interactive prompt; help lists commands and exit closes it. The prompt is not an OS shell: it does not evaluate variables, globs, chaining or generated commands. Windows backslashes are preserved; quote paths with spaces. Ctrl+C cancels waits/requests; preserve partial output for an unchanged retry.

watch only announces stable immediate files and never processes automatically. --once stops after the first ready file. --json produces JSON Lines (one event per stdout line), with structured errors on stderr; output may contain private local paths or summaries. Non-interactive processing/AI commands need explicit --yes.

Exit codes: 0 success, 2 usage, 3 login, 4 access, 5 busy, 6 network/server, 7 local I/O/integrity, 130 Ctrl+C, 143 SIGTERM. completion bash|zsh|powershell emits optional static scripts; review before loading. No profile is modified. PowerShell completion needs 7+, while CLI commands also work in Windows PowerShell 5.1. CMD uses native path Tab completion.

After installation and account connection, use your terminal to choose a workflow. The installation guide above covers Node.js, the official installer and device approval.

Run cici for a dedicated workspace, select EN/ID, then enter the main menu. The CLI runs directly in an OS terminal session, not an interactive PowerShell/CMD shell. cici --current-tab or cici tui stays in your current tab; SSH/headless and an unavailable launcher fall back there. Home and submenus reuse one screen. Help is paginated, /home or /reset returns without clearing your files. TERM=dumb uses plain numbered output. No browser GUI or local HTTP server is started.

Choose New workflow, analysis or capacity, then Browse files / Browse folder / Type paths. Native pickers are available on Windows and macOS; Linux browse needs Zenity and a desktop session, otherwise type paths. Drag files into the path prompt and quote names with spaces. For G-NetTrack, select the main measurement TXT and optionally its paired events KML, not every map export. ZIP must be extracted first. Capacity needs one KPI CSV, not a GPS log; select reviewed criteria JSON or review the documented defaults.

Declare the source timezone, inspect sample count, summary and warnings, then choose the output destination. The default creates a unique run inside ~/Cici Results; selecting an existing folder creates a new child without overwriting its files. Choose Stop or type cancel to leave without spending. The exact output and processing cost are displayed before y/yes confirmation. Files are checked again against the reviewed digest before authorization.

Results lets you open the output folder, see the numeric summary, inspect integrity, open report.html for Print / PDF or ask Cici AI. The AI action separately confirms sharing your question plus numeric summary. Its answer is an engineering candidate, not a proven root cause. Help lists command-specific instructions; the command prompt supports /help and /guide, Tab completion and /exit. Commands are not evaluated as shell code.

The terminal uses a brand-blue accent only when color is supported. Set NO_COLOR or TERM=dumb for plain output; pipes and --json remain plain. CLI analysis/capacity require active Max or Enterprise authorization; Max spends one shared credit for analysis or three for Capacity, while Enterprise/admin/facilitator processing is unlimited. CLI AI has its own 20-successful-replies UTC-day allowance. VDT stays on Web.

Filtered session uses only the active RF filter. Selected evidence uses explicit sample IDs intersected with that filter. An event-only selection uses a labelled ±15-second RF context. Sample window includes both entered one-based endpoints; invalid or empty scopes cannot be submitted.

Open evidence on the map, event register or chart, then choose Ask Cici. Review the sample count and Metrics & data quality before asking. Scope changes cancel pending answers and clear the conversation so different contexts are not mixed.

P10/P50/P90 describe the available imported values; missing measurements stay missing. Explicit throughput zero remains zero and may represent an idle test. A serving-label change is not proof of handover success or failure.

E1–E6 open local measurement evidence. K1–K6 refer to a small versioned collection of original CAKRA engineering notes, with links to the corresponding handbook section. Reference material is not another measurement source and is not an exhaustive standards database.

For current scoped requests, the model selects allowed metric paths and references; CAKRA renders the actual numbers and curated explanation. Unknown metrics, forged references or malformed output fall back to a deterministic local answer. Valid structure and consistency do not authenticate the uploaded source or establish a network root cause.

Legacy clients without segment context retain their compatibility behavior. Provider availability, account AI quotas and organization-wide budgets still apply. No customer data is added to a training corpus.