You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
-
## How to contribute to ALTK‑Evolve
1
+
## How to Contribute to Evolve
2
2
3
-
ALTK‑Evolve welcomes external contributions of all kinds. Whether you are fixing bugs, improving existing functionality, or adding new evolution-focused capabilities, we’re glad to work with you.
3
+
Evolve welcomes external contributions of all kinds. Whether you are fixing bugs, improving existing functionality, or adding new evolution-focused capabilities, we’re glad to work with you.
4
4
5
5
### Did you find a bug?
6
6
@@ -9,7 +9,7 @@ ALTK‑Evolve welcomes external contributions of all kinds. Whether you are fixi
9
9
### Types of contributions
10
10
11
11
* Fixing bugs
12
-
* Improving existing ALTK‑Evolve components
12
+
* Improving existing Evolve components
13
13
* Adding new components or evolution strategies
14
14
* Improving documentation, examples, or tests
15
15
@@ -54,9 +54,9 @@ Or:
54
54
pre-commit run --all-files
55
55
```
56
56
57
-
### Adding new components to ALTK‑Evolve
57
+
### Adding new components to Evolve
58
58
59
-
ALTK‑Evolve builds on Agent Lifecycle Toolkit concepts with a focus on agent evolution, adaptation, and improvement over time.
59
+
Evolve builds on Agent Lifecycle Toolkit concepts with a focus on agent evolution, adaptation, and improvement over time.
60
60
61
61
1. Identify the evolution purpose of your component.
62
62
2. Add a new package under the appropriate module.
Copy file name to clipboardExpand all lines: README.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ Prerequisites:
32
32
33
33
```bash
34
34
git clone <repository_url>
35
-
cd evolve
35
+
cdaltk-evolve
36
36
uv venv --python=3.12 &&source .venv/bin/activate
37
37
uv sync
38
38
```
@@ -44,7 +44,7 @@ For direct OpenAI usage:
44
44
export OPENAI_API_KEY=sk-...
45
45
```
46
46
47
-
For LiteLLM proxy usage and model selection (including global fallback via `EVOLVE_MODEL_NAME`), see [CONFIGURATION.md](CONFIGURATION.md).
47
+
For LiteLLM proxy usage and model selection (including global fallback via `EVOLVE_MODEL_NAME`), see [the configuration guide](docs/guides/configuration.md).
48
48
49
49
### Running the MCP Server & UI
50
50
@@ -102,7 +102,7 @@ Evolve automatically tracks the origin of every guideline it generates or stores
102
102
-`creation_mode`: Identifies how the tip was created (`auto-phoenix` via trace observability, `auto-mcp` via trajectory saving tools, or `manual`).
103
103
-`source_task_id`: The ID of the original trace or task that inspired the tip, providing full audibility.
104
104
105
-
See the [Low-Code Tracing Guide](docs/LOW_CODE_TRACING.md#6-understanding-tip-provenance-metadata) for more details.
105
+
See the [Low-Code Tracing Guide](docs/guides/low-code-tracing.md#6-understanding-tip-provenance-metadata) for more details.
106
106
107
107
108
108
## Community & Feedback
@@ -115,11 +115,13 @@ If you’re experimenting with Evolve or exploring on‑the‑job learning for a
115
115
116
116
## Documentation
117
117
118
-
-[EVOLVE_LITE.md](EVOLVE_LITE.md) - Lightweight mode via Claude Code plugin (no infra required)
Copy file name to clipboardExpand all lines: docs/examples/hello_world/index.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,9 +14,9 @@ uv init
14
14
```
15
15
16
16
## Step 2: Install Evolve
17
-
Install Evolve by following the [installation instructions](../../installation), or run:
17
+
Install Evolve by following the [installation instructions](../../installation/index.md), or run:
18
18
```bash
19
-
curl -fsSL https://raw.githubusercontent.com/AgentToolkit/evolve/main/platform-integrations/install.sh | bash -s -- install --platform bob --mode lite
19
+
curl -fsSL https://raw.githubusercontent.com/AgentToolkit/altk-evolve/main/platform-integrations/install.sh | bash -s -- install --platform bob --mode lite
20
20
```
21
21
## Step 3: Project Setup
22
22
Open the project directory in IBM Bob IDE, and switch Bob's mode to `Evolve Lite`
@@ -42,4 +42,4 @@ At this point, Bob will correct itself and eventually run `uv sync` and correctl
42
42
Bob should then run some Evolve Lite skills to save the learned correction into memory.
43
43
If it does not, the `/evolve:learn` command can be used to manually run the skill.
44
44
45
-
In the future, Bob should remember via Evolve-Lite skills that `uv` is used for this project and not make the same mistake. This can be tested in this toy project by deleting the `.venv` and `uv.lock`folder and trying the same utterance again.
45
+
In the future, Bob should remember via Evolve-Lite skills that `uv` is used for this project and not make the same mistake. This can be tested in this toy project by deleting the `.venv`directory and the `uv.lock`file and trying the same utterance again.
Copy file name to clipboardExpand all lines: docs/guides/extract-trajectories.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Extract Trajectories from Arize Phoenix
2
2
3
-
A Python tool to extract agent trajectories from Arize Phoenix traces and convert them to OpenAI chat completion message format.
3
+
A Python utility at `scripts/extract_trajectories.py` for extracting agent trajectories from Arize Phoenix traces and converting them to OpenAI chat completion message format.
4
4
5
5
## Features
6
6
@@ -23,25 +23,25 @@ A Python tool to extract agent trajectories from Arize Phoenix traces and conver
23
23
24
24
```bash
25
25
# Get recent trajectories as JSON (pretty-printed)
0 commit comments