@kmugalkhod/lightcode 0.16.0 → 0.17.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -105,6 +105,39 @@ TUI lists every OpenRouter model and persists the choice to
105
105
  probes the provider endpoint, and daily JSONL logs live under the Lightcode
106
106
  data directory (`logs/`).
107
107
 
108
+ ## Office networks and certificates
109
+
110
+ Lightcode uses the same standard enterprise configuration described in
111
+ [OpenCode's network documentation](https://opencode.ai/docs/network/):
112
+ `HTTPS_PROXY`, `HTTP_PROXY`, `NO_PROXY`, and `NODE_EXTRA_CA_CERTS`.
113
+ Local CLI/server connections bypass the proxy automatically.
114
+ The npm launcher on Windows also imports trusted roots from both LocalMachine
115
+ and CurrentUser stores when no explicit CA file is configured. Its export is
116
+ isolated per launch and limited to ten seconds.
117
+
118
+ If your office inspects HTTPS traffic, use the company CA bundle supplied by
119
+ your IT team (PEM format):
120
+
121
+ ```bash
122
+ export NODE_EXTRA_CA_CERTS=/absolute/path/company-ca.pem
123
+ lightcode
124
+ ```
125
+
126
+ `LIGHTCODE_CA_CERTS` and `SSL_CERT_FILE` are also supported for Lightcode's
127
+ provider, model catalog, connectivity probe, and web-tool requests. Explicit
128
+ bundles extend the public trust roots using
129
+ [Bun's TLS fetch options](https://bun.sh/docs/runtime/networking/fetch).
130
+ Certificate verification remains enabled. Untrusted, expired, and mismatched
131
+ certificates report an actionable error instead of triggering repeated chat
132
+ retries. Restart Lightcode after changing network configuration. Subprocesses
133
+ and external MCP programs use their own runtime's certificate settings; use
134
+ `NODE_EXTRA_CA_CERTS` when those runtimes support it.
135
+
136
+ OpenAI-compatible endpoints can run without an API key, including local model
137
+ servers. Supply their `/v1` base URL and exact model ID. Model compatibility
138
+ still depends on the endpoint implementing the supported API and the model
139
+ being capable of tool use; an arbitrary model name alone cannot guarantee that.
140
+
108
141
  ## Context optimization
109
142
 
110
143
  Long sessions stay healthy through three tiers: real-usage-calibrated token
@@ -129,18 +162,30 @@ description: Write a clear PR title and description from the diff.
129
162
  # Instructions the agent follows when this skill is loaded…
130
163
  ```
131
164
 
132
- Lightcode discovers skills from three locations, first match wins (project
133
- overrides user):
165
+ Lightcode discovers installed skills automatically, first match wins (project
166
+ overrides user), in this order:
134
167
 
135
168
  1. `.lightcode/skills/<name>/SKILL.md` — project-local
136
169
  2. `.agents/skills/<name>/SKILL.md` — project-local (fallback)
137
- 3. `~/.lightcode/skills/<name>/SKILL.md` — available in every project
170
+ 3. Project `.claude/skills`, `.codex/skills`, and `.opencode/skills`
171
+ 4. User `~/.lightcode/skills`, `~/.agents/skills`, and `~/.claude/skills`
172
+ 5. `$CODEX_HOME/skills` (defaults to `~/.codex/skills`, including `.system`)
173
+ 6. `$XDG_CONFIG_HOME/opencode/skills` (defaults to `~/.config/opencode/skills`)
174
+ 7. Additional roots in `LIGHTCODE_SKILL_PATHS` (colon-separated on Unix,
175
+ semicolon-separated on Windows). Use this for other installations or
176
+ plugin skill directories you want to make available.
138
177
 
139
178
  Each turn the agent is told which skills are available (name + description), so
140
179
  just ask it to "use the pr-description skill" (or mention the skill by name) and
141
180
  it loads the instructions via the `skill` tool and follows them. Run `/skills`
142
- in the TUI to list what's installed. Only simple `key: value` frontmatter lines
143
- are parsed (`name`, `description`); the rest of the file is the instruction body.
181
+ in the TUI to list what's installed. The agent can select relevant skills for
182
+ ordinary tasks without you naming one. YAML frontmatter supports quoted and
183
+ multiline `name`/`description` fields. Supporting files can be loaded through
184
+ the `skill` tool's `resource` argument, relative to the skill directory.
185
+ Discovery follows installation symlinks, skips broken/unreadable/malformed
186
+ entries, and refreshes within 30 seconds. Scans are bounded to eight directory
187
+ levels and 2,000 directories per root; individual files are limited to 1 MiB.
188
+ Discovery does not execute skill scripts or override tool permissions.
144
189
 
145
190
  ## Workspaces
146
191
 
@@ -0,0 +1,93 @@
1
+ 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)
2
+
3
+ This Font Software is licensed under the SIL Open Font License, Version 1.1.
4
+ This license is copied below, and is also available with a FAQ at:
5
+ http://scripts.sil.org/OFL
6
+
7
+
8
+ -----------------------------------------------------------
9
+ SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
10
+ -----------------------------------------------------------
11
+
12
+ PREAMBLE
13
+ The goals of the Open Font License (OFL) are to stimulate worldwide
14
+ development of collaborative font projects, to support the font creation
15
+ efforts of academic and linguistic communities, and to provide a free and
16
+ open framework in which fonts may be shared and improved in partnership
17
+ with others.
18
+
19
+ The OFL allows the licensed fonts to be used, studied, modified and
20
+ redistributed freely as long as they are not sold by themselves. The
21
+ fonts, including any derivative works, can be bundled, embedded,
22
+ redistributed and/or sold with any software provided that any reserved
23
+ names are not used by derivative works. The fonts and derivatives,
24
+ however, cannot be released under any other type of license. The
25
+ requirement for fonts to remain under this license does not apply
26
+ to any document created using the fonts or their derivatives.
27
+
28
+ DEFINITIONS
29
+ "Font Software" refers to the set of files released by the Copyright
30
+ Holder(s) under this license and clearly marked as such. This may
31
+ include source files, build scripts and documentation.
32
+
33
+ "Reserved Font Name" refers to any names specified as such after the
34
+ copyright statement(s).
35
+
36
+ "Original Version" refers to the collection of Font Software components as
37
+ distributed by the Copyright Holder(s).
38
+
39
+ "Modified Version" refers to any derivative made by adding to, deleting,
40
+ or substituting -- in part or in whole -- any of the components of the
41
+ Original Version, by changing formats or by porting the Font Software to a
42
+ new environment.
43
+
44
+ "Author" refers to any designer, engineer, programmer, technical
45
+ writer or other person who contributed to the Font Software.
46
+
47
+ PERMISSION & CONDITIONS
48
+ Permission is hereby granted, free of charge, to any person obtaining
49
+ a copy of the Font Software, to use, study, copy, merge, embed, modify,
50
+ redistribute, and sell modified and unmodified copies of the Font
51
+ Software, subject to the following conditions:
52
+
53
+ 1) Neither the Font Software nor any of its individual components,
54
+ in Original or Modified Versions, may be sold by itself.
55
+
56
+ 2) Original or Modified Versions of the Font Software may be bundled,
57
+ redistributed and/or sold with any software, provided that each copy
58
+ contains the above copyright notice and this license. These can be
59
+ included either as stand-alone text files, human-readable headers or
60
+ in the appropriate machine-readable metadata fields within text or
61
+ binary files as long as those fields can be easily viewed by the user.
62
+
63
+ 3) No Modified Version of the Font Software may use the Reserved Font
64
+ Name(s) unless explicit written permission is granted by the corresponding
65
+ Copyright Holder. This restriction only applies to the primary font name as
66
+ presented to the users.
67
+
68
+ 4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
69
+ Software shall not be used to promote, endorse or advertise any
70
+ Modified Version, except to acknowledge the contribution(s) of the
71
+ Copyright Holder(s) and the Author(s) or with their explicit written
72
+ permission.
73
+
74
+ 5) The Font Software, modified or unmodified, in part or in whole,
75
+ must be distributed entirely under this license, and must not be
76
+ distributed under any other license. The requirement for fonts to
77
+ remain under this license does not apply to any document created
78
+ using the Font Software.
79
+
80
+ TERMINATION
81
+ This license becomes null and void if any of the above conditions are
82
+ not met.
83
+
84
+ DISCLAIMER
85
+ THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
86
+ EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
87
+ MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
88
+ OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
89
+ COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
90
+ INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
91
+ DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
92
+ FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
93
+ OTHER DEALINGS IN THE FONT SOFTWARE.
Binary file