# Local Keep AI for Eclipse

Ask your own AI models about your code without leaving Eclipse — explain the
open file, generate tests, or chat, against **1,000+ models**, local or cloud,
with no API key needed for the local ones.

Bundle: `ai.localkeep.eclipse` · Requires **Eclipse 2023-03** or newer and
**Java 17** · License: MIT

[Website](https://localkeep.ai) · [Docs](https://localkeep.ai/docs/integrations/eclipse)

## Install

The plugin does **not** bundle the CLI. Install that first — it holds your
session and your model choice, and the plugin reads both from it:

```bash
pip install local-keep-ai-cli
lk login
```

Then install the plugin. From source, which is the current route:

1. **File → Import → Plug-ins and Fragments**, or open this directory as an
  existing project in an Eclipse workspace with PDE installed.
2. Right-click the project → **Export → Deployable plug-ins and fragments**.
3. Point the export at your Eclipse `dropins/` directory, then restart Eclipse.

To develop against it instead, use **Run → Run Configurations → Eclipse
Application**, which launches a second Eclipse with the plugin loaded.

## Use

**Window → Show View → Other → Local Keep AI → Local Keep AI** opens the chat
view. Type a question and press Enter.

Two commands act on the file in the active editor, from the **Local Keep AI**
menu or the editor's right-click menu:

- **Explain This File** — what it does, its entry points, and anything
 surprising in it.
- **Generate Tests** — tests in the framework the project already uses,
 covering the failure paths rather than only the happy one.

**List Models** shows what this account can reach and marks the active one.

## Settings

**Window → Preferences → Local Keep AI**. Both fields are optional:

- **Path to lk** — set this only if the plugin cannot find the binary.
- **Model override** — leave empty to use whatever your CLI is set to, so
 Eclipse and your terminal always agree on which model is answering.

## How it works

The plugin shells out to `lk`. It never talks to the Local Keep AI API itself
and never handles a token — the CLI already holds your session, so a second
copy of your credentials inside the IDE would be one more place for them to
leak and one more thing to break the next time authentication changes.

Every call runs inside an Eclipse `Job` and marshals its result back through
`Display.asyncExec` before touching a widget. A model answer takes seconds;
running it on the SWT display thread would freeze the whole IDE.

## Troubleshooting

**"Local Keep AI CLI not found"** — Eclipse cannot see `lk`. A GUI launch does
not inherit the PATH from your login shell, which is why this appears even when
`lk` works in your terminal. Set the path explicitly in
**Preferences → Local Keep AI**.

**The menu is missing** — the bundle did not start. Check
**Help → About Eclipse → Installation Details → Plug-ins** for
`ai.localkeep.eclipse`, and look in the Error Log view for a resolution
failure.

**A command does nothing** — it needs a file on disk in the active editor. An
untitled buffer or a jar entry has no path to hand the CLI, and the view says
so rather than failing silently.

## Licence

MIT — see [LICENSE](LICENSE).