lacy 1.8.11 → 1.8.13

package/CLAUDE.md

@@ -0,0 +1,340 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Mission
+
+Enable developers to talk directly to their shell.
+
+## Project Overview
+
+Lacy Shell is a shell plugin (ZSH and Bash 4+) that detects natural language and routes it to an AI coding agent. Commands execute normally. Natural language goes to the AI. No context switching required.
+
+**Install location:** `~/.lacy`
+**Package name:** `lacy` (npm)
+
+## Installation Methods
+
+| Method   | Command                                      |
+| -------- | -------------------------------------------- |
+| curl     | `curl -fsSL https://lacy.sh/install \| bash` |
+| npx      | `npx lacy`                                   |
+| Homebrew | `brew install lacymorrow/tap/lacy`           |
+
+## Visual Feedback
+
+**Real-time indicator** (left of prompt) changes color as you type:
+
+- **Green (34)** = will execute in shell
+- **Magenta (200)** = will go to AI agent
+
+**First-word syntax highlighting** (ZSH only, via `region_highlight`):
+
+- First word is highlighted **green bold** for shell commands, **magenta bold** for agent queries
+- Updates on every `zle-line-pre-redraw` (accounts for leading whitespace)
+
+**Mode indicator** shows current mode:
+
+- ZSH: right prompt (`RPS1`) — `SHELL` (green) / `AGENT` (magenta) / `AUTO` (blue)
+- Bash: PS1 badge — `SHELL` / `AGENT` / `AUTO` with matching colors
+
+**Ghost text suggestions** (ZSH only, via `POSTDISPLAY`):
+
+- After a reroute candidate fails and the agent responds, a suggestion appears as gray ghost text on the next empty prompt
+- Right arrow or Tab accepts the suggestion into BUFFER
+- Typing any character clears it; autosuggestions resumes normally
+
+## Auto Mode Logic
+
+In AUTO mode, routing is determined by:
+
+1. **Agent words** (~150 common conversational words like `perfect`, `thanks`, `yes`, `no`, `explain`, `why`) → Agent (always, even single-word). Defined in `LACY_AGENT_WORDS` in `lib/core/constants.sh`.
+2. **Shell reserved words** (`do`, `done`, `then`, `else`, `elif`, `fi`, `esac`, `in`, `select`, `function`, `coproc`, `{`, `}`, `!`, `[[`) → Agent (Layer 1 — these pass `command -v` but are never standalone commands)
+3. First word is valid command → Shell
+4. Single word, not a command → Shell (typo, let it error)
+5. Multiple words, first not a command → Agent (natural language)
+6. Valid command + NL arguments → Shell first, then agent on failure (post-execution reroute, silent)
+
+Rule 2 detail: Shell reserved words pass `command -v` but are never valid as the first token of a standalone invocation. When a user types "do we have X" or "in the codebase", they mean natural language. List defined in `LACY_SHELL_RESERVED_WORDS` in `lib/core/constants.sh`. See `docs/NATURAL_LANGUAGE_DETECTION.md` for full spec.
+
+Rule 6 detail: When a valid command receives NL arguments and fails (exit non-zero, code < 128), the error output is analyzed. If it matches a known error pattern AND has NL markers in the input, the command silently reroutes to the agent. No user-facing hint — just auto-reroute. Only active in auto mode.
+
+Examples:
+
+- `ls -la` → Shell (valid command)
+- `what files are here` → Agent (agent word "what")
+- `do we have a way to uninstall?` → Agent (reserved word "do")
+- `in the codebase where is auth?` → Agent (reserved word "in")
+- `cd..` → Shell (single word typo)
+- `fix the bug` → Agent (multi-word natural language)
+- `kill the process on localhost:3000` → Shell → Agent (4 bare words, "the" marker, fails)
+- `go ahead and fix the tests` → Shell → Agent ("ahead" marker, "unknown command" error)
+- `make sure the tests pass` → Shell → Agent ("sure" marker, "No rule to make target" error)
+- `kill -9 my baby` → Shell only (2 bare words, below threshold)
+- `echo the quick brown fox` → Shell only (succeeds, no reroute)
+- `!rm -rf` → Shell (emergency bypass with `!` prefix)
+
+## Canonical Functions
+
+### `lacy_shell_classify_input(input)` — The Single Source of Truth
+
+**File:** `lib/core/detection.sh`
+
+All input classification MUST go through this function. It returns one of three strings:
+
+- `"shell"` → route to shell (indicator: green)
+- `"agent"` → route to AI agent (indicator: magenta)
+- `"neutral"` → no routing decision yet (indicator: gray)
+
+**Mode-aware behavior:**
+
+1. **Empty input** → returns mode color (`shell`/`agent`) in locked modes, `neutral` in auto
+2. **Shell mode** → always returns `shell` (after empty check)
+3. **Agent mode** → always returns `agent` (after empty check)
+4. **Auto mode** → applies detection heuristics
+
+**Why this matters:**
+
+- The indicator, execution, and highlighting ALL call this function
+- Never create parallel detection logic — always extend this function
+- The empty-input behavior ensures the indicator shows the correct mode color when idle
+
+**Consumers:**
+
+- ZSH: `keybindings.zsh:lacy_shell_update_input_indicator()` — real-time indicator color
+- ZSH: `execute.zsh:lacy_shell_smart_accept_line()` — execution routing
+- ZSH: `keybindings.zsh:lacy_shell_update_first_word_highlight()` — syntax highlighting
+- Bash: `execute.bash:lacy_shell_smart_accept_line_bash()` — execution routing
+
+### `lacy_shell_detect_natural_language(input, output, exit_code)` — Layer 2 Post-Execution
+
+**File:** `lib/core/detection.sh`
+
+Analyzes a failed shell command's output to detect natural language. Returns 0 if NL detected, 1 otherwise. Both criteria must match:
+
+1. **Error pattern** — output contains a known shell error from `LACY_SHELL_ERROR_PATTERNS`
+2. **NL signal** — second word is in `LACY_NL_MARKERS`, OR 5+ words with parse/syntax error
+
+Minimum 2 words required. See `docs/NATURAL_LANGUAGE_DETECTION.md` for full algorithm.
+
+### `_lacy_build_query_context(query)` — Terminal Context for Agent Queries
+
+**File:** `lib/core/context.sh`
+
+Prepends delta-based terminal context (cwd, git branch, exit code, recent commands, terminal output) to agent queries. Only includes what changed since the last query — zero overhead when nothing changed.
+
+**Format:** `[cwd: /path] [git: branch] [exit: 1] [recent: cmd1 | cmd2] <query>`
+
+**With terminal output** (tmux, screen, iTerm2, Terminal.app):
+```
+[cwd: /path] [exit: 1] [recent: npm test]
+[terminal-output]
+npm ERR! Test failed. See above for more details.
+[/terminal-output]
+why did that fail?
+```
+
+**Delta tracking:**
+
+- CWD and git branch: compared against last-sent values, skipped if unchanged. Detached HEAD shows short commit hash instead of literal "HEAD"
+- Exit code: only included when non-zero AND a shell command ran since the last query
+- Recent commands: explicit ring buffer (max 10), not `fc`/`history` (avoids agent queries leaking)
+- Terminal output: lazy screen capture via terminal/multiplexer API at query time (tmux, screen, iTerm2, Terminal.app). Stripped of ANSI escapes, capped at 50 lines (configurable via `context.output_lines`). tmux/screen checked first since terminal emulator APIs return wrong content inside multiplexers.
+- Counters reset after each agent query — next query starts fresh
+
+**Hook chain:**
+
+1. `accept-line` routes to "shell" → `_lacy_ctx_mark_command($BUFFER)` records the command
+2. `precmd` fires → `_lacy_ctx_on_precmd($?)` captures exit code (only if `_LACY_CTX_REAL_CMD` flag is set)
+3. User types agent query → `_lacy_build_query_context()` builds delta, sets `_LACY_CTX_RESULT`, resets counters
+4. `/new` session → `_lacy_ctx_reset()` clears all state so next query sends full context
+
+**Why result variable, not stdout:** The function modifies global state (resets counters). Using `$()` subshell would lose those resets. `_LACY_CTX_RESULT` avoids the fork entirely.
+
+## Plugin Coexistence (zsh-autosuggestions)
+
+Lacy shares two ZLE resources with `zsh-autosuggestions` (and potentially `zsh-syntax-highlighting`). Mishandling either causes visible bugs. Full design rationale is documented in the header of `lib/zsh/keybindings.zsh`.
+
+### `region_highlight` — tagged entries with `memo=lacy`
+
+Multiple plugins write highlight specs to the `region_highlight` array. Lacy adds first-word coloring (green/magenta) and ghost text styling. These entries are tagged with `memo=lacy` (ZSH 5.8+ feature) so they can be selectively removed on each redraw without destroying highlights from other plugins.
+
+**Rule:** Never use `region_highlight=()`. Always filter: `region_highlight=("${(@)region_highlight:#*memo=lacy*}")`. Always append `memo=lacy` to any highlight entry Lacy creates.
+
+### `POSTDISPLAY` — suppressing autosuggestions during ghost text
+
+Both Lacy (reroute ghost text) and autosuggestions (history suggestions) write to `POSTDISPLAY`. When Lacy's ghost text is active (BUFFER empty), call `_zsh_autosuggest_clear` before setting `POSTDISPLAY` to prevent autosuggestions from overwriting it. When the user starts typing, Lacy clears its ghost text and autosuggestions resumes normally.
+
+### Right arrow / Tab — no dot prefix on fallback widgets
+
+Lacy's `_lacy_forward_char_or_accept` and `_lacy_expand_or_accept` widgets check for Lacy ghost text first. On fallback, they call `zle forward-char` (not `zle .forward-char`). The dot prefix bypasses widget wrapping, which would skip autosuggestions' accept-suggestion behavior. Without the dot, autosuggestions' wrapper fires and right arrow / tab accept its suggestions normally.
+
+## Supported AI CLI Tools
+
+| Tool     | Command                | Prompt Flag  |
+| -------- | ---------------------- | ------------ |
+| lash (recommended) | `lash run -c "query"`  | `-c`         |
+| claude   | `claude -p "query"`    | `-p`         |
+| opencode | `opencode run -c "query"` | `-c`         |
+| gemini   | `gemini --resume -p "query"` | `-p`         |
+| codex    | `codex exec resume --last "query"` | positional   |
+| hermes   | `hermes chat -q "query"` | `-q`         |
+| copilot  | `copilot -p "query"`   | `-p`         |
+| goose    | `goose run -t "query"` | `-t`         |
+| amp      | `amp -x "query"`       | `-x`         |
+| aider    | `aider --no-auto-commits --message "query"` | `--message`  |
+| custom   | user-defined command   | user-defined |
+
+lash is the recommended default — it's an opencode fork built by the same author. Website: lash.lacy.sh. During onboarding, lacy offers to install lash if no AI CLI tool is detected.
+
+All tools handle their own authentication - no API keys needed from lacy.
+
+## Architecture
+
+```
+~/.lacy/
+├── lacy.plugin.zsh          # Entry point (ZSH)
+├── lacy.plugin.bash         # Entry point (Bash 4+)
+├── config.yaml              # User configuration
+├── install.sh               # Installer (bash + npx fallback)
+├── uninstall.sh             # Uninstaller
+├── bin/
+│   └── lacy                 # Standalone CLI (no Node required)
+└── lib/
+    ├── core/                    # Shared modules (Bash 4+ and ZSH)
+    │   ├── constants.sh         # Colors, timeouts, paths, detection arrays
+    │   ├── config.sh            # YAML config, API key management
+    │   ├── modes.sh             # Mode state (shell/agent/auto)
+    │   ├── spinner.sh           # Loading spinner with shimmer text effect
+    │   ├── mcp.sh               # Multi-tool routing (LACY_TOOL_CMD registry)
+    │   ├── preheat.sh           # Agent preheating (background server, session reuse)
+    │   ├── context.sh           # Delta-based terminal context for agent queries
+    │   ├── detection.sh         # classify_input(), has_nl_markers(), detect_natural_language()
+    │   └── commands.sh          # Shared command implementations (mode, tool, session, quit)
+    ├── zsh/
+    │   ├── keybindings.zsh      # Ctrl+Space toggle, indicator, first-word region_highlight
+    │   ├── prompt.zsh           # Prompt with indicator, mode in right prompt
+    │   └── execute.zsh          # Execution routing, reroute candidate logic
+    ├── bash/
+    │   ├── init.bash            # Bash adapter init (sources core + bash modules)
+    │   ├── keybindings.bash     # Macro-based Enter override, Ctrl+Space toggle
+    │   ├── prompt.bash          # Mode badge in PS1
+    │   └── execute.bash         # Execution routing, reroute candidate logic
+    └── *.zsh                    # Backward-compat wrappers → lib/core/ or lib/zsh/
+
+packages/lacy/               # npm package for interactive installer
+├── package.json
+├── index.mjs                # @clack/prompts based installer
+└── README.md
+```
+
+## CLI (standalone, no Node required)
+
+After installation, `~/.lacy/bin` is added to `$PATH`, making the `lacy` command available:
+
+```bash
+lacy setup           # Interactive settings (tool, mode, config) — fancy Node UI if available
+lacy status          # Show installation status
+lacy doctor          # Diagnose common issues
+lacy update          # Pull latest changes
+lacy uninstall       # Remove Lacy Shell — fancy Node UI if available
+lacy reinstall       # Fresh installation
+lacy config          # Show config
+lacy config edit     # Open config in $EDITOR
+lacy install         # Install (delegates to npx or curl installer)
+lacy version         # Show version
+lacy help            # Show all commands
+```
+
+Source: `bin/lacy` (pure bash, zero dependencies)
+
+**Hybrid Node delegation:** `setup`, `install`, and `uninstall` try `npx lacy@latest` first for the rich @clack/prompts UI, then fall back to bash if Node is unavailable. Set `LACY_NO_NODE=1` to force bash-only mode.
+
+### Testing locally
+
+`bin/lacy` delegates to `npx lacy@latest` which downloads the **published** npm package, not the local code. To test local changes to `packages/lacy/index.mjs`:
+
+```bash
+# Run the local Node installer/menu directly
+node packages/lacy/index.mjs          # already-installed dashboard
+node packages/lacy/index.mjs setup    # same dashboard
+node packages/lacy/index.mjs --help   # help text
+
+# Or force the bash fallback (skips npx entirely)
+LACY_NO_NODE=1 bin/lacy setup
+```
+
+## Key Commands
+
+- `mode [shell|agent|auto]` - Switch modes
+- `mode` - Show current mode and color legend
+- `tool` - Show active AI tool and available tools
+- `tool set <name>` - Set AI tool (lash, claude, opencode, gemini, codex, hermes, copilot, goose, amp, aider, custom, auto) — persists to config.yaml
+- `tool set custom "cmd"` - Set a custom command as the AI tool
+- `/new` / `/reset` / `/clear` - Start a new conversation session
+- `/resume` - Resume the last saved session
+- `ask "question"` - Direct query to agent
+- `quit` / `stop` / `exit` - Exit lacy shell
+- `Ctrl+Space` - Toggle between modes
+- `Ctrl+C` (2x) - Quit
+
+Leading-slash commands (e.g. `/new`) are intercepted before shell execution and routed to the session handler. The slash is stripped and matched against known session commands.
+
+## Key Files
+
+- `lib/core/constants.sh` - Colors, paths, `LACY_AGENT_WORDS`, `LACY_SHELL_RESERVED_WORDS`, `LACY_NL_MARKERS`, `LACY_SHELL_ERROR_PATTERNS`
+- `lib/core/detection.sh` - **`lacy_shell_classify_input()`** (canonical), `lacy_shell_has_nl_markers()`, `lacy_shell_detect_natural_language()`
+- `lib/core/mcp.sh` - `_lacy_run_tool_cmd()` safe executor, `lacy_tool_cmd()` registry, `lacy_shell_query_agent()` routing
+- `lib/core/context.sh` - `_lacy_build_query_context()` delta-based terminal context, `_lacy_ctx_mark_command()`, `_lacy_ctx_on_precmd()`
+- `lib/core/config.sh` - `agent_tools.active` parsing → `LACY_ACTIVE_TOOL`
+- `lib/core/spinner.sh` - Braille spinner + shimmer "Thinking" animation during AI queries
+- `lib/core/preheat.sh` - Background server (lash/opencode) + session reuse (claude), `lacy_session_new()`, `lacy_session_resume()`
+- `lib/core/commands.sh` - Shared command implementations: mode, tool, session, quit (portable Bash 4+/ZSH)
+- `lib/zsh/execute.zsh` - `lacy_shell_tool()` command, routing logic, reroute candidates, slash-command interception
+- `lib/zsh/keybindings.zsh` - Real-time indicator logic, first-word `region_highlight`
+- `install.sh` - Bash installer with npx fallback, interactive menu
+- `packages/lacy/index.mjs` - Node installer with @clack/prompts
+- `docs/NATURAL_LANGUAGE_DETECTION.md` - Shared spec for NL detection (synced with lash)
+
+## Configuration
+
+Config file: `~/.lacy/config.yaml`
+
+```yaml
+agent_tools:
+  active: claude # or lash, opencode, gemini, codex, hermes, copilot, goose, amp, aider, custom, empty for auto
+  # custom_command: "your-command -flags"  # used when active: custom
+
+api_keys:
+  openai: "sk-..." # Only needed if no CLI tool
+  anthropic: "sk-..."
+
+modes:
+  default: auto
+# Preheat: keep agents warm between queries
+# preheat:
+#   eager: false          # Start background server on plugin load
+#   server_port: 4096     # Port for background server
+```
+
+**Preheating:** lash/opencode use a background server (`lash serve`) to eliminate cold-start. Claude uses `--resume SESSION_ID` for conversation continuity. Other tools have no preheating.
+
+## Development Notes
+
+- Install path changed from `~/.lacy-shell` to `~/.lacy`
+- Repo (`lib/`) and install dir (`~/.lacy/lib/`) are separate copies — changes must be applied to both
+- Prompt capture is deferred to first `precmd`/`PROMPT_COMMAND` so user's shell profile loads first
+- Indicator only updates when type changes (avoids flickering)
+- Colors: Green=34, Magenta=200, Blue=75, Gray=238
+- Use `print -P` (not `echo`) for colored output in ZSH — `%F{...}%f` escapes need `print -P`
+- Use `printf '\e[38;5;Nm...\e[0m'` for colored output in Bash
+- Installer uses `printf` instead of `echo -e` for portability
+- Node installer falls back to bash if npm package not available
+
+### Bash adapter notes
+
+- **Enter key**: Can't use `bind -x` directly on `\C-m` — it replaces accept-line entirely, so shell commands never submit. Instead, bind classification to a hidden key (`\C-x\C-l`) and make `\C-m` a macro: `"\C-x\C-l\C-j"` (classify, then accept-line)
+- **Spinner**: Background `{ ... } &` jobs dump their source on exit via bash's `[N] Done ...` notification. Fix: `disown` the PID immediately after starting; use `kill` + `sleep` instead of `wait` for cleanup
+- **No real-time indicator**: Bash can't redraw PS1 on keystroke (no `zle-line-pre-redraw` equivalent). Mode badge in PS1 updates on each prompt cycle only
+- **Ctrl+Space**: Uses macro `"\C-a\C-k _lacy_mode_toggle_\C-j"` — types hidden command and submits, so PROMPT_COMMAND can update PS1
+- **macOS default bash is 3.2** — adapter requires 4+ and shows a clear error if version is too old. Users install modern bash via `brew install bash`

package/CONTRIBUTING.md

@@ -0,0 +1,141 @@
+# Contributing to Lacy
+
+Thanks for your interest in contributing to Lacy! This guide will help you get started.
+
+## Getting Started
+
+### Prerequisites
+
+- **ZSH** or **Bash 4+** (macOS ships with Bash 3.2 -- install Bash 4+ via `brew install bash`)
+- **Git** (for development; not required for end-user installation)
+- An AI CLI tool for testing agent routing (Claude Code, Lash, Gemini CLI, etc.)
+
+### Development Setup
+
+1. **Fork and clone** the repository:
+
+   ```bash
+   git clone https://github.com/<your-username>/lacy.git
+   cd lacy
+   ```
+
+2. **Symlink for development** instead of using the installed copy:
+
+   ```bash
+   # Back up your installed copy if you have one
+   mv ~/.lacy ~/.lacy.bak
+
+   # Symlink repo to install path
+   ln -s "$(pwd)" ~/.lacy
+   ```
+
+3. **Source the plugin** in your shell:
+
+   ```bash
+   # ZSH
+   source ~/.lacy/lacy.plugin.zsh
+
+   # Bash 4+
+   source ~/.lacy/lacy.plugin.bash
+   ```
+
+4. **Open a new terminal** to test your changes. After editing files, open a fresh shell to reload.
+
+### Project Structure
+
+```
+lib/
+  core/           # Shared modules (Bash 4+ and ZSH)
+    constants.sh  # Colors, detection arrays, error patterns
+    config.sh     # YAML config parsing
+    detection.sh  # Input classification (the core algorithm)
+    modes.sh      # Mode state management
+    context.sh    # Terminal context for agent queries
+    commands.sh   # Built-in command implementations
+    spinner.sh    # Loading animation
+    mcp.sh        # AI tool routing
+    preheat.sh    # Agent warm-up
+  zsh/            # ZSH-specific modules
+  bash/           # Bash 4+ adapter modules
+bin/lacy          # Standalone CLI (pure bash)
+packages/lacy/    # npm package (interactive installer)
+tests/            # Test scripts
+docs/             # Documentation and specs
+```
+
+## Making Changes
+
+### Branching
+
+Create a feature branch from `main`:
+
+```bash
+git checkout -b feat/your-feature
+```
+
+### Code Style
+
+- Shell scripts should be compatible with **Bash 4+** (for `lib/core/`) or **ZSH** (for `lib/zsh/`)
+- Use `printf` instead of `echo -e` for portability
+- Use `print -P` for colored output in ZSH (`%F{N}%f` escapes)
+- Use `printf '\e[38;5;Nm...\e[0m'` for colored output in Bash
+- Keep functions focused and well-named
+- Use conventional commit messages: `feat:`, `fix:`, `chore:`, `docs:`
+
+### Key Design Principles
+
+- **Single source of truth**: All input classification goes through `lacy_shell_classify_input()` in `lib/core/detection.sh`. Never create parallel detection logic.
+- **Plugin coexistence**: Lacy shares ZLE resources with `zsh-autosuggestions` and `zsh-syntax-highlighting`. Always tag `region_highlight` entries with `memo=lacy`. Never clear `region_highlight` with `region_highlight=()`.
+- **No Node dependency at runtime**: The shell plugin and CLI (`bin/lacy`) must work without Node.js installed. Node is only used for the optional interactive installer.
+- **Bash/ZSH portability**: Core modules in `lib/core/` must work in both Bash 4+ and ZSH.
+
+### Testing
+
+Run the test suite in both shells:
+
+```bash
+bash tests/test_core.sh
+zsh tests/test_core.sh
+```
+
+For Bash-specific tests:
+
+```bash
+bash tests/test_bash.bash
+```
+
+Manual testing is also important. Open a fresh shell and verify:
+
+- Mode switching works (`mode shell`, `mode agent`, `mode auto`, `Ctrl+Space`)
+- Input classification is correct (commands stay green, natural language turns magenta)
+- Agent routing works for your change
+- No regressions in normal shell command execution
+
+## Submitting a Pull Request
+
+1. **Test your changes** in both ZSH and Bash 4+ when modifying `lib/core/` code
+2. **Commit** with a conventional commit message:
+   ```bash
+   git commit -m "feat: add support for fish shell"
+   ```
+3. **Push** your branch and open a PR against `main`
+4. **Describe** what your PR does and why. Include before/after behavior if applicable.
+5. **Link** any related issues
+
+## Reporting Bugs
+
+Open an issue with:
+
+- Your shell and version (`echo $SHELL && $SHELL --version`)
+- Your OS (`uname -a`)
+- Steps to reproduce
+- Expected vs. actual behavior
+- Output of `lacy doctor` if applicable
+
+## Feature Requests
+
+Open an issue describing the feature, the problem it solves, and how you'd expect it to work. Discussion is welcome before implementation.
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the [MIT License](LICENSE).

package/LICENSE

@@ -0,0 +1,110 @@
+# Functional Source License, Version 1.1, MIT Future License
+
+## Abbreviation
+
+FSL-1.1-MIT
+
+## Notice
+
+Copyright 2025 Lacy Morrow
+
+## Terms and Conditions
+
+### Licensor ("We")
+
+The party offering the Software under these Terms and Conditions.
+
+### The Software
+
+The "Software" is each version of the software that we make available under
+these Terms and Conditions, as indicated by our inclusion of these Terms and
+Conditions with the Software.
+
+### License Grant
+
+Subject to your compliance with this License Grant and the Patents,
+Redistribution and Trademark clauses below, we hereby grant you the right to
+use, copy, modify, create derivative works, publicly perform, publicly display
+and redistribute the Software for any Permitted Purpose identified below.
+
+### Permitted Purpose
+
+A Permitted Purpose is any purpose other than a Competing Use. A Competing Use
+means making the Software available to others in a commercial product or
+service that:
+
+1. substitutes for the Software;
+
+2. substitutes for any other product or service we offer using the Software
+   that exists as of the date we make the Software available; or
+
+3. offers the same or substantially similar functionality as the Software.
+
+Permitted Purposes specifically include using the Software:
+
+1. for your internal use and access;
+
+2. for non-commercial education;
+
+3. for non-commercial research; and
+
+4. in connection with professional services that you provide to a licensee
+   using the Software in accordance with these Terms and Conditions.
+
+### Patents
+
+To the extent your use for a Permitted Purpose would necessarily infringe our
+patents, the license grant above includes a license under our patents. If you
+make a claim against any party that the Software infringes or contributes to
+the infringement of any patent, then your patent license to the Software ends
+immediately.
+
+### Redistribution
+
+The Terms and Conditions apply to all copies, modifications and derivatives of
+the Software.
+
+If you redistribute any copies, modifications or derivatives of the Software,
+you must include a copy of or a link to these Terms and Conditions and not
+remove any copyright notices provided in or with the Software.
+
+### Disclaimer
+
+THE SOFTWARE IS PROVIDED "AS IS" AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF FITNESS FOR A PARTICULAR
+PURPOSE, MERCHANTABILITY, TITLE OR NON-INFRINGEMENT.
+
+IN NO EVENT WILL WE HAVE ANY LIABILITY TO YOU ARISING OUT OF OR RELATED TO THE
+SOFTWARE, INCLUDING INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES,
+EVEN IF WE HAVE BEEN INFORMED OF THEIR POSSIBILITY IN ADVANCE.
+
+### Trademarks
+
+Except for displaying the License Details and identifying us as the origin of
+the Software, you have no right under these Terms and Conditions to use our
+trademarks, trade names, service marks or product names.
+
+## Grant of Future License
+
+We hereby irrevocably grant you an additional license to use the Software under
+the MIT license that is effective on the second anniversary of the date we make
+the Software available. On or after that date, you may use the Software under
+the MIT license, in which case the following will apply:
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
+of the Software, and to permit persons to whom the Software is furnished to do
+so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+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 THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.