aiscope 0.1.0

DevTools for your AI coding tools' memory. See what Cursor, Claude Code, and Copilot actually remember about your project — and where they disagree.
Documentation 
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
41
42
43
44
45
46
47
48

# `AGENTS.md`

The `AGENTS.md` file is a tool-agnostic convention emerging across the
ecosystem — Copilot, Cursor, Claude, and Codex all read it. aiscope treats
it as a first-class source.

## Discovery

aiscope finds `AGENTS.md` at **any depth** in the repo and assigns it to the
**Copilot Agents subsystem** by convention.

## Path scoping

The file's directory becomes its scope's `path_prefix`:

| File location            | Scope             |
| ------------------------ | ----------------- |
| `AGENTS.md`              | everywhere        |
| `apps/web/AGENTS.md`     | `apps/web/**`     |
| `services/api/AGENTS.md` | `services/api/**` |

This means a top-level `AGENTS.md` and a `apps/web/AGENTS.md` will not
conflict on naming rules unless both apply to overlapping paths — perfect
for monorepos.

## Why use it

If you want **one source of truth** that all your AI tools read, put it in
`AGENTS.md`. Most modern AI tools will pick it up automatically, and aiscope
will validate its consistency with everything else.

## Example

```markdown
# AGENTS.md

## Code style

- Use 2-space indentation
- Prefer single quotes in TypeScript
- Use snake_case for Python

## Testing

- Every PR must include tests for new public APIs
```

No frontmatter needed — the file applies to its directory and below.