Unified · Split
| @@ -13,6 +13,12 @@ At runtime, `executor` behaves like one local product: · 12 unmodified lines | |||
| 13 | 13 | ||
| 14 | The current codebase is the v3 rewrite. Older experiments live in `legacy/` and `legacy2/`, but the active architecture is the one in `apps/` and `packages/`. | 14 | The current codebase is the v3 rewrite. Older experiments live in `legacy/` and `legacy2/`, but the active architecture is the one in `apps/` and `packages/`. |
| 15 | 15 | ||
| 16 | ## Attribution | ||
| 17 | |||
| 18 | - The npm package name `executor` is used with attribution to [Crystian](https://www.linkedin.com/in/crystian/). | ||
| 19 | - The `codemode` concept in this project is inspired by Cloudflare's [Code Mode announcement](https://blog.cloudflare.com/code-mode/). | ||
| 20 | |||
| 21 | |||
| 16 | ## Why this exists | 22 | ## Why this exists |
| 17 | 23 | ||
| 18 | `executor` is built around a simple idea: agents should work against a structured tool environment instead of guessing at raw HTTP calls, carrying huge MCP definitions in context, or running arbitrary local commands with broad permissions. | 24 | `executor` is built around a simple idea: agents should work against a structured tool environment instead of guessing at raw HTTP calls, carrying huge MCP definitions in context, or running arbitrary local commands with broad permissions. |