LexAI/.gitea/ISSUE_TEMPLATE/bug_report.md at 9895244535c8658054af0ad6cc91bc65a6d63079

kibin/LexAI

Fork 0

Files

john kevin asprec 2c00d2e431

CI — Test & Build / Test & Build (pull_request) Has been cancelled

Details

Preview — PR Build Check / PR Preview Build (pull_request) Has been cancelled

Details

feat(cli): add initial CLI implementation with argument parsing and prompt handling

- Created package.json and package-lock.json for CLI package.
- Implemented argument parsing in args.ts to handle various flags and commands.
- Developed main CLI logic in cli.ts to execute commands and handle errors.
- Added configuration loading from a JSON file in config.ts, with environment variable support.
- Implemented prompt resolution and provider interaction in prompt.ts.
- Added usage documentation for the CLI.
- Configured TypeScript settings in tsconfig.json for the CLI package.
- Updated README in vscode package to reflect the new CLI functionality.
- Refactored root tsconfig.json to streamline project structure.

2026-08-13 19:19:42 +08:00

910 B

Raw Blame History

name, about, title, labels

name	about	title	labels
Bug report	Report a problem with LexAI (Chrome, VS Code, or CLI)	[bug]	bug

Summary

A clear, one-sentence description of the bug.

Package

Which LexAI surface is affected?

Chrome extension (packages/chrome)
VS Code / Cursor extension (packages/vscode)
CLI Prompt Builder (packages/cli)
Shared library (src/lib) / unclear

Environment

LexAI version / commit (if known):
OS:
Browser / VS Code / Cursor version (if relevant):
Provider + model (no API keys):

Steps to reproduce

Expected behavior

What you expected to happen.

Actual behavior

What happened instead. Include error messages (redact secrets).

Screenshots / logs

Attach if helpful. Never paste API keys or encrypted key material.

Additional context

Anything else that might help (page type, selection size, offline, etc.).

910 B Raw Blame History