aiscope 0.1.1

DevTools for your AI coding tools' memory. See what Cursor, Claude Code, and Copilot actually remember about your project — and where they disagree.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

# Interactive TUI

Run `aiscope` with no output flags to launch the ratatui interface.

```bash
aiscope .
```

## Layout

Three panes:

- **Sources** (left) — every memory file aiscope discovered, color-coded by tool.
- **Unified context** (right) — every rule across every file, with conflicts
  flagged inline. Each rule shows its `applyTo` glob in dim gray on the right.
- **Score** (bottom) — totals: rules, clashes, duplicates, tokens, waste %.

## Keys

| Key             | Action                       |
| --------------- | ---------------------------- |
| `q` / `Esc`     | Quit                         |
| `c`             | Toggle conflicts-only filter |
| `↑` / `↓`       | Scroll one row               |
| `j` / `k`       | Same as ↓ / ↑ (vim-style)    |
| `PgUp` / `PgDn` | Page scroll                  |

## Tool icons

| Icon | Tool        |
| ---- | ----------- |
| `▲`  | Copilot     |
| `○`  | Cursor      |
| `◆`  | Claude Code |

## Falling back to text

If stdout is not a TTY (you piped or redirected), aiscope automatically prints
plain text instead of TUI escape codes. So `aiscope . > scan.txt` works
naturally.