@naraya/cli 0.1.0 → 0.4.0

package/LICENSE

@@ -0,0 +1,20 @@
+Naraya CLI — Proprietary License
+Copyright (c) 2026 PT. Naraya Teknologi Indonesia. All rights reserved.
+
+This software and its accompanying assets (including but not limited to system
+prompts, agent definitions, skills, and configuration) are the confidential and
+proprietary property of PT. Naraya Teknologi Indonesia ("Naraya").
+
+NO LICENSE IS GRANTED to copy, modify, distribute, sublicense, reverse engineer,
+decompile, disassemble, or create derivative works from any part of this
+software or its assets, in whole or in part, except as expressly authorized in
+writing by Naraya.
+
+Use of this software requires a valid Naraya account and API key and is governed
+by the Naraya Terms of Service. Access may be revoked at any time.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL NARAYA BE LIABLE
+FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

package/README.md

@@ -1,93 +1,394 @@
-# NaraCLI
-
-
-
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-* [Create](https://docs.gitlab.com/user/project/repository/web_editor/#create-a-file) or [upload](https://docs.gitlab.com/user/project/repository/web_editor/#upload-a-file) files
-* [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://gitlab.naraya.ai/adearman/naracli.git
-git branch -M main
-git push -uf origin main
-```
-
-## Integrate with your tools
-
-* [Set up project integrations](https://gitlab.naraya.ai/adearman/naracli/-/settings/integrations)
-
-## Collaborate with your team
-
-* [Invite team members and collaborators](https://docs.gitlab.com/user/project/members/)
-* [Create a new merge request](https://docs.gitlab.com/user/project/merge_requests/creating_merge_requests/)
-* [Automatically close issues from merge requests](https://docs.gitlab.com/user/project/issues/managing_issues/#closing-issues-automatically)
-* [Enable merge request approvals](https://docs.gitlab.com/user/project/merge_requests/approvals/)
-* [Set auto-merge](https://docs.gitlab.com/user/project/merge_requests/auto_merge/)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-* [Get started with GitLab CI/CD](https://docs.gitlab.com/ci/quick_start/)
-* [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/user/application_security/sast/)
-* [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/topics/autodevops/requirements/)
-* [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/user/clusters/agent/)
-* [Set up protected environments](https://docs.gitlab.com/ci/environments/protected_environments/)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+# Naraya CLI
+
+> One sign-in, every model. A coding agent that delegates specialist work to focused subagents and brings evidence to every claim.
+
+[![Node](https://img.shields.io/badge/node-%E2%89%A522.19-blue)](https://nodejs.org) [![License: MIT](https://img.shields.io/badge/license-MIT-green)](LICENSE) [![Version](https://img.shields.io/badge/version-0.2.4-blue)](package.json)
+
+Naraya CLI is a thin wrapper around [pi](https://github.com/earendil-works/pi-mono) that:
+
+- Routes all model traffic through [router.naraya.ai](https://router.naraya.ai) with one API key.
+- Ships **11 focused subagents** (`nara-build`, `nara-architect`, `nara-release`, `nara-review`, `nara-debug`, `nara-plan`, `nara-explore`, `nara-search`, `nara-fe`, `nara-droid`, `nara-vision`) as folder-based packages with their own skills, scripts, and references.
+- Injects a `APPEND-SYSTEM.md` so the model reaches for the bundled agents and skills on every turn.
+- Provides a `delegate` tool that fans work out to subagents in parallel, sequential chains, or single focus — each in an isolated context window.
+
+---
+
+## Table of contents
+
+- [Install](#install)
+- [Quickstart](#quickstart)
+- [Usage](#usage)
+- [Subagents](#subagents)
+- [Skills](#skills)
+- [Agent structure](#agent-structure)
+- [Extending](#extending)
+- [Development](#development)
+- [Architecture](#architecture)
+- [License](#license)
+
+---
+
+## Install
+
+```bash
+# Requires Node.js >= 22.19
+npm install -g @naraya/cli
+```
+
+Or use directly from a checkout:
+
+```bash
+git clone https://gitlab.naraya.ai/adearman/naracli
+cd naracli
+npm install
+npm link   # expose `naraya` on PATH
+```
+
+---
+
+## Quickstart
+
+```bash
+# 1. Sign in (one-time)
+naraya login
+
+# 2. Verify auth
+naraya status
+
+# 3. Launch the agent in the current project
+naraya
+```
+
+Inside the agent, press `/` for the command palette, `/agents` to list subagents, `/skills` to list skills.
+
+```bash
+# Quick subcommands without launching the TUI
+naraya login              # OAuth-style sign-in to router.naraya.ai
+naraya logout             # wipe local credentials
+naraya status             # show auth + quota + current model
+naraya status --usd       # same, with USD cost equivalent
+```
+
+---
+
+## Usage
+
+### Interactive mode
+
+```bash
+naraya                        # launch in cwd
+naraya --model naraya/glm-5   # override default model for this session
+naraya --continue             # resume the last session
+```
+
+Slash commands inside the TUI:
+
+| Command | Effect |
+|---|---|
+| `/agents` | list subagents |
+| `/agent-model <name>` | change a subagent's model |
+| `/skill:<name> [args]` | load a skill |
+| `/skills` | list available skills |
+| `/help` | full command palette |
+
+### Headless / scripted
+
+```bash
+naraya -p "audit the auth module for OWASP top 10"   # single prompt, prints result, exits
+naraya -p --json <task>                              # machine-readable output
+```
+
+### Delegation patterns (built into the model)
+
+The agent delegates to specialists via the `delegate` tool. You do not invoke it directly — you phrase the request and the model decides.
+
+Patterns the model uses:
+
+```ts
+// One focused specialist
+delegate { agent: "nara-droid", task: "..." }
+
+// Independent units in parallel (max 8 at once, 4 concurrent)
+delegate { tasks: [
+  { agent: "nara-search",  task: "research X" },
+  { agent: "nara-explore", task: "find usages of Y" },
+  { agent: "nara-plan",    task: "draft plan for Z" }
+]}
+
+// Sequential, {previous} injects the prior step's output
+delegate { chain: [
+  { agent: "nara-explore", task: "map the auth flow" },
+  { agent: "nara-plan",    task: "draft a plan based on {previous}" },
+  { agent: "nara-review",  task: "review the plan in {previous}" }
+]}
+```
+
+---
+
+## Subagents
+
+Naraya ships **11 subagents**. Each is a self-contained folder under `assets/agents/`.
+
+### Coordination
+
+| Agent | Purpose | When to use |
+|---|---|---|
+| `nara-build` | Implements features, bugfixes, refactors, releases | Top-level orchestrator. Default for "implement X", "fix Y", "refactor Z" |
+| `nara-architect` | System design, ADRs, component decomposition | Greenfield design, scaling decisions, API contract design, trade-off analysis. Read-only — never edits code |
+| `nara-release` | Version sync, verification, deploy safety | Before any production push, mobile store release, or schema migration |
+| `nara-review` | Multi-aspect code review (security, perf, a11y, API, tests) | Pre-merge review, audit, self-review before push. Does not fix |
+| `nara-debug` | 4-phase root-cause debugging | "X is broken", flaky tests, intermittent failures. Stops after 3 failed fix attempts |
+
+### Investigation (read-only)
+
+| Agent | Purpose | When to use |
+|---|---|---|
+| `nara-plan` | Implementation plans, never edits code | Pair with `nara-build` for hand-off |
+| `nara-explore` | Fast codebase navigation (haiku) | "Where is X defined?", "who calls Y?", quick map |
+| `nara-search` | Evidence-first research with citations | Library comparison, version migration, external doc lookup |
+
+### Specialist (writes code in their domain)
+
+| Agent | Purpose | When to use |
+|---|---|---|
+| `nara-fe` | Frontend UI/UX (React, Vue, Svelte, Angular, CSS, Tailwind, a11y) | UI changes, component design, responsive, accessibility |
+| `nara-droid` | Native Android (Kotlin, Gradle, Compose, Room, Hilt, adb, APK/AAB) | Android-specific tasks, build failures, release |
+| `nara-vision` | Image analysis using mistral-medium-3-5 vision model | Screenshots, diagrams, UI layouts, code snippets, visual content |
+
+### Picking the right agent
+
+The model picks based on the **unit of work**, not the surface form. Quick heuristic:
+
+- The user said "implement", "fix", "build", "add", "refactor" → `nara-build`
+- The user said "plan", "design", "architect", "decompose" → `nara-architect` (design) or `nara-plan` (task breakdown)
+- The user said "review", "audit", "check this" → `nara-review`
+- The user said "release", "deploy", "ship" → `nara-release`
+- The user said "debug", "broken", "crash", "flaky" → `nara-debug`
+- The user said "find", "where", "who calls" → `nara-explore`
+- The user said "research", "compare", "what is the best", "how does X work in library Y" → `nara-search`
+- The user said something Android-specific → `nara-droid`
+- The user said something UI/frontend-specific → `nara-fe`
+- The user shared an image, screenshot, or needs visual analysis → `nara-vision`
+
+If multiple of these apply, the model fans out to parallel subagents.
+
+---
+
+## Skills
+
+Naraya bundles a **global skill pool** at `skills/` (~100 skills) that any agent can load on demand via `/skill:<name>` or by reading `skills/<name>/SKILL.md` directly.
+
+Highlights:
+
+| Skill | What it covers |
+|---|---|
+| `systematic-debugging` | 4-phase root-cause debugging |
+| `test-driven-development` | RED-GREEN-REFACTOR discipline |
+| `writing-plans` | Implementation plans with bite-sized tasks |
+| `web-app-release-workflow` | Ship Dockerized web apps |
+| `security`, `auth-identity`, `compliance-governance` | Security review and compliance |
+| `architecture`, `api-design-patterns`, `distributed-systems` | System design |
+| `mlops/*` | ML/LLM training, serving, fine-tuning, evaluation |
+| `creative/{humanizer, p5js, claude-design}` | Content / UI generation |
+| `android-kotlin`, `compose-patterns`, `gradle-troubleshoot` | Android development |
+| `react-patterns`, `css-patterns` | Frontend |
+
+**Skills vs subagents:** a skill is a workflow / lens the agent applies inline. A subagent is a separate context that runs in parallel. Use skills for "do X the right way", subagents for "do X in isolation".
+
+---
+
+## Agent structure
+
+Each agent is a folder under `assets/agents/`. Folder name MUST equal the frontmatter `name:` field.
+
+```
+assets/agents/
+├── nara-build/                 # Generalist implementer (top-level)
+│   ├── AGENTS.md               # Frontmatter (name/description/tools/model) + system prompt
+│   ├── skills/                 # Agent-specific skills, NOT published to global pool
+│   │   └── engineering-patterns/SKILL.md
+│   ├── scripts/                # Helper shell scripts (chmod +x)
+│   │   ├── impact-scan.sh
+│   │   └── scan.sh
+│   ├── references/             # On-demand docs the agent may read into context
+│   │   └── adr-template.md
+│   ├── assets/                 # Static resources (templates, data)
+│   └── README.md               # per-agent docs
+├── nara-plan/                  # Read-only planner
+├── nara-explore/               # Fast read-only code navigation (haiku)
+├── nara-search/                # Evidence-first research
+├── nara-droid/                 # Native Android specialist
+├── nara-fe/                    # Frontend UI/UX specialist
+├── nara-vision/                # Image analysis (mistral-medium-3-5 vision)
+├── nara-architect/             # System design & ADRs (read-only)
+├── nara-release/               # Release safety
+├── nara-review/                # Multi-aspect code review
+└── nara-debug/                 # 4-phase root-cause debugging
+```
+
+### Conventions
+
+- **Folder name = frontmatter `name:`.** The orchestrator warns but does not fail if they diverge.
+- **`AGENTS.md` is the only file the loader reads.** Everything else is opt-in for the agent to `read` into context.
+- **Per-agent `skills/` are NOT published to the global skill pool.** They are scoped to that agent.
+- **Scripts are executable** (`chmod +x`). They can be invoked from the agent's `bash` tool.
+- **References are docs the agent may read.** Large checklists, protocol walkthroughs, template snippets.
+
+### Adding a new agent
+
+1. Create `assets/agents/<your-role>/AGENTS.md` with frontmatter (`name`, `description`, `tools`, `model`) + body.
+2. Add the four subdirs: `skills/`, `scripts/`, `references/`, `assets/`.
+3. (Optional) Add a `README.md` documenting the agent.
+4. Run `npm test` to confirm the seed manifest picks it up.
+5. (Optional) Add the agent to the roster in `assets/APPEND-SYSTEM.md` so the model knows to delegate to it.
+
+### Editing an existing agent
+
+Edit `assets/agents/<role>/AGENTS.md`. The orchestrator hot-reads this on each `delegate` call, so changes take effect on the next invocation. No restart needed.
+
+---
+
+## Extending
+
+### Adding a skill to a specific agent
+
+Drop a directory under `assets/agents/<role>/skills/<skill-name>/` with a `SKILL.md` inside:
+
+```
+assets/agents/nara-fe/
+└── skills/
+    └── vue-patterns/
+        └── SKILL.md
+```
+
+### Adding a skill to the global pool
+
+Drop it under `skills/<skill-name>/SKILL.md` at the repo root. The global pool is auto-discovered by pi.
+
+### Overriding model per-agent
+
+Edit the frontmatter `model:` field in `AGENTS.md`. Or set a per-agent override at runtime with `/agent-model <agent> <model>`.
+
+### Customizing the system prompt
+
+Edit `assets/APPEND-SYSTEM.md`. This file is appended to the model's system prompt on every launch.
+
+---
+
+## Development
+
+```bash
+git clone https://gitlab.naraya.ai/adearman/naracli
+cd naracli
+npm install
+npm test                # run node:test suite (8 tests)
+```
+
+### Project layout
+
+```
+naraya-cli/
+├── bin/
+│   └── naraya.mjs             # CLI entry: subcommand dispatch + pi launch
+├── src/
+│   ├── banner.mjs             # login/launch banner
+│   ├── clipboard.mjs          # copy auth URL to clipboard
+│   ├── config.mjs             # models.json read/write
+│   ├── goodbye.mjs            # farewell on quit
+│   ├── login.mjs              # naraya login (OAuth-style)
+│   ├── seed.mjs               # asset sync to ~/.naraya/agent
+│   ├── splash.mjs             # startup animation
+│   └── status.mjs             # naraya status (quota, cost)
+├── assets/
+│   ├── APPEND-SYSTEM.md       # injected into system prompt
+│   ├── agents/                # 10 subagent folders (see above)
+│   ├── extensions/            # .ts extensions loaded by pi
+│   ├── skills/                # empty (skills live at repo root for global pool)
+│   └── themes/naraya.json     # default theme
+├── skills/                    # global skill pool (~100 skills)
+├── test/
+│   ├── config.test.mjs
+│   ├── seed.test.mjs          # covers agent folder + nested resources
+│   └── status.test.mjs
+├── package.json
+└── README.md
+```
+
+### Testing
+
+```bash
+npm test                                  # all 8 tests
+node --test test/seed.test.mjs           # just seed (asset sync)
+node --test test/status.test.mjs         # just status rendering
+```
+
+The seed test covers both the legacy flat layout and the new folder-based agent layout (AGENTS.md + nested skills/scripts).
+
+---
+
+## Architecture
+
+### Request flow
+
+```
+User input
+   │
+   ▼
+┌─────────────────────────┐
+│ bin/naraya.mjs          │  CLI entry, subcommand dispatch
+│  - login/logout/status  │
+│  - else: launch pi      │
+└──────────┬──────────────┘
+           │
+           ▼
+┌─────────────────────────┐
+│ src/seed.mjs            │  Sync assets/ to ~/.naraya/agent
+│  - assets/agents/*      │   (only managed files; user files preserved)
+│  - assets/extensions/*  │
+│  - assets/APPEND-SYSTEM │
+└──────────┬──────────────┘
+           │
+           ▼
+┌─────────────────────────┐
+│ pi-coding-agent         │  pi runtime
+│  - system prompt:       │   ← APPEND-SYSTEM.md appended
+│  - skill discovery      │   ← global pool + per-agent
+│  - extension loading    │   ← naraya-orchestrator, naraya-debug, etc.
+│  - delegate tool        │   ← fans out to subagents
+└──────────┬──────────────┘
+           │
+           ▼
+┌─────────────────────────┐
+│ Subagent (isolated ctx) │  one per `delegate` call
+│  - reads AGENTS.md      │
+│  - reads per-agent      │
+│    skills/scripts/refs  │
+│  - reads global skills  │
+│  - returns result       │
+└─────────────────────────┘
+           │
+           ▼
+        Output to user
+```
+
+### Why folder-based agents?
+
+- **Colocation.** Each agent is one self-contained directory: definition + skills + scripts + references + assets. Move it, version it, delete it as one unit.
+- **No global namespace pollution.** Per-agent `skills/` are scoped; only `AGENTS.md` is published.
+- **Easier to share.** A folder is a package. An `.md` file in a flat dir is a file in a list.
+- **Scales.** Adding an agent = adding a folder. Adding an agent to the old flat layout = adding a file that could collide.
+- **Backward compatible.** The orchestrator loader supports both folder layout (`<role>/AGENTS.md`) and legacy flat (`<role>.md`).
+
+### Why split coordination / specialist / investigation?
+
+- **Coordination agents** (`nara-build`, `nara-architect`, `nara-release`, `nara-review`, `nara-debug`) need broad context. They route, sequence, verify.
+- **Specialist agents** (`nara-fe`, `nara-droid`) need deep domain knowledge. Their system prompt is shaped by their domain.
+- **Investigation agents** (`nara-plan`, `nara-explore`, `nara-search`) are read-only. They never modify state. They produce artifacts (plans, maps, evidence) that the orchestrator consumes.
+
+Mixing these roles in one agent produces shallow specialists and shallow coordinators.
+
+---
+
+## License
+
+MIT. See [LICENSE](LICENSE).

package/bin/naraya-native.mjs

@@ -0,0 +1,4 @@
+#!/usr/bin/env node
+import D from"node:os";import p from"node:path";import f from"node:fs";import"node:crypto";import{AuthStorage as te,ModelRegistry as ne,SessionManager as se,createAgentSession as ae,initTheme as q,getMarkdownTheme as re,getSelectListTheme as oe}from"@earendil-works/pi-coding-agent";import{fileURLToPath as ie}from"node:url";import{TUI as ce,Container as b,Editor as Be,Text as x,Markdown as _e,ProcessTerminal as le,KeybindingsManager as de,TUI_KEYBINDINGS as me,setKeybindings as $e}from"@earendil-works/pi-tui";import{readClipboardImage as ue}from"../src/clipboard.mjs";import"../src/splash.mjs";const F=p.join(D.homedir(),".naraya","native-debug.log"),$=e=>{try{f.appendFileSync(F,`${new Date().toISOString()} ${e}
+`)}catch{}};try{f.rmSync(F,{force:!0})}catch{}process.on("uncaughtException",e=>{$(`UNCAUGHT ${e?.stack??e}`)}),process.on("unhandledRejection",e=>{$(`UNHANDLED ${e?.stack??e}`)});const c="\x1B[38;2;45;123;255m",pe="\x1B[48;2;45;123;255m",he="\x1B[38;2;10;29;77m",ge="\x1B[48;2;10;29;77m",T="\x1B[38;2;255;140;40m",Ne="\x1B[38;2;111;191;115m",B="\x1B[2m",k="\x1B[1m",s="\x1B[0m",fe=/\x1b\[[0-9;]*m/g,m=e=>e.replace(fe,"").length,Ue=(()=>{try{const e=p.dirname(p.dirname(ie(import.meta.url)));return JSON.parse(f.readFileSync(p.join(e,"package.json"),"utf8")).version??"dev"}catch{return"dev"}})(),w=["_____________BB___","___BBB_______BBB__","_BBBBBB______BBBBB","_BBBBBBBB____BBBBB","B_BBBBBBBB___BBBBB","BB_BBBBBBBB__BBBNN","BBB_BBBBBBB__BBNNN","BBBB__BBB____BNNNN","BBBBBB_____BBBNNNN","BBBBBB___BBBBBNNNN","BBBBB___BBBBBBNNNN","BBBBB___BBBBBBNNNN","BBBBB____BBBBBNNNN","BBBBB______BBBNNN_","BBBBB_______BBNN__","_BBBB________B____","__BBB_____________","____B_____________"],M=e=>e==="B"?c:e==="N"?he:"",ye=e=>e==="B"?pe:e==="N"?ge:"";function Ye(){const e=[];for(let t=0;t<w.length;t+=2){let n="";for(let r=0;r<w[t].length;r++){const a=w[t][r],o=w[t+1]?.[r]??"_";a==="_"&&o==="_"?n+=" ":a!=="_"&&o==="_"?n+=`${M(a)}\u2580${s}`:a==="_"&&o!=="_"?n+=`${M(o)}\u2584${s}`:a===o?n+=`${M(a)}\u2588${s}`:n+=`${M(a)}${ye(o)}\u2580${s}`}e.push(n)}return e}const j=(e,t)=>e+" ".repeat(Math.max(0,t-m(e)));function Ke(e,t){const n=Math.max(...e.map(m),0),r=Math.max(...t.map(m),0),a=Math.max(e.length,t.length),o=Math.floor((a-e.length)/2),_=Math.floor((a-t.length)/2);return Array.from({length:a},(N,l)=>`${j(e[l-o]??"",n)}  ${j(t[l-_]??"",r)}`)}const E=p.join(D.homedir(),".naraya","agent"),G=p.join(E,"models.json");let U;try{U=JSON.parse(f.readFileSync(G,"utf8"))}catch{console.error("Run `naraya login` first."),process.exit(1)}const y=U.providers?.naraya??{},be=(y.models??[]).map(e=>e.id),h=process.env.NARAYA_MODEL??be[0],xe=(y.models??[]).find(e=>e.id===h)?.name??h;h||(console.error("No naraya models \u2014 run `naraya login`."),process.exit(1));const Y=te.create(p.join(E,"auth.json")),K=ne.create(Y,G),P=K.find("naraya",h);P||(console.error(`Model naraya/${h} not found.`),process.exit(1));const{session:I}=await ae({cwd:process.cwd(),agentDir:E,model:P,thinkingLevel:"off",authStorage:Y,modelRegistry:K,tools:["read","grep","find","ls","edit","write","bash"],sessionManager:se.create(process.cwd())});try{$e(new de(me))}catch{}try{q("naraya",!0)}catch{try{q("dark",!0)}catch{}}const we=re(),Me={borderColor:e=>`${c}${e}${s}`,selectList:oe()};let V=!1,J=!1,z=0,H=0,u=null;async function Se(){try{const e=await fetch(`${y.baseUrl}/me`,{headers:{authorization:`Bearer ${y.apiKey}`},signal:AbortSignal.timeout(3e3)});if(!e.ok)return;const t=await e.json(),n=Number(t.quota?.limit??0),r=Number(t.quota?.remaining??0),a=o=>o>=1e6?`${(o/1e6).toFixed(1).replace(/\.0$/,"")}M`:Number(o).toLocaleString("id-ID");u={email:t.account?.email??"",plan:t.account?.plan??"",saldo:`Rp ${Number(t.credit?.available??0).toLocaleString("id-ID",{maximumFractionDigits:0})}`,usd:t.credit?.usd_equivalent?`$${t.credit.usd_equivalent}`:"",kuota:n>0?`${a(r)} / ${a(n)}`:"fair-use",models:Array.isArray(t.models)?t.models.length:0}}catch{}}const Ae={render(e){const t=Math.min(48,Math.max(40,e-2)),n=t-4,r=(d,L)=>{const ee=Math.max(1,n-m(d)-m(L));return`${d}${" ".repeat(ee)}${L}`},a=y?`${B} v${process.env.NARAYA_VERSION??"dev"}${s}${c}`:"",o=` ${k}NARAYA${s}${a}${c} `,_=`${c}\u256D\u2500${o}${"\u2500".repeat(Math.max(0,t-m(o)-3))}\u256E${s}`,N=`${c}\u2570${"\u2500".repeat(Math.max(0,t-2))}\u256F${s}`,l=d=>`${c}\u2502${s} ${d}${" ".repeat(Math.max(0,n-m(d)))} ${c}\u2502${s}`;return u?[_,l(r(`${k}${u.email}${s}`,`${B}${u.plan}${s}`)),l(r(`${c}Saldo${s} ${u.saldo}`,`${B}${u.usd}${s}`)),l(r(`${c}Kuota${s} ${u.kuota}`,`${B}${u.models} model${s}`)),N,""]:[_,l(`${B}memuat akun\u2026${s}`),N,""]}},Ce={render(e){const t=process.cwd(),n=`${c}\u25C6 ${xe}${s}`,r=Math.max(1,e-m(t)-m(n)),a=`${B}${t}${s}${" ".repeat(r)}${n}`,o=d=>d<1e3?`${d}`:`${(d/1e3).toFixed(1).replace(/\.0$/,"")}k`,_=`${B}\u2191${o(z)} \u2193${o(H)} tokens${s}`,N=`${V?T:B}\u26A1 auto-approve ${V?"ON":"OFF"} \xB7 Ctrl+Alt+A${s}`,l=`${J?T:B}\u2702\uFE0F truncate ${J?"ON":"OFF"} \xB7 Ctrl+Alt+O${s}`;return["\u2500".repeat(e),a,_,N,l]}},i=new ce(new le,!1),W=()=>{try{i.stop()}catch{}try{I.dispose?.()}catch{}process.exit(0)};process.on("SIGINT",W);const X=new b,g=new b,Q=new b,Z=new b;X.addChild(Ae),Z.addChild(Ce);let R=null,O="",S=!1;const A=new Map;let C=0;async function Te(e){$(`submit text=${JSON.stringify((e??"").slice(0,40))} busy=${S}`);let t=(e??"").trim();if(!t&&A.size===0||S){$("submit skipped (empty/busy)");return}const n=[];t=t.replace(/\[🖼 Image #(\d+)\]/g,(a,o)=>{const _=A.get(Number(o));if(_)try{n.push({type:"image",data:f.readFileSync(_.path).toString("base64"),mimeType:_.mimeType})}catch{}return""}).replace(/\s{2,}/g," ").trim(),A.clear(),C=0;const r=n.length?`${B}\u{1F4CE} ${n.length} gambar${s}  `:"";g.addChild(new x(`${r}${k}\u203A${s} ${t||"(gambar)"}`,1,0)),O="",R=new _e("",1,0,we),g.addChild(R),i.requestRender(),S=!0;try{await I.prompt(t||"Describe this image.",n.length?{images:n}:void 0)}catch(a){$(`prompt error ${a?.stack??a}`),g.addChild(new x(`${T}[error]${s} ${a?.message??a}`,1,0))}finally{S=!1,i.requestRender()}}class ke extends Be{handleInput(t){if($(`handleInput ${JSON.stringify(t.slice(0,10))} len=${t.length}`),t===""){W();return}if(t==="\r"||t===`
+`){const n=this.getText();this.setText(""),Te(n);return}if(t==="\x1Bv"||t==="\x1BV"){const n=ue();if(n){C+=1,A.set(C,n);const r=this.getText(),a=r&&!r.endsWith(" ")?" ":"";this.setText(`${r}${a}[\u{1F5BC} Image #${C}] `),i.requestRender()}return}super.handleInput(t)}}const v=new ke(i,Me,{placeholder:"Pesan ke Naraya \u2014 Enter kirim \xB7 Alt+V tempel gambar \xB7 Ctrl+C keluar"});Q.addChild(v),I.subscribe(e=>{if($(`event ${e.type}${e.assistantMessageEvent?.type?"/"+e.assistantMessageEvent.type:""}`),e.type==="message_update"&&e.assistantMessageEvent?.type==="text_delta")O+=e.assistantMessageEvent.delta,R?.setText(O),i.requestRender();else if(e.type==="tool_execution_start")g.addChild(new x(`${B}\u2699 ${e.toolName??"tool"}\u2026${s}`,1,0)),i.requestRender();else if(e.type==="turn_end"){const t=e.message?.usage;t&&(z+=t.input??0,H+=t.output??0),i.requestRender()}}),i.addChild(X),i.addChild(g),i.addChild(Q),i.addChild(Z),i.setFocus(v),i.start(),$(`started; focus=${i.focusedComponent===v?"editor":"other"} isTTY=${process.stdin.isTTY}`),g.addChild(new x(`${Ne}\u2713${s} Naraya native \u2014 naraya/${h}. Ketik pesan, Enter kirim.`,1,0)),Se().then(()=>i.requestRender());