litgravity
Add one word, `lit`, to an Antigravity CLI (agy) prompt and get a planned, tested, reviewed workflow, plus a handoff note for the next session. Formerly antigravity-swarm.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/wjgoarxiv/litgravity with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/wjgoarxiv/litgravity'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/wjgoarxiv--litgravity)HTML
<a href="/listings/wjgoarxiv--litgravity"><img src="/api/listings/wjgoarxiv--litgravity/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
You need Node.js 20 or newer and the Antigravity CLI, signed in once. In a terminal, run:
npx @litfamily/litgravity install
The installer shows every destination first. By default it copies the plugin to `~/.gemini/config/plugins/litgravity`, so LitGravity is available in every project; `--scope project` copies it to `./.agents/plugins/litgravity` for one project. It validates the plugin with `agy plugin validate` before and after copying. agy loads a plugin's hooks, skills and agents without a trust step, so there is nothing to approve. Then check the result:
npx @litfamily/litgravity doctor
`doctor` lists the installed copy, the validation result, the six hook events and a smoke run of each hook script, every skill and agent, every engine with its pre-warm command, the host programs the skills call, and the Python the engines will use. It ends with `LitGravity: ready` when nothing is broken.
Useful switches: `--dry-run` previews and writes nothing; `--yes` lets an agent or CI shell install (a shell without a terminal otherwise only previews); `--status-line` adds the optional LitGravity status line to agy's user settings (never on by default).
The status line is one row under the prompt, drawn in the LitFamily status-line style: the `[π₯LIT vβ¦]` mark, then every segment in LitGravity's flame orange. It reads `model [effort] β ctx [βββ] 42%/1049k β quota [ββ]28% β» 2h5m`, then the active lit route as a pink `π₯ LIT` chip with its clock, then where the route stands on its map (PIN, RED, GREEN, VERIFY, REVIEW, RECORD for the open criterion of litwork and lit-loop, read from its evidence files; interview, plan, work, review, done for planning and start-work, with the plan's rows), the lanes of a lit-team, and whatever agy also reports: cost, background tasks, the branch and the title. The context and quota gauges turn yellow at 70% and red at 90%. On a narrow terminal the extras go first and the route and the context gauge stay. `NO_COLOR` turns colour off and `LITGRAVITY_HUD_ASCII=1` keeps every glyph ASCII. If agy already shows another status line, the installer refuses to touch it; `install --status-line --replace-status-line` swaps it after saving the old value, and `uninstall` puts that value back.
Let a coding agent install it
Paste this into a coding agent opened in any folder:
Install LitGravity, the LitFamily plugin for Google's Antigravity CLI. Use only the official npm package @litfamily/litgravity. Show me your plan and wait for my yes before changing anything. 1. Check that Node.js 20+ and agy are on PATH (`agy --version`). 2. Preview: npx @litfamily/litgravity install --dry-run 3. Install: npx @litfamily/litgravity install --yes 4. Verify: npx @litfamily/litgravity doctor and report its last line. 5. Tell me what was written (the installer prints a "Written:" list) and anything it refused.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md Β· README Β· 297 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- <p align="center"><picture><source media="(prefers-reduced-motion: reduce)" srcset="./docs/assets/cover-motion-still.webp" /><source media="(prefers-reduced-motion: no-preference)" srcset="./docs/assets/cover-motion.webp" /><img src="./docs/assets/cover.webp" width="100%" alt="LitFamily cover: seven armored machines stand in their bays, and the LitGravity machine in the seventh bay, gyroscope rings around a dark spherical head, wakes with orange cores in its head and chest and a lit frame, under LITFAMILY and KEEP THE WORK LIT." /></picture></p>
- <h1 align="center">LitGravity</h1>
- <p align="center"><strong>Keep the work lit.</strong></p>
- <p align="center">LitGravity gives Google's Antigravity CLI (<code>agy</code>) the habit of planning before it edits, checking what it built, and leaving a handoff, so the next conversation starts where this one stopped. One npm command installs it as an agy plugin.</p>
- <p align="center">
- <a href="https://www.npmjs.com/package/@litfamily/litgravity"><img src="https://img.shields.io/npm/v/@litfamily/litgravity?color=FF6337&label=npm" alt="npm version" /></a>
- <a href="https://www.npmjs.com/package/@litfamily/litgravity"><img src="https://img.shields.io/npm/dm/@litfamily/litgravity?color=D7F75B" alt="npm downloads per month" /></a>
- <a href="./LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue" alt="MIT license" /></a>
- <a href="https://github.com/wjgoarxiv/litgravity/stargazers"><img src="https://img.shields.io/github/stars/wjgoarxiv/litgravity?style=flat" alt="GitHub stars" /></a>
- </p>
- <p align="center"><a href="#install"><img src="./docs/assets/readme/icon-book.svg" width="16" alt="" /> Install</a> <a href="#demo"><img src="./docs/assets/readme/icon-play.svg" width="16" alt="" /> Demo</a> <a href="#safety-and-uninstall"><img src="./docs/assets/readme/icon-shield.svg" width="16" alt="" /> Update & remove</a> <a href="#quick-start">Quick start</a> <a href="#what-you-can-make">What you can make</a> <a href="#what-you-get">What you get</a> <a href="#what-agy-limits-today">agy limits</a> <a href="./README_ko-KR.md">νκ΅μ΄</a></p>
- > [!TIP]
- > One npm command installs LitGravity as an agy plugin ([Install](#install)). Then start any agy prompt with `lit`, as [Quick start](#quick-start) shows.
- ## Demo
- What ignition looks like, captured from the real hook and status line on this Mac: the typed prompt, the injected route note, and the status line carrying the lit-loop map.
- <!-- demo-gif --><p align="center"><img src="./docs/assets/litgravity/demo-ignition.webp" width="960" alt="Terminal capture. The prompt reads lit add a --shout flag that prints the greeting in capitals, with a test. The hook answers with the LIT mark and LIT IGNITED Β· lit-loop, names the lit-loop skill file to read first, and notes that tool events go to the conversation ledger. Below, the status line shows the model, the context gauge at 42 percent, the lit-loop chip with its clock, and the PIN through RECORD map with PIN lit." /></p>
- ## Quick start
- 1. [Install LitGravity](#install), then open agy in a project. Type `/skills` to see the LitGravity skills and `/hooks` to see the plugin's hooks.
- 2. Start a prompt with `lit`. The word after it picks the route, as the table below shows.
- 3. Approve a plan, then `lit start plans/<slug>.md` builds it row by row with tests.
- 4. Before you stop, `lit handoff`. Next time, `lit recap` reads where you were.
- ```text
- you type lit plan a tiny todo app
- it does reads the plan skill, explores the repo, writes plans/todo-app.md with ordered tasks and checks
- it ends "Plan saved. Run `lit start plans/todo-app.md` when you are happy with it."
- ```
- | You type | What happens |
- |---|---|
- | `lit` | Runs the default loop, or picks up a plan you started with `lit start` |
- | `lit` while its route is already active | A short "continues" note |
- | `lit plan`, `lit review`, `lit research`, `lit debug`, `lit handoff`, `lit recap`, `lit brainstorm`, `lit korean` | Picks that route |
- | `lit <other route>` | Switches |
- | Any skill id as that word (`lit debugging`, `lit structural-search`) | Runs that skill; `/litgravity:<skill-id>` does the same as a slash command |
- | `lit new` | Starts over |
- `npx @litfamily/litgravity list` prints every skill with the words that reach it.
- ## What you can make
- Each picture is a real output made on this Mac. The `lit-adhd` brief was drawn by its collector over three real agy conversations; the others were made by each skill's own engine from the skill's worked example. The deck, the P&ID, the schematics and the film come from skills that now live in wjgoarxiv-skills (see [Extensions](#extensions)); install those extensions and agy makes them the same way.
- | Picture | Skill | What it shows |
- |---|---|---|
- | <img src="./docs/assets/litgravity/showcase/deck-themes.webp" width="480" alt="The same Korean deck about a logistics platform in four tonalities: a dark night cover with an amber year, a navy cover with four KPI figures, a cobalt cover on cream, and a teal cover; below each, the matching chart slide with a native bar chart of monthly shipments, two bullet takeaways and a data table." /> | `lit-pptx` | One deck in four of its tonalities. Charts and KPI rows stay native and editable, Pretendard is embedded, and each deck passed the gate for overflow, contrast and empty slides. |
- | <img src="./docs/assets/litgravity/showcase/pid-dosing-skid.webp" width="480" alt="P&ID of a sodium hypochlorite dosing skid on a framed sheet: a storage tank TK-101 with level transmitter and alarm, duty and standby metering pumps P-101A and P-101B behind filters and check valves, a relief valve PSV-101 back to the tank, a flow loop FE-101, FT-101 and FIC-101 signalling the pump, a legend, notes and a title block." /> | `lit-schematic` | A P&ID with ISA-5.1 tags, line numbers, a legend and a title block. Its checker passed: no text on a line, no line through a symbol, no loose end. |
- | <img src="./docs/assets/litgravity/showcase/schematics.webp" width="480" alt="Two drawings side by side: an isometric cutaway of a shell-and-tube heat exchanger with copper tube bundle, baffles and saddle supports, each part labelled; and a journal-style two-panel figure of an adsorption rig, panel a a flow diagram with gas cylinders, mass flow controllers, an oven column and a mass spectrometer, panel b the column itself with adsorbent bed and thermocouples." /> | `lit-schematic` | The same skill drawing equipment as an isometric cutaway and as a two-panel figure for a paper. |
- | <img src="./docs/assets/litgravity/showcase/motion-film.webp" width="480" alt="Four frames of a 12-second film in one dark house style: a ring drawing on beside the Korean line μκ² μμν΄μ λκΉμ§, a bar chart beside One clock for every frame, a line through points beside ν νλ©΄μ ν κ°μ§ μκ°, and a grid of teal and amber tiles over Same house, every film." /> | `lit-typographic-motion` | Four frames of a 12-second film from a one-line Korean request. The skill wrote a treatment first, rendered it frame by frame with a sound bed, and its gate checked flashes, legibility and the loop. |
- | <img src="./docs/assets/litgravity/showcase/adhd-brief-en.webp" width="480" alt="The lit adhd brief in a dark chat pane: a headline counting three sessions, two active cards for a P&ID and a landing page with what each wrote and its next step, a table row for an ended deck session, a roadmap line, and a box with the recommended next step." /> | `lit-adhd` | Type `lit adhd` after a scattered day for a KPI board. `lit adhd detail` adds the per-session brief shown here. |
- The lit-adhd board shows the one thing to do now and exactly what to type, done and remaining milestones with progress bars, and reminders shaped as `thing β what to do`. The reminders cover a conversation waiting on you, uncommitted changes, lanes still running and a plan left for a week.
- ## Install
- You need Node.js 20 or newer and the Antigravity CLI, signed in once. Run from any folder, and the check ends with `LitGravity: ready` when nothing is broken:
- ```bash
- npx @litfamily/litgravity install
- npx @litfamily/litgravity doctor
- ```
- To update later, run the same `install` again; [Safety and uninstall](#safety-and-uninstall) lists every lifecycle command. To let a coding agent do the install, paste the prompt in the [reference](./docs/reference.md#let-a-coding-agent-install-it).
- The installer shows every destination first and validates the plugin with `agy plugin validate` before and after copying. agy loads a plugin's hooks, skills and agents without a trust step, so there is nothing to approve. By default the plugin goes to `~/.gemini/config/plugins/litgravity`, so LitGravity is available in every project.
- | Switch | What it does |
- |---|---|
- | `--scope project` | Copies to `./.agents/plugins/litgravity` for one project |
- | `--dry-run` | Previews and writes nothing |
- | `--yes` | Installs from a shell without a terminal (agent, CI), which otherwise only previews |
- | `--no-agent-file` | Skips the global rule file for one run |
- | `--status-line` | Adds the opt-in status line to agy's user settings, after a backup |
- Every user-scope install also leaves one owned rule file at `~/.gemini/config/rules/litgravity.md`, because agy reads that folder at every session start. The rule stays short on purpose (the lit activation word, where plans and handoffs live, and the release freeze), so the ground rules hold before any skill loads. An interactive install asks first and a No stores the rule off, while `--yes` adds it; the [lifecycle table](#safety-and-uninstall) turns it off later or adds a project block.
- `doctor` lists the installed copy, the validation result, the six hook events and a smoke run of each hook script, the global rule file, every skill and agent, the extensions with their install line, any old engine cache or stray saved copy, and the host programs the skills call.
- The installer writes in a few places outside your project, and the map shows them. If the destination is a symlink, someone else's folder, or a copy you edited, it stops with `No files written.`; otherwise it copies the plugin, then writes the rule file and a small receipt. Everything else LitGravity leaves on disk is written later by your conversations, and the installer never changes your extension copies (it only reads the skill folders to tell you, once, when `extensions check` has something to show).
- <p align="center">
- <picture>
- <source media="(prefers-color-scheme: dark)" srcset="./docs/assets/litgravity/diagrams/install-map.en.dark.png">
- <img src="./docs/assets/litgravity/diagrams/install-map.en.light.png" width="900" alt="Flowchart of litgravity install. Plan printed, then a destination check: a symlinked, foreign or edited destination stops the install with No files written and, for an edited copy, a command that moves it to saved/. A new or LitGravity-owned destination goes on to agy plugin validate, then copy and validate again into the plugin folder ~/.gemini/config/plugins/litgravity, or ./.agents/plugins/litgravity at project scope. The last step writes the global rule file ~/.gemini/config/rules/litgravity.md, records receipt.json, backups/ and saved/ under ~/.local/share/litgravity/, and changes ~/.gemini/antigravity-cli/settings.json only with --status-line. Below, two bands: written later by conversations (~/.local/state/litgravity/, plans/, .litgravity/ with ledger, handoff and goals) and left alone by the installer (~/.gemini/config/skills/<id> extension copies and agy credential files).">
- </picture>
- </p>
- <p align="center"><img src="./docs/assets/litgravity/install-doctor.webp" width="960" alt="Terminal capture. The install command ends with Status: Ready, and the doctor command ends with LitGravity: ready after thirty passing checks." /></p>
- ## What you get
- A lit turn runs the same routine through these parts. A bigger change gets a written plan first, the work is built row by row with tests under a goal record that outlives one conversation, and a second look reviews it before anything merges. Research shows its sources, documents and prose read clean, and the turn ends with a handoff the next conversation reads.
- | Part | Contents | Role |
- |---|---|---|
- | 42 skills | 33 dense agy skills with their references and scripts, plus 9 stubs for moved skills | Plan, build, check, research, write, hand off |
- | 11 agents | Child agents agy starts under their type names | Plan, execute, verify, review, Korean prose |
- | 6 hooks | Run at session start, each turn, each tool call, and the stop gate | Route `lit`, hold unfinished turns, ledger every tool |
- agy loads only the first 24,000 bytes of a `SKILL.md`, so each of the 33 dense skills, read on demand, keeps its references, scripts and templates in its own folder, with the long material in `references/` and the skill naming the file to open. The skill groups are loop and goals, ideas and planning, building, review and cleanup, research and knowledge, teams, prose, continuity and guidance, and tools, plus the nine stubs of the moved families (see [Extensions](#extensions)).
- - **Host programs.** The skills call programs already on your machine: Python 3, Chrome or Chromium for browser work, ast-grep, ripgrep and the language checkers that `lsp` drives. `doctor` names what is missing and the command that installs it; LitGravity never installs software globally.
- - **Agents.** agy starts them with `invoke_subagent` under their type name: lit-planner, lit-executor, lit-verifier, qa-runner, quality-reviewer, librarian-researcher, and five Korean prose agents (korean-style-analyzer, korean-prose-editor, meaning-preservation-auditor, native-flow-reviewer, polish-orchestrator). Reviewers and the Korean agents get read and search tools only.
- - **Models.** `npx @litfamily/litgravity models` lists the models and effort tiers your agy offers, read from agy itself, so a model Google adds later shows up with no LitGravity update.
- <details>
- <summary>The six hook events</summary>
- - SessionStart adds the LitGravity route list, the newest handoff note (cut to 6,000 characters) and an update notice, once per new conversation. An update notice or the `lit adhd` nudge is not repeated in a project that already saw it (`.litgravity/shown/notices.jsonl`).
- - Stop saves `.litgravity/handoff/auto.md` at every turn end of a conversation a lit route has touched: the last request, the plan row that is next, the open goal criterion and the tail of the last reply. This replaces the compaction event agy lacks. `LITGRAVITY_AUTO_HANDOFF=0` turns the save and the full-note carry off; SessionStart then points at `latest.md` as before.
- - PreInvocation is the `lit` router. agy has no prompt hook, so on the first model call of a turn the router reads the newest prompt from the transcript, applies the re-entry rule and injects one step that names the skill file to read.
- - PostInvocation and Stop run the checks that agy cannot run in advance (see [the limits](#what-agy-limits-today)). Stop also holds an unfinished turn, as [Held turns](#held-turns-and-the-ledger) describes.
- - PreToolUse refuses child agents that could write while lit-plan is active.
- - PostToolUse writes one ledger line per tool call while a route is active, in `.litgravity/ledger/<conversation>.jsonl`, with key shapes redacted. A silent ledger means the hooks are not loaded.
- </details>
- ### The status line
- One row under the prompt shows where the work stands: the model and its effort tier, the context and quota gauges, the active route with its clock, and the map of that route with the current stage lit. The capture below is a real render from this Mac, before and after a `lit` prompt.
- <p align="center"><img src="./docs/assets/litgravity/status-states.webp" width="960" alt="Terminal capture of the status line. Before lit it shows the model and the context gauge at 42 percent. After lit it adds the lit-loop chip with its clock and the PIN through RECORD map with PIN lit." /></p>
- `--status-line` at install turns it on. Its segments, colours, plain-text form and the looks for `lit adhd`, YOUR TURN, review lanes and DONE are in the [reference](./docs/reference.md#the-status-line).
- ## Extensions
- LitGravity is the LitFamily core for agy, and it is complete on its own: planning, building, checking, research, handoffs and the `lit` router all ship in this package. The skills that make files (slides, Word documents, diagrams, schematics, figures, interfaces, films and README covers) each pull in their own engines, and together they used to be most of the package, while most people use one or two of them. They are now LitFamily extensions on one extension shelf, the wjgoarxiv-skills repository, where each skill has a folder written for agy.
- Everything on the left ships in the npm package, and the core needs nothing on the right to plan, build, check, research or hand off. Install the extensions you use alongside LitGravity for the full LitFamily experience; leave the rest out and nothing in the core is missing.
- <p align="center">
- <picture>
- <source media="(prefers-color-scheme: dark)" srcset="./docs/assets/litgravity/diagrams/core-extensions.en.dark.png">
- <img src="./docs/assets/litgravity/diagrams/core-extensions.en.light.png" width="900" alt="Two areas. Left, the LitGravity plugin: 33 core skills in nine groups (loop and goals, ideas and planning, building, review and cleanup, research and knowledge, teams, prose, continuity and guidance, tools), 11 agents, 6 hooks, and nine stubs that keep the old names: lit-pptx, lit-docx, lit-diagram-drawer, lit-schematic, lit-scientific-visualization, frontend-ui-ux, visual-qa, lit-typographic-motion and readme-studio. Right, wjgoarxiv-skills extensions in five families: decks, documents, figures, design and video-covers, each folder at variants/litgravity/<id>. An arrow labelled install <id> --yes runs from that folder to a card for litgravity extensions install with four numbered steps: check same-name skills and stop if any; move an old copy aside, whole, to ~/.gemini/extension-backups/<date>/; copy into the emptied folder; write a receipt inside the copy. An arrow labelled new copy + receipt runs on to agy user skills at ~/.gemini/config/skills/<id>, which answers as /<id>. Another arrow labelled if installed runs from the stubs to the same place. Below it, a card lists the other verbs, list, check, update, remove and prune-backups, each a plan only until --yes, and a note says that when the extension is not installed, the stub gives this command and the four hand lines and makes nothing.">
- </picture>
- </p>
- | Family in wjgoarxiv-skills | Extensions |
- |---|---|
- | `decks` | `lit-pptx` |
- | `documents` | `lit-docx` |
- | `figures` | `lit-diagram-drawer`, `lit-schematic`, `lit-scientific-visualization` |
- | `design` | `frontend-ui-ux`, `visual-qa` |
- | `video-covers` | `lit-typographic-motion`, `readme-studio` |
- LitGravity keeps a short stub under each extension's old name, so `lit deck β¦`, `lit motion β¦`, `/litgravity:lit-pptx` and the rest still land somewhere useful. The stub hands the turn to your installed copy, or, when the extension is not installed yet, gives you the lines that install it and makes nothing. The installer says the same after every install or update, and the first agy conversation after it mentions it once.
- The easiest way in is LitGravity's own `extensions` command. Every verb that changes anything prints its plan first and waits for `--yes`, so you can read exactly which folder moves where before it happens:
- ```bash
- npx @litfamily/litgravity extensions install lit-pptx # the plan only
- npx @litfamily/litgravity extensions install lit-pptx --yes # do it (--project: this workspace only)
- ```
- | Verb | What it does |
- |---|---|
- | `install` | Backs up any old copy, then copies in the new one and its receipt |
- | `list` | Shows each as installed (with receipt), not installed, receipt-less, or shadowed by a same-name skill |
- | `update` | Fetches the source and reinstalls only the ones whose files changed |
- | `remove` | Moves its own copy into the backups; a folder without a receipt is yours, so it refuses |
- | `check` | Changes nothing; prints one fix line per duplicate, receipt-less copy or missing source |
- | `prune-backups` | Shows the backups with their sizes and deletes them only with `--yes` |
- A few rules keep the command safe and easy to drive:
- - **Same-name check.** Before copying, `install` looks in every folder agy loads and stops with the path of any skill sharing the name. Your skill is never moved, and `--allow-shadow` installs anyway with a warning.
- - **Backups.** An existing copy at the destination goes whole into a dated folder under `~/.gemini/extension-backups/` before the new copy goes in.
- - **Source.** It keeps its own shallow clone of just the agy folders of wjgoarxiv-skills in `~/.cache/litgravity/extensions-src` (or reads a clone you already have with `--from <path>`), so there is nothing to clone by hand.
- - **Several at once.** `--family <name>` and `--all` pick several. `npx @litfamily/litgravity extensions help` has the details, and `doctor` runs `check` and prints its summary.
- Start a new conversation (or type `/skills reload`), and the skill answers as `/<id>`. To install by hand, the [reference](./docs/reference.md#install-an-extension-by-hand) gives the four shell lines, the workspace-only version, and how to update and remove a copy.
- ## How a lit turn runs
- agy still runs the conversation and picks the model. LitGravity adds a routine in plain files you can read, so you stop re-explaining where you were and checking by hand what really works:
- | What agy does | What lit adds |
- |---|---|
- | Starts fast from one typed line | A plan in `plans/` before the first edit |
- | Forgets the last conversation once a long one fills its context | A handoff in `.litgravity/` the next turn reads |
- | Calls it done when the model says so | Checks against the plan, marks the unchecked as unverified |
- <p align="center">
- <picture>
- <source media="(prefers-color-scheme: dark)" srcset="./docs/assets/litgravity/diagrams/lit-route.en.dark.png">
- <img src="./docs/assets/litgravity/diagrams/lit-route.en.light.png" width="900" alt="Flowchart of one lit turn in agy. You type lit plan a tiny todo app. The PreInvocation hook reads the prompt from the transcript and injects one step: read lit-plan/SKILL.md. After the model call, the PreToolUse hook checks invoke_subagent and may start one of 11 child agent types, only read-only ones during lit-plan. After each tool call, the PostToolUse hook appends a line to .litgravity/ledger/<conversation>.jsonl. The PostInvocation hook runs boundary and prose checks and tells the model to undo changes outside plans/, at most twice per turn. The Stop hook asks whether work is left open: held, the turn continues for up to three holds and pause releases it; released, the turn ends. Below, the next turns: lit start on plans/<slug>.md, lit review with five lanes (goal, qa, quality, security, context), lit handoff writing .litgravity/handoff/latest.md, and the SessionStart hook pointing the next conversation to that note.">
- </picture>
- </p>
- agy gives a plugin no hook on the prompt itself, so the PreInvocation hook steers from the first model call and the other hooks each watch one moment of the turn. Each moment leaves a file you can open afterwards (the plan, the ledger, the handoff note), and the next turns pick up from those files:
- - **`lit start`** builds the plan, checked with tests and a look at the real surface. Whatever nobody could check is marked as unverified.
- - **`lit review`** checks the result in five lanes.
- - **`lit handoff`** writes `.litgravity/handoff/latest.md` with what was built, how it was checked and what is left. The SessionStart hook of your next conversation points to it.
- ### What a planning turn may do
- `lit plan` turns are planning only. Most of that is asked, then checked afterwards, because agy offers no safe way to stop a write before it happens (see [the limits](#what-agy-limits-today)):
- - The router tells the model to write only under `plans/` and `.litgravity/` and to keep the shell to plain read-only commands. Your own approval prompts still decide whether a write or command runs.
- - After every model call and at the end of the turn, the boundary check compares the workspace with its state at the start of the turn. A file changed or removed outside `plans/` is reported and the model is asked to undo it, at most twice per turn. A command that changed nothing on disk leaves no trace for this check.
- - Child agents are refused before they start unless they are read-only: lit-planner, librarian-researcher, lit-verifier, quality-reviewer and the Korean prose agents.
- Route state lives outside the project, under `~/.local/state/litgravity/`, away from the files a planning turn is asked to touch. If that state is damaged, the child-agent limit and the plan gate stay on; if it goes missing, the hooks fall back to the route journal kept beside it.
- ### Held turns and the ledger
- If you think in process plants, here is the same routine as one. Your prompt is the feed, the PreInvocation router is the header, and each route word opens the line to its vessel. I drew the stages as one train to keep it readable; in agy each of them is a separate `lit` prompt, usually in a later turn.
- <p align="center">
- <picture>
- <source media="(prefers-reduced-motion: reduce) and (prefers-color-scheme: dark)" srcset="./docs/assets/litgravity/schematic/lit-plant.en.dark.png">
- <source media="(prefers-reduced-motion: reduce)" srcset="./docs/assets/litgravity/schematic/lit-plant.en.png">
- <source media="(prefers-color-scheme: dark)" srcset="./docs/assets/litgravity/schematic/lit-plant-loop.en.dark.webp">
- <source media="(prefers-color-scheme: light)" srcset="./docs/assets/litgravity/schematic/lit-plant-loop.en.webp">
- <img src="./docs/assets/litgravity/schematic/lit-plant-loop.en.webp" width="900" alt="Process flow diagram of the lit workflow in agy. A lit prompt and the last handoff feed the PreInvocation router. A header runs along the top and drops into three vessels by route word: lit plan into lit-plan, lit start into start-work, lit review into review-work, and lit handoff into a lit-handoff unit. Between lit-plan and start-work, analyser AIC-101 (Stop: plan file yet?) drives a three-way valve that either releases the turn or sends it back; between start-work and review-work, AIC-102 (Stop: rows open?) does the same. Each vessel sends a sample line down to the PostToolUse ledger, .litgravity/ledger/<conversation>.jsonl. The lit-handoff unit sends latest.md off the sheet. A stream table lists, for each route, the skill, what leaves (plans/<slug>.md, plan rows ticked and tests run, findings with file:line first, .litgravity/handoff/latest.md) and whether the Stop hook holds it. In the animated version, dashes move along every stream.">
- </picture>
- </p>
- Every vessel bleeds a sample line into the ledger, and the handoff note leaves on the right for whichever conversation comes next. Between the vessels, the Stop hook's two analysers hold a turn while its work is open:
- | Route | Held at the end while |
- |---|---|
- | lit-plan | no `plans/<slug>.md` exists yet |
- | start-work | an approved plan has open rows |
- | litgoal, lit-loop | a goal record has an open criterion |
- A turn is held at most three times in a row without progress. Say `pause`, or write `BLOCKED at row N:`, `PAUSED at row N:` or `CANCELLED:` in the ledger, to release a hold. The capture below is the real hold from a planning turn that wrote nothing.
- <p align="center"><img src="./docs/assets/litgravity/handoff-hold.webp" width="960" alt="Terminal capture. After the prompt lit plan a tiny todo app with no plan file written, the Stop hook answers decision continue with the lit-plan gate reason asking for the plan file. A second block shows a ledger line recording a read_file tool call." /></p>
- ## What agy limits today
- These are the facts of agy 1.4.3, probed on a real install. LitGravity works inside them, and the [reference](./docs/reference.md#what-agy-limits-today-in-detail) gives each one in full.
- - **No blocking before a write.** agy's PreToolUse hook has to decide every call it sees, so LitGravity checks file changes and prose after the fact. The one hard stop is a child agent that could write during a lit-plan turn.
- - **Headless runs cannot ask.** In `agy -p`, a `run_command` or `write_file` that needs permission is denied and ends the run. The skills read first and report `BLOCKED` with the permission they need.
- - **Seeing images.** agy's model reads a PNG through `read_file`, and every look step in the visual skills relies on that.
- - **Starter Quota.** Every model call counts against your account's quota, so tests and probes use the free `agy plugin validate` and `/hooks`, `/skills`, `/agents`.
- - **No compaction event, no slash-command folder, no MCP server from a plugin here.** Handoff notes, skills as commands (`/litgravity:<skill-id>`) and script subcommands take their place.
- - **No lsp tool.** The `lsp` and `lsp-setup` skills drive language checkers from the command line instead.
- ## Safety and uninstall
- Every lifecycle command previews with `--dry-run`, and hooks fail open: if one breaks, your conversation continues. Files that conversations created in your projects (`plans/`, `.litgravity/`) stay where they are.
- | Task | Command |
- |---|---|
- | Install | `npx @litfamily/litgravity install` |
- | Update | `npx @litfamily/litgravity install` (validates, replaces in place) |
- | Global rule off or back on | `npx @litfamily/litgravity config agentFile off` (or `on`) |
- | Project block | `npx @litfamily/litgravity agent-file project --dir <path>` (writes only the marked block into the repo's `AGENTS.md`) |
- | Check | `npx @litfamily/litgravity doctor` |
- | Extensions | `npx @litfamily/litgravity extensions list` (then `install`, `update`, `remove`, `check`, `prune-backups`) |
- | Remove | `npx @litfamily/litgravity uninstall --yes` |
- The installer writes only its own plugin folder, its data directory, its rule file and, when you ask, the status line key, and it never reads agy's credential files.
- <details>
- <summary>What each part may write, and what it leaves</summary>
- - The installer writes only its own plugin folder, its data directory (`$XDG_DATA_HOME/litgravity`), the owned rule file in agy's global rules folder, and, when you ask, the status line key in agy's user settings, after a backup. It never reads agy's credential files. A rule file it did not write stops the install before the first write instead of being merged into.
- - A symlinked, foreign or edited destination stops the install before the first write. To keep an edited copy, the installer gives a command that moves it to `~/.local/share/litgravity/saved/<scope>-<date>`. That folder is outside agy's plugins folder on purpose: agy loads every folder it finds there, so a copy saved beside the plugin would run as a second LitGravity. `doctor` warns about any such leftover. `--dry-run` never mutates.
- - `extensions` writes only into agy's skill folder for the scope (`~/.gemini/config/skills/<id>` or `.agents/skills/<id>`), `~/.gemini/extension-backups/` and its own source clone in `~/.cache/litgravity/extensions-src`. Without `--yes` it only prints its plan. It never moves a same-name skill you keep elsewhere, never removes a folder without its receipt, and deletes only inside `~/.gemini/extension-backups/`, only with `prune-backups --yes`.
- - Releases up to 0.1.8 cached engines under `~/.local/share/litgravity/runtime/` (`$XDG_DATA_HOME/litgravity/runtime/`), and the cache can take 150 MB or more. Nothing reads or writes there now, the extensions included, and `uninstall` leaves it, so delete that folder to free the space; `doctor` names it while it is there.
- - Set `LITGRAVITY_HOOK_TRACE=<file>` before starting agy to log one line per hook call. It is off otherwise.
- </details>
- ## Reference
- [docs/reference.md](./docs/reference.md) keeps the material most readers need only once: [the status line](./docs/reference.md#the-status-line) in full, [a coding agent's install prompt](./docs/reference.md#let-a-coding-agent-install-it), [installing an extension by hand](./docs/reference.md#install-an-extension-by-hand), and [what agy limits today, in detail](./docs/reference.md#what-agy-limits-today-in-detail).
- ## Family
- LitGravity is one of the seven LitFamily packages. Each one brings the same way of working to a single coding agent, and each installs and runs on its own: install the one for the agent you use, and it needs none of the others. [LitFamily](https://github.com/wjgoarxiv/litfamily) lists all seven and the agent each one is for.
- The seven armored machines on the cover are those seven packages, and LitGravity is the orbit machine in the seventh bay. The cover is brand motion made with the LitFamily motion skill: drawn and animated artwork, with no agy session recorded in it. If your system asks for reduced motion, you see a still frame instead.
- <p align="center"><img src="./docs/assets/litfamily-machines.png" width="100%" alt="The seven LitFamily machines side by side, all lit: LitClaude, LitHermes, LitCodex, LitOpenCode, LitGrok, LitMuse and LitGravity, under LITFAMILY and KEEP THE WORK LIT." /></p>
- ## License
- MIT. See [LICENSE](./LICENSE).
- The LitGravity and LitFamily names and logos are covered by the [trademark policy](./TRADEMARK.md).
plugin/skills/lsp-setup/scripts/lsp-server-table.mjs Β· Bundled script Β· 192 lines Β· 1 finding marked
- // Hand-maintained table shared by detect-lsp.mjs and verify-lsp.mjs.
- //
- // language id used for references/<language>/README.md (c-cpp covers C and C++)
- // serverId/command the language-server launch line verify-lsp.mjs spawns over stdio. A wrong entry shows up as a
- // real roundtrip failure; the lines come from each server's published documentation.
- // extensions file extensions that select this entry (lower case, with the dot)
- // checkers one-shot CLI executables worth probing for this language (type checkers, linters, builders)
- // wired true when ../../lsp/scripts/diagnostics.mjs normalises this language's checker output
- // buildCheck the project command to cite as evidence when no checker is wired (the user's own build)
- // projectFiles config and manifest files whose presence is worth reporting ("*" is a wildcard)
- // install per-OS command the USER could run for the server (darwin, linux, win32). No script here
- // executes it. Commands age, so the package manager's own output is the final word.
- export const LANGUAGES = [
- { language: 'typescript', serverId: 'typescript', command: ['typescript-language-server', '--stdio'],
- extensions: ['.ts', '.tsx', '.js', '.jsx', '.mjs', '.cjs', '.mts', '.cts'],
- checkers: ['tsc', 'eslint'], wired: true, buildCheck: 'npx tsc --noEmit -p tsconfig.json',
- projectFiles: ['tsconfig.json', 'jsconfig.json', 'package.json'],
- install: {
- darwin: 'npm install --save-dev typescript@6 typescript-language-server (or: brew install typescript-language-server)',
- linux: 'npm install --save-dev typescript@6 typescript-language-server',
- win32: 'npm install --save-dev typescript@6 typescript-language-server',
- } },
- { language: 'python', serverId: 'basedpyright', command: ['basedpyright-langserver', '--stdio'],
- extensions: ['.py', '.pyi'], checkers: ['pyright', 'basedpyright', 'ruff', 'mypy'], wired: true,
- buildCheck: 'python3 -m pytest -q',
- projectFiles: ['pyrightconfig.json', 'pyproject.toml', 'ruff.toml', 'mypy.ini', 'setup.cfg'],
- install: {
- darwin: 'uv tool install basedpyright (or: brew install basedpyright)',
- linux: 'uv tool install basedpyright (or: pipx install basedpyright)',
- win32: 'uv tool install basedpyright (or: pip install basedpyright)',
- } },
- { language: 'go', serverId: 'gopls', command: ['gopls'], extensions: ['.go'],
- checkers: ['gopls', 'go'], wired: true, buildCheck: 'go vet ./...', projectFiles: ['go.mod', 'go.work'],
- install: {
- darwin: 'go install golang.org/x/tools/gopls@latest (or: brew install gopls)',
- linux: 'go install golang.org/x/tools/gopls@latest',
- win32: 'go install golang.org/x/tools/gopls@latest',
- } },
- { language: 'rust', serverId: 'rust', command: ['rust-analyzer'], extensions: ['.rs'],
- checkers: ['cargo', 'rustc'], wired: true, buildCheck: 'cargo check --all-targets',
- projectFiles: ['Cargo.toml', 'Cargo.lock', 'rust-toolchain.toml'],
- install: {
- darwin: 'rustup component add rust-analyzer rust-src (or: brew install rust-analyzer)',
- linux: 'rustup component add rust-analyzer rust-src',
- win32: 'rustup component add rust-analyzer rust-src',
- } },
- { language: 'c-cpp', serverId: 'clangd', command: ['clangd', '--background-index', '--clang-tidy'],
- extensions: ['.c', '.cpp', '.cc', '.cxx', '.c++', '.h', '.hpp', '.hh', '.hxx', '.h++'],
- checkers: ['clangd', 'clang', 'cc', 'clang-tidy'], wired: true, buildCheck: 'cmake --build build',
- projectFiles: ['compile_commands.json', '.clangd', 'CMakeLists.txt', 'Makefile'],
- install: {
- darwin: 'brew install llvm (keg-only: add "$(brew --prefix llvm)/bin" to PATH), or use the clangd that xcrun --find clangd locates',
- linux: 'sudo apt install clangd (Fedora: sudo dnf install clang-tools-extra; Arch: sudo pacman -S clang)',
- win32: 'winget install LLVM.LLVM (or: choco install llvm)',
- } },
- { language: 'java', serverId: 'jdtls', command: ['jdtls'], extensions: ['.java'],
- checkers: ['javac', 'mvn', 'gradle'], wired: false, buildCheck: 'mvn -q -DskipTests compile or ./gradlew compileJava',
- projectFiles: ['pom.xml', 'build.gradle', 'build.gradle.kts', 'gradlew'],
- install: {
- darwin: 'brew install jdtls',
- linux: 'download a release from https://github.com/eclipse-jdtls/eclipse.jdt.ls, extract it and put its jdtls launcher on PATH (Arch AUR: jdtls)',
- win32: 'download a release from https://github.com/eclipse-jdtls/eclipse.jdt.ls, extract it and put its jdtls launcher on PATH',
- } },
- { language: 'kotlin', serverId: 'kotlin-ls', command: ['kotlin-lsp', '--stdio'], extensions: ['.kt', '.kts'],
- checkers: ['kotlinc', 'gradle'], wired: false, buildCheck: './gradlew compileKotlin',
- projectFiles: ['build.gradle.kts', 'settings.gradle.kts', 'gradlew'],
- install: {
- darwin: 'brew install JetBrains/utils/kotlin-lsp',
- linux: 'download a release from https://github.com/Kotlin/kotlin-lsp, extract it and symlink its launcher as kotlin-lsp on PATH',
- win32: 'download a release from https://github.com/Kotlin/kotlin-lsp, extract it and put its launcher on PATH',
- } },
- { language: 'csharp', serverId: 'csharp', command: ['csharp-ls'], extensions: ['.cs'],
- checkers: ['dotnet'], wired: false, buildCheck: 'dotnet build --no-restore -v q',
- projectFiles: ['*.sln', '*.slnx', '*.csproj', 'global.json'],
- install: {
- darwin: 'dotnet tool install -g csharp-ls (needs the .NET SDK; add ~/.dotnet/tools to PATH)',
- linux: 'dotnet tool install -g csharp-ls (needs the .NET SDK; add ~/.dotnet/tools to PATH)',
- win32: 'dotnet tool install -g csharp-ls (needs the .NET SDK)',
- } },
- { language: 'razor', serverId: 'razor', command: ['roslyn-language-server', '--stdio'], extensions: ['.razor', '.cshtml'],
- checkers: ['dotnet'], wired: false, buildCheck: 'dotnet build --no-restore -v q', projectFiles: ['*.csproj', '*.sln'],
- install: {
- darwin: 'dotnet tool install -g roslyn-language-server --prerelease (see references/csharp/README.md)',
- linux: 'dotnet tool install -g roslyn-language-server --prerelease (see references/csharp/README.md)',
- win32: 'dotnet tool install -g roslyn-language-server --prerelease (see references/csharp/README.md)',
- } },
- { language: 'swift', serverId: 'sourcekit-lsp', command: ['sourcekit-lsp'], extensions: ['.swift'],
- checkers: ['swift', 'swiftc'], wired: false, buildCheck: 'swift build', projectFiles: ['Package.swift', 'compile_commands.json'],
- install: {
- darwin: 'xcode-select --install (or install Xcode); sourcekit-lsp ships in the toolchain, find it with xcrun --find sourcekit-lsp',
- linux: 'install a toolchain from https://www.swift.org/install/linux/ ; sourcekit-lsp is in its usr/bin',
- win32: 'install the Swift toolchain from https://www.swift.org/install/windows/ ; sourcekit-lsp is in its bin directory',
- } },
- { language: 'ruby', serverId: 'ruby-lsp', command: ['ruby-lsp'], extensions: ['.rb', '.rake', '.gemspec', '.ru'],
- checkers: ['ruby', 'rubocop'], wired: false, buildCheck: 'bundle exec rubocop --format json',
- projectFiles: ['Gemfile', 'Gemfile.lock', '.rubocop.yml', '.ruby-version'],
- install: {
- darwin: 'gem install ruby-lsp (use a Homebrew or version-manager Ruby, not the system Ruby)',
- linux: 'gem install ruby-lsp',
- win32: 'gem install ruby-lsp (RubyInstaller)',
- } },
- { language: 'php', serverId: 'php', command: ['intelephense', '--stdio'], extensions: ['.php'],
- checkers: ['php', 'phpstan', 'psalm'], wired: false, buildCheck: 'php -l <file> or vendor/bin/phpstan analyse --error-format=json',
- projectFiles: ['composer.json', 'composer.lock', 'phpstan.neon'],
- install: {
- darwin: 'npm install -g intelephense',
- linux: 'npm install -g intelephense',
- win32: 'npm install -g intelephense',
- } },
- { language: 'dart', serverId: 'dart', command: ['dart', 'language-server', '--protocol=lsp'], extensions: ['.dart'],
- checkers: ['dart', 'flutter'], wired: false, buildCheck: 'dart analyze --format=machine (Flutter: flutter analyze)',
- projectFiles: ['pubspec.yaml', 'analysis_options.yaml'],
- install: {
- darwin: 'brew tap dart-lang/dart && brew install dart (or brew install dart-sdk, or the Flutter SDK, which bundles dart)',
- linux: 'follow https://dart.dev/get-dart (Google apt repository) or install the Flutter SDK',
- win32: 'choco install dart-sdk (or install the Flutter SDK)',
- } },
- { language: 'elixir', serverId: 'elixir-ls', command: ['elixir-ls'], extensions: ['.ex', '.exs'],
- checkers: ['mix', 'elixir'], wired: false, buildCheck: 'mix compile --warnings-as-errors',
- projectFiles: ['mix.exs', 'mix.lock', '.formatter.exs', '.tool-versions'],
- install: {
- darwin: 'brew install elixir-ls',
- linux: 'download the release zip from https://github.com/elixir-lsp/elixir-ls/releases, unzip it and symlink language_server.sh as elixir-ls on PATH',
- win32: 'download the release zip from https://github.com/elixir-lsp/elixir-ls/releases and put language_server.bat on PATH',
- } },
- { language: 'zig', serverId: 'zls', command: ['zls'], extensions: ['.zig', '.zon'],
- checkers: ['zig'], wired: false, buildCheck: 'zig build --summary all or zig ast-check <file>',
- projectFiles: ['build.zig', 'build.zig.zon'],
- install: {
- darwin: 'brew install zls (the zls version must match your zig version)',
- linux: 'download the zls release that matches your zig version from https://github.com/zigtools/zls/releases (Arch: sudo pacman -S zls)',
- win32: 'download the zls release that matches your zig version from https://github.com/zigtools/zls/releases',
- } },
- { language: 'lua', serverId: 'lua-ls', command: ['lua-language-server'], extensions: ['.lua'],
- checkers: ['lua-language-server', 'luac', 'luacheck'], wired: false, buildCheck: 'lua-language-server --check . --checklevel=Warning',
- projectFiles: ['.luarc.json', '.luarc.jsonc', '.luacheckrc'],
- install: {
- darwin: 'brew install lua-language-server',
- linux: 'download a release from https://github.com/LuaLS/lua-language-server/releases and put its bin directory on PATH (Arch: sudo pacman -S lua-language-server)',
- win32: 'download a release from https://github.com/LuaLS/lua-language-server/releases and put its bin directory on PATH',
- } },
- { language: 'bash', serverId: 'bash', command: ['bash-language-server', 'start'], extensions: ['.sh', '.bash', '.zsh', '.ksh'],
- checkers: ['shellcheck', 'bash'], wired: true, buildCheck: 'shellcheck -f json <file>',
- projectFiles: ['.shellcheckrc'],
- install: {
- darwin: 'npm install -g bash-language-server and brew install shellcheck',
- linux: 'npm install -g bash-language-server and sudo apt install shellcheck (Fedora: sudo dnf install ShellCheck)',
- win32: 'npm install -g bash-language-server and scoop install shellcheck (or: choco install shellcheck)',
- } },
- { language: 'yaml', serverId: 'yaml-ls', command: ['yaml-language-server', '--stdio'], extensions: ['.yaml', '.yml'],
- checkers: ['yamllint', 'check-jsonschema'], wired: false, buildCheck: 'yamllint -f parsable <file>',
- projectFiles: ['.yamllint', '.yamllint.yml', '.yamllint.yaml'],
- install: {
- darwin: 'npm install -g yaml-language-server (or: brew install yaml-language-server)',
- linux: 'npm install -g yaml-language-server',
- win32: 'npm install -g yaml-language-server',
- } },
- { language: 'terraform', serverId: 'terraform', command: ['terraform-ls', 'serve'], extensions: ['.tf', '.tfvars'],
- checkers: ['terraform', 'tflint'], wired: false, buildCheck: 'terraform validate -json (after terraform init)',
- projectFiles: ['.terraform.lock.hcl', 'versions.tf', '.tflint.hcl'],
- install: {
- darwin: 'brew install hashicorp/tap/terraform-ls',
- linux: 'add the HashiCorp package repository, then sudo apt install terraform-ls (or sudo dnf install terraform-ls); release zips are at https://releases.hashicorp.com/terraform-ls/',
- win32: 'choco install terraform-ls',
- } },
- { language: 'dockerfile', serverId: 'dockerfile', command: ['docker-langserver', '--stdio'], extensions: ['.dockerfile'],
- checkers: ['hadolint'], wired: false, buildCheck: 'hadolint <file>', projectFiles: ['.hadolint.yaml'],
- install: {
- darwin: 'npm install -g dockerfile-language-server-nodejs and brew install hadolint',
- linux: 'npm install -g dockerfile-language-server-nodejs and a hadolint release from https://github.com/hadolint/hadolint/releases',
- win32: 'npm install -g dockerfile-language-server-nodejs and scoop install hadolint',
- } },
- { language: 'haskell', serverId: 'haskell-language-server', command: ['haskell-language-server-wrapper', '--lsp'], extensions: ['.hs', '.lhs'],
- checkers: ['ghc', 'cabal', 'stack'], wired: false, buildCheck: 'cabal build all or stack build',
- projectFiles: ['cabal.project', 'stack.yaml', 'hie.yaml', '*.cabal'],
- install: {
- darwin: 'ghcup install hls (ghcup itself: brew install ghcup, or https://www.haskell.org/ghcup/)',
- linux: 'ghcup install hls (ghcup itself: https://www.haskell.org/ghcup/)',
- win32: 'ghcup install hls (ghcup for Windows: https://www.haskell.org/ghcup/)',
- } },
- { language: 'julia', serverId: 'julials', command: ['julia', '--startup-file=no', '--history-file=no', '--project=@lsp', '-e', 'using LanguageServer; runserver()'],
- extensions: ['.jl'], checkers: ['julia'], wired: false,
- buildCheck: "julia --project -e 'using Pkg; Pkg.test()'", projectFiles: ['Project.toml', 'Manifest.toml'],
- install: {
- darwin: `brew install juliaup, then julia -e 'using Pkg; Pkg.activate("lsp"; shared=true); Pkg.add("LanguageServer")' (see references/julia/README.md)`,
- linux: `curl -fsSL https://install.julialang.org | sh, then julia -e 'using Pkg; Pkg.activate("lsp"; shared=true); Pkg.add("LanguageServer")' (see references/julia/README.md)`,
- Note: Pipes a downloaded script directly into a shell (curl | sh / wget | bash)
- Line 187 on GitHub
- win32: `winget install --name Julia --id 9NJNWW8PVKMN -e -s msstore, then julia -e 'using Pkg; Pkg.activate("lsp"; shared=true); Pkg.add("LanguageServer")'`,
- } },
- ];
- export const PLATFORM = process.platform === 'darwin' || process.platform === 'win32' ? process.platform : 'linux';
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If itβs helped, pass it on.