@kmugalkhod/lightcode 0.15.0 → 0.17.0

package/README.md

@@ -23,10 +23,21 @@ command it installs is `lightcode`.
 
 The two interfaces share the same local sessions, history, provider settings,
 and agent engine. `lightcode web` opens a dedicated loopback-only server and
-launches your browser. Start from Home, Desktop, Documents, Downloads, or
-Projects, browse into any nested folder, then start or resume a project chat.
-The per-launch browser credential stays in the URL fragment and the current
-browser tab; it is never passed to agent subprocesses.
+launches your browser. Opening a project uses the host folder chooser first:
+the Windows or macOS system dialog, then Zenity or KDialog on Linux when
+available in a graphical session. If the system chooser is unavailable or
+cannot open—including Linux without Zenity or KDialog—Lightcode falls back to
+an authenticated in-app browser rooted at Home, Desktop, Documents, Downloads,
+and Projects. That bounded browser is also available as a secondary project
+action. The local server—not the browser page—receives and
+canonicalizes the selected path, rejects filesystem, drive, and UNC share
+roots, and grants only the chosen project; cancelling leaves the current
+workspace unchanged. The per-launch browser credential stays in the URL
+fragment and current tab and is never passed to agent subprocesses.
+
+The browser rail stays focused on projects and sessions. Agents, Skills, MCP,
+Plugins, and deeper customization remain managed through the terminal
+interface for now.
 
 The first browser release runs one Lightcode interface at a time: press Ctrl+C
 to stop the TUI or browser server before switching. Sessions remain available
@@ -84,7 +95,7 @@ variables. Notable keys:
 | `maxRetries` | Provider-call retries for transient errors (default 5) |
 | `autoContinue.stallTimeoutSeconds` | Abort+retry a byte-silent stream (default 300; raise for very slow reasoning models) |
 | `autoContinue.maxErrorRetries` | Auto-resends before surfacing a stream error (default 8) |
-| `LIGHTCODE_DESKTOP_PATH`, `LIGHTCODE_DOCUMENTS_PATH`, `LIGHTCODE_DOWNLOADS_PATH`, `LIGHTCODE_PROJECTS_PATH` | Optional absolute overrides for browser picker locations |
+| `LIGHTCODE_DESKTOP_PATH`, `LIGHTCODE_DOCUMENTS_PATH`, `LIGHTCODE_DOWNLOADS_PATH`, `LIGHTCODE_PROJECTS_PATH` | Optional absolute overrides for the secure common-location fallback; they do not change the host-native picker |
 
 The local companion server listens on `127.0.0.1:4983` (uncommon on purpose —
 port 3000 belongs to the apps you build). Override with `PORT` for the server
@@ -94,6 +105,39 @@ TUI lists every OpenRouter model and persists the choice to
 probes the provider endpoint, and daily JSONL logs live under the Lightcode
 data directory (`logs/`).
 
+## Office networks and certificates
+
+Lightcode uses the same standard enterprise configuration described in
+[OpenCode's network documentation](https://opencode.ai/docs/network/):
+`HTTPS_PROXY`, `HTTP_PROXY`, `NO_PROXY`, and `NODE_EXTRA_CA_CERTS`.
+Local CLI/server connections bypass the proxy automatically.
+The npm launcher on Windows also imports trusted roots from both LocalMachine
+and CurrentUser stores when no explicit CA file is configured. Its export is
+isolated per launch and limited to ten seconds.
+
+If your office inspects HTTPS traffic, use the company CA bundle supplied by
+your IT team (PEM format):
+
+```bash
+export NODE_EXTRA_CA_CERTS=/absolute/path/company-ca.pem
+lightcode
+```
+
+`LIGHTCODE_CA_CERTS` and `SSL_CERT_FILE` are also supported for Lightcode's
+provider, model catalog, connectivity probe, and web-tool requests. Explicit
+bundles extend the public trust roots using
+[Bun's TLS fetch options](https://bun.sh/docs/runtime/networking/fetch).
+Certificate verification remains enabled. Untrusted, expired, and mismatched
+certificates report an actionable error instead of triggering repeated chat
+retries. Restart Lightcode after changing network configuration. Subprocesses
+and external MCP programs use their own runtime's certificate settings; use
+`NODE_EXTRA_CA_CERTS` when those runtimes support it.
+
+OpenAI-compatible endpoints can run without an API key, including local model
+servers. Supply their `/v1` base URL and exact model ID. Model compatibility
+still depends on the endpoint implementing the supported API and the model
+being capable of tool use; an arbitrary model name alone cannot guarantee that.
+
 ## Context optimization
 
 Long sessions stay healthy through three tiers: real-usage-calibrated token
@@ -118,18 +162,30 @@ description: Write a clear PR title and description from the diff.
 # Instructions the agent follows when this skill is loaded…
 ```
 
-Lightcode discovers skills from three locations, first match wins (project
-overrides user):
+Lightcode discovers installed skills automatically, first match wins (project
+overrides user), in this order:
 
 1. `.lightcode/skills/<name>/SKILL.md` — project-local
 2. `.agents/skills/<name>/SKILL.md` — project-local (fallback)
-3. `~/.lightcode/skills/<name>/SKILL.md` — available in every project
+3. Project `.claude/skills`, `.codex/skills`, and `.opencode/skills`
+4. User `~/.lightcode/skills`, `~/.agents/skills`, and `~/.claude/skills`
+5. `$CODEX_HOME/skills` (defaults to `~/.codex/skills`, including `.system`)
+6. `$XDG_CONFIG_HOME/opencode/skills` (defaults to `~/.config/opencode/skills`)
+7. Additional roots in `LIGHTCODE_SKILL_PATHS` (colon-separated on Unix,
+   semicolon-separated on Windows). Use this for other installations or
+   plugin skill directories you want to make available.
 
 Each turn the agent is told which skills are available (name + description), so
 just ask it to "use the pr-description skill" (or mention the skill by name) and
 it loads the instructions via the `skill` tool and follows them. Run `/skills`
-in the TUI to list what's installed. Only simple `key: value` frontmatter lines
-are parsed (`name`, `description`); the rest of the file is the instruction body.
+in the TUI to list what's installed. The agent can select relevant skills for
+ordinary tasks without you naming one. YAML frontmatter supports quoted and
+multiline `name`/`description` fields. Supporting files can be loaded through
+the `skill` tool's `resource` argument, relative to the skill directory.
+Discovery follows installation symlinks, skips broken/unreadable/malformed
+entries, and refreshes within 30 seconds. Scans are bounded to eight directory
+levels and 2,000 directories per root; individual files are limited to 1 MiB.
+Discovery does not execute skill scripts or override tool permissions.
 
 ## Workspaces
 

package/assets/web/geist-LICENSE.txt

@@ -0,0 +1,93 @@
+Copyright 2024 The Geist Project Authors (https://github.com/vercel/geist-font) Geist-Italic[wght].ttf: Copyright 2024 The Geist Project Authors (https://github.com/vercel/geist-font)
+
+This Font Software is licensed under the SIL Open Font License, Version 1.1.
+This license is copied below, and is also available with a FAQ at:
+http://scripts.sil.org/OFL
+
+
+-----------------------------------------------------------
+SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
+-----------------------------------------------------------
+
+PREAMBLE
+The goals of the Open Font License (OFL) are to stimulate worldwide
+development of collaborative font projects, to support the font creation
+efforts of academic and linguistic communities, and to provide a free and
+open framework in which fonts may be shared and improved in partnership
+with others.
+
+The OFL allows the licensed fonts to be used, studied, modified and
+redistributed freely as long as they are not sold by themselves. The
+fonts, including any derivative works, can be bundled, embedded,
+redistributed and/or sold with any software provided that any reserved
+names are not used by derivative works. The fonts and derivatives,
+however, cannot be released under any other type of license. The
+requirement for fonts to remain under this license does not apply
+to any document created using the fonts or their derivatives.
+
+DEFINITIONS
+"Font Software" refers to the set of files released by the Copyright
+Holder(s) under this license and clearly marked as such. This may
+include source files, build scripts and documentation.
+
+"Reserved Font Name" refers to any names specified as such after the
+copyright statement(s).
+
+"Original Version" refers to the collection of Font Software components as
+distributed by the Copyright Holder(s).
+
+"Modified Version" refers to any derivative made by adding to, deleting,
+or substituting -- in part or in whole -- any of the components of the
+Original Version, by changing formats or by porting the Font Software to a
+new environment.
+
+"Author" refers to any designer, engineer, programmer, technical
+writer or other person who contributed to the Font Software.
+
+PERMISSION & CONDITIONS
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Font Software, to use, study, copy, merge, embed, modify,
+redistribute, and sell modified and unmodified copies of the Font
+Software, subject to the following conditions:
+
+1) Neither the Font Software nor any of its individual components,
+in Original or Modified Versions, may be sold by itself.
+
+2) Original or Modified Versions of the Font Software may be bundled,
+redistributed and/or sold with any software, provided that each copy
+contains the above copyright notice and this license. These can be
+included either as stand-alone text files, human-readable headers or
+in the appropriate machine-readable metadata fields within text or
+binary files as long as those fields can be easily viewed by the user.
+
+3) No Modified Version of the Font Software may use the Reserved Font
+Name(s) unless explicit written permission is granted by the corresponding
+Copyright Holder. This restriction only applies to the primary font name as
+presented to the users.
+
+4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
+Software shall not be used to promote, endorse or advertise any
+Modified Version, except to acknowledge the contribution(s) of the
+Copyright Holder(s) and the Author(s) or with their explicit written
+permission.
+
+5) The Font Software, modified or unmodified, in part or in whole,
+must be distributed entirely under this license, and must not be
+distributed under any other license. The requirement for fonts to
+remain under this license does not apply to any document created
+using the Font Software.
+
+TERMINATION
+This license becomes null and void if any of the above conditions are
+not met.
+
+DISCLAIMER
+THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
+OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
+OTHER DEALINGS IN THE FONT SOFTWARE.