Added restart script and fixed dockerfile and run to match docs
This commit is contained in:
3
.gitignore
vendored
3
.gitignore
vendored
@@ -1,5 +1,4 @@
|
||||
.env
|
||||
pdf/
|
||||
data/
|
||||
model/
|
||||
claude.txt
|
||||
__pycache__/
|
||||
18
Dockerfile
18
Dockerfile
@@ -10,7 +10,7 @@ RUN rm -rf /requirements.txt
|
||||
FROM requirements AS sia-test
|
||||
COPY ./ /root/sia/
|
||||
WORKDIR /root/sia/
|
||||
RUN mkdir -p /root/model
|
||||
RUN mkdir -p /root/models/current
|
||||
CMD ["python3", "-m", "unittest", "discover", "-v", "-p", "*test.py"]
|
||||
|
||||
FROM node:20-alpine AS web-test
|
||||
@@ -36,14 +36,22 @@ RUN apt-get update
|
||||
RUN apt-get install -y google-chrome-stable
|
||||
RUN rm -rf /var/lib/apt/lists/*
|
||||
|
||||
RUN mkdir -p \
|
||||
/root/sia \
|
||||
/root/data/iterations \
|
||||
/root/data/user \
|
||||
/root/data/tasks \
|
||||
/root/data/environment \
|
||||
/root/models \
|
||||
/root/desktop
|
||||
|
||||
COPY ./tools/itb/requirements.txt /root/sia/tools/itb/requirements.txt
|
||||
RUN cd /root/sia/tools/itb/ && python3 -m pip install -r requirements.txt
|
||||
|
||||
COPY ./tools/ /root/sia/tools/
|
||||
RUN cd /root/sia/tools/itb/ && python3 -m pip install -e ".[dev]"
|
||||
|
||||
COPY ./ /root/sia/
|
||||
COPY --from=web-build /app/dist /root/sia/static/
|
||||
WORKDIR /root/sia
|
||||
COPY --from=web-build /app/dist /root/static/
|
||||
WORKDIR /root/desktop
|
||||
|
||||
CMD ["python3", "-m", "sia"]
|
||||
CMD ["/root/sia/scripts/restart.sh"]
|
||||
2991
collect.txt
Normal file
2991
collect.txt
Normal file
File diff suppressed because it is too large
Load Diff
0
container.sh → scripts/container.sh
Executable file → Normal file
0
container.sh → scripts/container.sh
Executable file → Normal file
11
scripts/restart.sh
Normal file
11
scripts/restart.sh
Normal file
@@ -0,0 +1,11 @@
|
||||
#!/bin/bash
|
||||
|
||||
while true; do
|
||||
PYTHONPATH="/root/sia:$PYTHONPATH" python3 -m sia
|
||||
if [ $? -eq 42 ]; then
|
||||
echo "SIA exited with code 42. Restarting."
|
||||
else
|
||||
echo "SIA exited with code $?. Not restarting."
|
||||
break
|
||||
fi
|
||||
done
|
||||
14
run.sh → scripts/run.sh
Executable file → Normal file
14
run.sh → scripts/run.sh
Executable file → Normal file
@@ -22,11 +22,13 @@ docker run \
|
||||
-ti \
|
||||
--gpus=all \
|
||||
-p 8080:8080 \
|
||||
-e SIA_ITERATIONS_DIR=/root/iterations \
|
||||
--env-file .env \
|
||||
-v /$(pwd)/model/:/root/model/ \
|
||||
-v /$(pwd)/.env:/root/.env \
|
||||
-v /$(pwd)/iterations/:/root/iterations/ \
|
||||
-v /$(pwd)/tools/:/root/sia/tools/ \
|
||||
-v /$(pwd)/.git/:/root/sia/.git/ \
|
||||
-v /$(pwd)/model/:/root/models/current/ \
|
||||
-v /$(pwd)/iterations/:/root/data/iterations/ \
|
||||
-v /$(pwd)/tasks/:/root/data/tasks/ \
|
||||
-v /$(pwd)/user/:/root/data/user/ \
|
||||
-v /$(pwd)/environment/:/root/data/environment/ \
|
||||
-v /$(pwd)/:/root/sia/ \
|
||||
sia "$@"
|
||||
|
||||
exit $?
|
||||
0
test.sh → scripts/test.sh
Executable file → Normal file
0
test.sh → scripts/test.sh
Executable file → Normal file
@@ -15,26 +15,26 @@ class Config:
|
||||
parser.add_argument(
|
||||
'--system-prompt',
|
||||
type=Path,
|
||||
default=os.getenv('SIA_SYSTEM_PROMPT', 'system_prompt.md'),
|
||||
help='Path to the system prompt file (default: system_prompt.md, env: SIA_SYSTEM_PROMPT)'
|
||||
default=os.getenv('SIA_SYSTEM_PROMPT', '/root/sia/system_prompt.md'),
|
||||
help='Path to the system prompt file (default: /root/sia/system_prompt.md, env: SIA_SYSTEM_PROMPT)'
|
||||
)
|
||||
parser.add_argument(
|
||||
'--action-schema',
|
||||
type=Path,
|
||||
default=os.getenv('SIA_ACTION_SCHEMA', 'action_schema.xsd'),
|
||||
help='Path to the action schema file (default: action_schema.xsd, env: SIA_ACTION_SCHEMA)'
|
||||
default=os.getenv('SIA_ACTION_SCHEMA', '/root/sia/action_schema.xsd'),
|
||||
help='Path to the action schema file (default: /root/sia/action_schema.xsd, env: SIA_ACTION_SCHEMA)'
|
||||
)
|
||||
parser.add_argument(
|
||||
'--iterations-dir',
|
||||
type=Path,
|
||||
default=os.getenv('SIA_ITERATIONS_DIR', 'iterations'),
|
||||
help='Path to the directory for storing iterations (default: iterations, env: SIA_ITERATIONS_DIR)'
|
||||
default=os.getenv('SIA_ITERATIONS_DIR', '/root/data/iterations'),
|
||||
help='Path to the directory for storing iterations (default: /root/data/iterations, env: SIA_ITERATIONS_DIR)'
|
||||
)
|
||||
parser.add_argument(
|
||||
'--work-dir',
|
||||
type=Path,
|
||||
default=os.getenv('SIA_WORK_DIR', '/root'),
|
||||
help='Path to the working directory (default: /root, env: SIA_WORK_DIR)'
|
||||
default=os.getenv('SIA_WORK_DIR', '/root/desktop'),
|
||||
help='Path to the working directory (default: /root/desktop, env: SIA_WORK_DIR)'
|
||||
)
|
||||
|
||||
# Web server configuration
|
||||
@@ -59,8 +59,8 @@ class Config:
|
||||
parser.add_argument(
|
||||
'--static-files',
|
||||
type=Path,
|
||||
default=self._parse_optional_path('SIA_STATIC_FILES', './static/'),
|
||||
help='Path to static web files (default: ./static/, env: SIA_STATIC_FILES)'
|
||||
default=self._parse_optional_path('SIA_STATIC_FILES', '/root/static/'),
|
||||
help='Path to static web files (default: /root/static/, env: SIA_STATIC_FILES)'
|
||||
)
|
||||
|
||||
# Local LLM configuration
|
||||
@@ -73,8 +73,8 @@ class Config:
|
||||
parser.add_argument(
|
||||
'--local-model',
|
||||
type=str,
|
||||
default=os.getenv('SIA_LOCAL_MODEL', '/root/model/'),
|
||||
help='Path to local model directory (default: /root/model/, env: SIA_LOCAL_MODEL)'
|
||||
default=os.getenv('SIA_LOCAL_MODEL', '/root/models/current'),
|
||||
help='Path to local model directory (default: /root/models/current, env: SIA_LOCAL_MODEL)'
|
||||
)
|
||||
parser.add_argument(
|
||||
'--local-temperature',
|
||||
|
||||
@@ -1,8 +1,9 @@
|
||||
from collections import defaultdict
|
||||
from datetime import datetime, timezone
|
||||
from enum import Enum, auto
|
||||
from sys import exit
|
||||
from threading import Lock
|
||||
from typing import Callable, Dict, List, Optional
|
||||
from collections import defaultdict
|
||||
|
||||
from .base_agent import BaseAgent
|
||||
from .command import Command
|
||||
@@ -160,7 +161,9 @@ class WebAgent(BaseAgent):
|
||||
if isinstance(parse_result, Command):
|
||||
result = parse_result.execute(self._working_memory)
|
||||
self._command_result = result
|
||||
if not result.should_stop:
|
||||
if result.should_stop:
|
||||
exit(42)
|
||||
else:
|
||||
self._working_memory.update()
|
||||
else:
|
||||
parse_result.update()
|
||||
|
||||
@@ -1,4 +0,0 @@
|
||||
The unit tests for the sia project are no longer up-to-date.
|
||||
Find failing unit tests and fix them.
|
||||
Find missing unit tests and write them.
|
||||
Make regular commits to the git repo in the /root/sia directory but don't push them.
|
||||
@@ -1,5 +0,0 @@
|
||||
The SIA source is located in /root/sia.
|
||||
Not all features are implemented yet.
|
||||
Look at the readme and code to find what is missing.
|
||||
Make sure to unit test your work.
|
||||
Make commits to the git repo when a features are done but don't push them.
|
||||
@@ -1,4 +0,0 @@
|
||||
Look online for christmas toys for my 5 year old nephew.
|
||||
I believe he likes Kapla.
|
||||
Look for a large set.
|
||||
It can be a knock-off.
|
||||
@@ -23,7 +23,7 @@ class Config:
|
||||
parser.add_argument(
|
||||
'--config',
|
||||
type=Path,
|
||||
default=os.getenv('SIA_TRAINING_CONFIG', 'training/config.yaml'),
|
||||
default=os.getenv('SIA_TRAINING_CONFIG', '/root/sia/training/config.yaml'),
|
||||
help='Path to config file'
|
||||
)
|
||||
parser.add_argument(
|
||||
|
||||
@@ -8,5 +8,5 @@
|
||||
stdin="0"
|
||||
time="2025-01-16T13:45:04Z">
|
||||
</context></context><response><reasoning>
|
||||
I should start by exploring the file system to understand the environment and identify any relevant files or directories.
|
||||
It seems like I have just restarted. I should list the procedures and look for an initialization procedure.
|
||||
</reasoning></response></iteration>
|
||||
@@ -8,10 +8,8 @@
|
||||
stdin="0"
|
||||
time="2025-01-16T13:45:49Z">
|
||||
<reasoning id="20250116_134549_655">
|
||||
<![CDATA[
|
||||
I should start by exploring the file system to understand the environment and identify any relevant files or directories.
|
||||
]]>
|
||||
<![CDATA[It seems like I have just restarted. I should list the procedures and look for an initialization procedure.]]>
|
||||
</reasoning>
|
||||
</context></context><response><single>
|
||||
ls /
|
||||
ls -la /root/sia/procedures
|
||||
</single></response></iteration>
|
||||
@@ -1,53 +0,0 @@
|
||||
<?xml version='1.0' encoding='utf-8'?>
|
||||
<iteration system_prompt_hash="a357171f34284409058700f0d6c20cbb4f4bfe643aff5b12168c5158767f89b4" action_schema_hash="a4cf87f3d53c7b14aab3c96097d8b7bf838e8f77e413d11f51051afbe22fa3a6"><context><context
|
||||
context="6.61%"
|
||||
disk_total="1081101176832"
|
||||
disk_used="42638553088"
|
||||
memory_total="16630435840"
|
||||
memory_used="1060290560"
|
||||
stdin="0"
|
||||
time="2025-01-16T13:45:55Z">
|
||||
<reasoning id="20250116_134549_655">
|
||||
<![CDATA[
|
||||
I should start by exploring the file system to understand the environment and identify any relevant files or directories.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134555_680">
|
||||
<![CDATA[
|
||||
ls /
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[NGC-DL-CONTAINER-LICENSE
|
||||
bin
|
||||
boot
|
||||
cuda-keyring_1.0-1_all.deb
|
||||
dev
|
||||
etc
|
||||
home
|
||||
lib
|
||||
lib32
|
||||
lib64
|
||||
libx32
|
||||
media
|
||||
mnt
|
||||
opt
|
||||
proc
|
||||
root
|
||||
run
|
||||
sbin
|
||||
srv
|
||||
sys
|
||||
tmp
|
||||
usr
|
||||
var
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
</context></context><response><reasoning>
|
||||
<![CDATA[
|
||||
The file system contains several standard directories such as /bin, /etc, /home, /usr, and /var.
|
||||
To get a better understanding of the environment, I should explore the /root directory to see if there are any user-specific files or directories.
|
||||
I will use the `ls /root` command to list the contents of the /root directory.
|
||||
]]>
|
||||
</reasoning></response></iteration>
|
||||
@@ -1,58 +0,0 @@
|
||||
<?xml version='1.0' encoding='utf-8'?>
|
||||
<iteration system_prompt_hash="a357171f34284409058700f0d6c20cbb4f4bfe643aff5b12168c5158767f89b4" action_schema_hash="a4cf87f3d53c7b14aab3c96097d8b7bf838e8f77e413d11f51051afbe22fa3a6"><context><context
|
||||
context="6.95%"
|
||||
disk_total="1081101176832"
|
||||
disk_used="42638553088"
|
||||
memory_total="16630435840"
|
||||
memory_used="1066680320"
|
||||
stdin="0"
|
||||
time="2025-01-16T13:46:39Z">
|
||||
<reasoning id="20250116_134549_655">
|
||||
<![CDATA[
|
||||
I should start by exploring the file system to understand the environment and identify any relevant files or directories.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134555_680">
|
||||
<![CDATA[
|
||||
ls /
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[NGC-DL-CONTAINER-LICENSE
|
||||
bin
|
||||
boot
|
||||
cuda-keyring_1.0-1_all.deb
|
||||
dev
|
||||
etc
|
||||
home
|
||||
lib
|
||||
lib32
|
||||
lib64
|
||||
libx32
|
||||
media
|
||||
mnt
|
||||
opt
|
||||
proc
|
||||
root
|
||||
run
|
||||
sbin
|
||||
srv
|
||||
sys
|
||||
tmp
|
||||
usr
|
||||
var
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_134639_663">
|
||||
<![CDATA[
|
||||
|
||||
The file system contains several standard directories such as /bin, /etc, /home, /usr, and /var.
|
||||
To get a better understanding of the environment, I should explore the /root directory to see if there are any user-specific files or directories.
|
||||
I will use the `ls /root` command to list the contents of the /root directory.
|
||||
|
||||
]]>
|
||||
</reasoning>
|
||||
</context></context><response><single>
|
||||
ls /root
|
||||
</single></response></iteration>
|
||||
@@ -1,72 +0,0 @@
|
||||
<?xml version='1.0' encoding='utf-8'?>
|
||||
<iteration system_prompt_hash="a357171f34284409058700f0d6c20cbb4f4bfe643aff5b12168c5158767f89b4" action_schema_hash="a4cf87f3d53c7b14aab3c96097d8b7bf838e8f77e413d11f51051afbe22fa3a6"><context><context
|
||||
context="7.15%"
|
||||
disk_total="1081101176832"
|
||||
disk_used="42638553088"
|
||||
memory_total="16630435840"
|
||||
memory_used="1068597248"
|
||||
stdin="0"
|
||||
time="2025-01-16T13:46:44Z">
|
||||
<reasoning id="20250116_134549_655">
|
||||
<![CDATA[
|
||||
I should start by exploring the file system to understand the environment and identify any relevant files or directories.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134555_680">
|
||||
<![CDATA[
|
||||
ls /
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[NGC-DL-CONTAINER-LICENSE
|
||||
bin
|
||||
boot
|
||||
cuda-keyring_1.0-1_all.deb
|
||||
dev
|
||||
etc
|
||||
home
|
||||
lib
|
||||
lib32
|
||||
lib64
|
||||
libx32
|
||||
media
|
||||
mnt
|
||||
opt
|
||||
proc
|
||||
root
|
||||
run
|
||||
sbin
|
||||
srv
|
||||
sys
|
||||
tmp
|
||||
usr
|
||||
var
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_134639_663">
|
||||
<![CDATA[
|
||||
|
||||
The file system contains several standard directories such as /bin, /etc, /home, /usr, and /var.
|
||||
To get a better understanding of the environment, I should explore the /root directory to see if there are any user-specific files or directories.
|
||||
I will use the `ls /root` command to list the contents of the /root directory.
|
||||
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134644_445">
|
||||
<![CDATA[
|
||||
ls /root
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[iterations
|
||||
model
|
||||
sia
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
</context></context><response><reasoning>
|
||||
The /root directory contains three items: iterations, model, and sia.
|
||||
I should explore the contents of these directories to understand their purpose and relevance.
|
||||
I will start by listing the contents of the /root/iterations directory using the `ls /root/iterations` command.
|
||||
</reasoning></response></iteration>
|
||||
@@ -1,77 +0,0 @@
|
||||
<?xml version='1.0' encoding='utf-8'?>
|
||||
<iteration system_prompt_hash="a357171f34284409058700f0d6c20cbb4f4bfe643aff5b12168c5158767f89b4" action_schema_hash="a4cf87f3d53c7b14aab3c96097d8b7bf838e8f77e413d11f51051afbe22fa3a6"><context><context
|
||||
context="7.43%"
|
||||
disk_total="1081101176832"
|
||||
disk_used="42638553088"
|
||||
memory_total="16630435840"
|
||||
memory_used="1057677312"
|
||||
stdin="0"
|
||||
time="2025-01-16T13:47:29Z">
|
||||
<reasoning id="20250116_134549_655">
|
||||
<![CDATA[
|
||||
I should start by exploring the file system to understand the environment and identify any relevant files or directories.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134555_680">
|
||||
<![CDATA[
|
||||
ls /
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[NGC-DL-CONTAINER-LICENSE
|
||||
bin
|
||||
boot
|
||||
cuda-keyring_1.0-1_all.deb
|
||||
dev
|
||||
etc
|
||||
home
|
||||
lib
|
||||
lib32
|
||||
lib64
|
||||
libx32
|
||||
media
|
||||
mnt
|
||||
opt
|
||||
proc
|
||||
root
|
||||
run
|
||||
sbin
|
||||
srv
|
||||
sys
|
||||
tmp
|
||||
usr
|
||||
var
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_134639_663">
|
||||
<![CDATA[
|
||||
|
||||
The file system contains several standard directories such as /bin, /etc, /home, /usr, and /var.
|
||||
To get a better understanding of the environment, I should explore the /root directory to see if there are any user-specific files or directories.
|
||||
I will use the `ls /root` command to list the contents of the /root directory.
|
||||
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134644_445">
|
||||
<![CDATA[
|
||||
ls /root
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[iterations
|
||||
model
|
||||
sia
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_134729_674">
|
||||
<![CDATA[
|
||||
The /root directory contains three items: iterations, model, and sia.
|
||||
I should explore the contents of these directories to understand their purpose and relevance.
|
||||
I will start by listing the contents of the /root/iterations directory using the `ls /root/iterations` command.
|
||||
]]>
|
||||
</reasoning>
|
||||
</context></context><response><single>
|
||||
ls /root/iterations
|
||||
</single></response></iteration>
|
||||
@@ -1,94 +0,0 @@
|
||||
<?xml version='1.0' encoding='utf-8'?>
|
||||
<iteration system_prompt_hash="a357171f34284409058700f0d6c20cbb4f4bfe643aff5b12168c5158767f89b4" action_schema_hash="a4cf87f3d53c7b14aab3c96097d8b7bf838e8f77e413d11f51051afbe22fa3a6"><context><context
|
||||
context="7.85%"
|
||||
disk_total="1081101176832"
|
||||
disk_used="42638553088"
|
||||
memory_total="16630435840"
|
||||
memory_used="1059065856"
|
||||
stdin="0"
|
||||
time="2025-01-16T13:47:36Z">
|
||||
<reasoning id="20250116_134549_655">
|
||||
<![CDATA[
|
||||
I should start by exploring the file system to understand the environment and identify any relevant files or directories.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134555_680">
|
||||
<![CDATA[
|
||||
ls /
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[NGC-DL-CONTAINER-LICENSE
|
||||
bin
|
||||
boot
|
||||
cuda-keyring_1.0-1_all.deb
|
||||
dev
|
||||
etc
|
||||
home
|
||||
lib
|
||||
lib32
|
||||
lib64
|
||||
libx32
|
||||
media
|
||||
mnt
|
||||
opt
|
||||
proc
|
||||
root
|
||||
run
|
||||
sbin
|
||||
srv
|
||||
sys
|
||||
tmp
|
||||
usr
|
||||
var
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_134639_663">
|
||||
<![CDATA[
|
||||
|
||||
The file system contains several standard directories such as /bin, /etc, /home, /usr, and /var.
|
||||
To get a better understanding of the environment, I should explore the /root directory to see if there are any user-specific files or directories.
|
||||
I will use the `ls /root` command to list the contents of the /root directory.
|
||||
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134644_445">
|
||||
<![CDATA[
|
||||
ls /root
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[iterations
|
||||
model
|
||||
sia
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_134729_674">
|
||||
<![CDATA[
|
||||
The /root directory contains three items: iterations, model, and sia.
|
||||
I should explore the contents of these directories to understand their purpose and relevance.
|
||||
I will start by listing the contents of the /root/iterations directory using the `ls /root/iterations` command.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134736_148">
|
||||
<![CDATA[
|
||||
ls /root/iterations
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[iteration_20250116_134549_655.xml
|
||||
iteration_20250116_134555_680.xml
|
||||
iteration_20250116_134639_663.xml
|
||||
iteration_20250116_134644_445.xml
|
||||
iteration_20250116_134729_674.xml
|
||||
iteration_20250116_134736_148.xml
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
</context></context><response><reasoning>
|
||||
There are not tasks in the root directory and the iterations directory only contains what I'just done.
|
||||
This is a clean start of SIA.
|
||||
I should look for procedures to follow in the `/root/sia/procedures` directory.
|
||||
</reasoning></response></iteration>
|
||||
@@ -1,99 +0,0 @@
|
||||
<?xml version='1.0' encoding='utf-8'?>
|
||||
<iteration system_prompt_hash="a357171f34284409058700f0d6c20cbb4f4bfe643aff5b12168c5158767f89b4" action_schema_hash="a4cf87f3d53c7b14aab3c96097d8b7bf838e8f77e413d11f51051afbe22fa3a6"><context><context
|
||||
context="8.1%"
|
||||
disk_total="1081101176832"
|
||||
disk_used="42638553088"
|
||||
memory_total="16630435840"
|
||||
memory_used="1065271296"
|
||||
stdin="0"
|
||||
time="2025-01-16T13:50:16Z">
|
||||
<reasoning id="20250116_134549_655">
|
||||
<![CDATA[
|
||||
I should start by exploring the file system to understand the environment and identify any relevant files or directories.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134555_680">
|
||||
<![CDATA[
|
||||
ls /
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[NGC-DL-CONTAINER-LICENSE
|
||||
bin
|
||||
boot
|
||||
cuda-keyring_1.0-1_all.deb
|
||||
dev
|
||||
etc
|
||||
home
|
||||
lib
|
||||
lib32
|
||||
lib64
|
||||
libx32
|
||||
media
|
||||
mnt
|
||||
opt
|
||||
proc
|
||||
root
|
||||
run
|
||||
sbin
|
||||
srv
|
||||
sys
|
||||
tmp
|
||||
usr
|
||||
var
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_134639_663">
|
||||
<![CDATA[
|
||||
|
||||
The file system contains several standard directories such as /bin, /etc, /home, /usr, and /var.
|
||||
To get a better understanding of the environment, I should explore the /root directory to see if there are any user-specific files or directories.
|
||||
I will use the `ls /root` command to list the contents of the /root directory.
|
||||
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134644_445">
|
||||
<![CDATA[
|
||||
ls /root
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[iterations
|
||||
model
|
||||
sia
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_134729_674">
|
||||
<![CDATA[
|
||||
The /root directory contains three items: iterations, model, and sia.
|
||||
I should explore the contents of these directories to understand their purpose and relevance.
|
||||
I will start by listing the contents of the /root/iterations directory using the `ls /root/iterations` command.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134736_148">
|
||||
<![CDATA[
|
||||
ls /root/iterations
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[iteration_20250116_134549_655.xml
|
||||
iteration_20250116_134555_680.xml
|
||||
iteration_20250116_134639_663.xml
|
||||
iteration_20250116_134644_445.xml
|
||||
iteration_20250116_134729_674.xml
|
||||
iteration_20250116_134736_148.xml
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_135016_476">
|
||||
<![CDATA[
|
||||
There are not tasks in the root directory and the iterations directory only contains what I'just done.
|
||||
This is a clean start of SIA.
|
||||
I should look for procedures to follow in the `/root/sia/procedures` directory.
|
||||
]]>
|
||||
</reasoning>
|
||||
</context></context><response><single>
|
||||
ls /root/sia/procedures
|
||||
</single></response></iteration>
|
||||
@@ -1,113 +0,0 @@
|
||||
<?xml version='1.0' encoding='utf-8'?>
|
||||
<iteration system_prompt_hash="a357171f34284409058700f0d6c20cbb4f4bfe643aff5b12168c5158767f89b4" action_schema_hash="a4cf87f3d53c7b14aab3c96097d8b7bf838e8f77e413d11f51051afbe22fa3a6"><context><context
|
||||
context="8.33%"
|
||||
disk_total="1081101176832"
|
||||
disk_used="42638553088"
|
||||
memory_total="16630435840"
|
||||
memory_used="1065758720"
|
||||
stdin="0"
|
||||
time="2025-01-16T13:50:24Z">
|
||||
<reasoning id="20250116_134549_655">
|
||||
<![CDATA[
|
||||
I should start by exploring the file system to understand the environment and identify any relevant files or directories.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134555_680">
|
||||
<![CDATA[
|
||||
ls /
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[NGC-DL-CONTAINER-LICENSE
|
||||
bin
|
||||
boot
|
||||
cuda-keyring_1.0-1_all.deb
|
||||
dev
|
||||
etc
|
||||
home
|
||||
lib
|
||||
lib32
|
||||
lib64
|
||||
libx32
|
||||
media
|
||||
mnt
|
||||
opt
|
||||
proc
|
||||
root
|
||||
run
|
||||
sbin
|
||||
srv
|
||||
sys
|
||||
tmp
|
||||
usr
|
||||
var
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_134639_663">
|
||||
<![CDATA[
|
||||
|
||||
The file system contains several standard directories such as /bin, /etc, /home, /usr, and /var.
|
||||
To get a better understanding of the environment, I should explore the /root directory to see if there are any user-specific files or directories.
|
||||
I will use the `ls /root` command to list the contents of the /root directory.
|
||||
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134644_445">
|
||||
<![CDATA[
|
||||
ls /root
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[iterations
|
||||
model
|
||||
sia
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_134729_674">
|
||||
<![CDATA[
|
||||
The /root directory contains three items: iterations, model, and sia.
|
||||
I should explore the contents of these directories to understand their purpose and relevance.
|
||||
I will start by listing the contents of the /root/iterations directory using the `ls /root/iterations` command.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134736_148">
|
||||
<![CDATA[
|
||||
ls /root/iterations
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[iteration_20250116_134549_655.xml
|
||||
iteration_20250116_134555_680.xml
|
||||
iteration_20250116_134639_663.xml
|
||||
iteration_20250116_134644_445.xml
|
||||
iteration_20250116_134729_674.xml
|
||||
iteration_20250116_134736_148.xml
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_135016_476">
|
||||
<![CDATA[
|
||||
There are not tasks in the root directory and the iterations directory only contains what I'just done.
|
||||
This is a clean start of SIA.
|
||||
I should look for procedures to follow in the `/root/sia/procedures` directory.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_135024_642">
|
||||
<![CDATA[
|
||||
ls /root/sia/procedures
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[README.md
|
||||
user_communication
|
||||
using_procedures
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
</context></context><response><reasoning>
|
||||
There are no specific procedures to follow.
|
||||
I will ask the user what I should do.
|
||||
I'll load the `using_procedures` and `user_communication` procedures.
|
||||
</reasoning></response></iteration>
|
||||
@@ -1,119 +0,0 @@
|
||||
<?xml version='1.0' encoding='utf-8'?>
|
||||
<iteration system_prompt_hash="a357171f34284409058700f0d6c20cbb4f4bfe643aff5b12168c5158767f89b4" action_schema_hash="a4cf87f3d53c7b14aab3c96097d8b7bf838e8f77e413d11f51051afbe22fa3a6"><context><context
|
||||
context="8.55%"
|
||||
disk_total="1081101176832"
|
||||
disk_used="42638553088"
|
||||
memory_total="16630435840"
|
||||
memory_used="1067671552"
|
||||
stdin="0"
|
||||
time="2025-01-16T13:52:32Z">
|
||||
<reasoning id="20250116_134549_655">
|
||||
<![CDATA[
|
||||
I should start by exploring the file system to understand the environment and identify any relevant files or directories.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134555_680">
|
||||
<![CDATA[
|
||||
ls /
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[NGC-DL-CONTAINER-LICENSE
|
||||
bin
|
||||
boot
|
||||
cuda-keyring_1.0-1_all.deb
|
||||
dev
|
||||
etc
|
||||
home
|
||||
lib
|
||||
lib32
|
||||
lib64
|
||||
libx32
|
||||
media
|
||||
mnt
|
||||
opt
|
||||
proc
|
||||
root
|
||||
run
|
||||
sbin
|
||||
srv
|
||||
sys
|
||||
tmp
|
||||
usr
|
||||
var
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_134639_663">
|
||||
<![CDATA[
|
||||
|
||||
The file system contains several standard directories such as /bin, /etc, /home, /usr, and /var.
|
||||
To get a better understanding of the environment, I should explore the /root directory to see if there are any user-specific files or directories.
|
||||
I will use the `ls /root` command to list the contents of the /root directory.
|
||||
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134644_445">
|
||||
<![CDATA[
|
||||
ls /root
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[iterations
|
||||
model
|
||||
sia
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_134729_674">
|
||||
<![CDATA[
|
||||
The /root directory contains three items: iterations, model, and sia.
|
||||
I should explore the contents of these directories to understand their purpose and relevance.
|
||||
I will start by listing the contents of the /root/iterations directory using the `ls /root/iterations` command.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134736_148">
|
||||
<![CDATA[
|
||||
ls /root/iterations
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[iteration_20250116_134549_655.xml
|
||||
iteration_20250116_134555_680.xml
|
||||
iteration_20250116_134639_663.xml
|
||||
iteration_20250116_134644_445.xml
|
||||
iteration_20250116_134729_674.xml
|
||||
iteration_20250116_134736_148.xml
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_135016_476">
|
||||
<![CDATA[
|
||||
There are not tasks in the root directory and the iterations directory only contains what I'just done.
|
||||
This is a clean start of SIA.
|
||||
I should look for procedures to follow in the `/root/sia/procedures` directory.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_135024_642">
|
||||
<![CDATA[
|
||||
ls /root/sia/procedures
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[README.md
|
||||
user_communication
|
||||
using_procedures
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_135232_795">
|
||||
<![CDATA[
|
||||
There are no specific procedures to follow.
|
||||
I will ask the user what I should do.
|
||||
I'll load the `using_procedures` and `user_communication` procedures.
|
||||
]]>
|
||||
</reasoning>
|
||||
</context></context><response><single>
|
||||
ls -la /root/sia/procedures/using_procedures
|
||||
ls -la /root/sia/procedures/user_communication
|
||||
</single></response></iteration>
|
||||
@@ -1,139 +0,0 @@
|
||||
<?xml version='1.0' encoding='utf-8'?>
|
||||
<iteration system_prompt_hash="a357171f34284409058700f0d6c20cbb4f4bfe643aff5b12168c5158767f89b4" action_schema_hash="a4cf87f3d53c7b14aab3c96097d8b7bf838e8f77e413d11f51051afbe22fa3a6"><context><context
|
||||
context="9.52%"
|
||||
disk_total="1081101176832"
|
||||
disk_used="42638553088"
|
||||
memory_total="16630435840"
|
||||
memory_used="1073836032"
|
||||
stdin="0"
|
||||
time="2025-01-16T13:52:53Z">
|
||||
<reasoning id="20250116_134549_655">
|
||||
<![CDATA[
|
||||
I should start by exploring the file system to understand the environment and identify any relevant files or directories.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134555_680">
|
||||
<![CDATA[
|
||||
ls /
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[NGC-DL-CONTAINER-LICENSE
|
||||
bin
|
||||
boot
|
||||
cuda-keyring_1.0-1_all.deb
|
||||
dev
|
||||
etc
|
||||
home
|
||||
lib
|
||||
lib32
|
||||
lib64
|
||||
libx32
|
||||
media
|
||||
mnt
|
||||
opt
|
||||
proc
|
||||
root
|
||||
run
|
||||
sbin
|
||||
srv
|
||||
sys
|
||||
tmp
|
||||
usr
|
||||
var
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_134639_663">
|
||||
<![CDATA[
|
||||
|
||||
The file system contains several standard directories such as /bin, /etc, /home, /usr, and /var.
|
||||
To get a better understanding of the environment, I should explore the /root directory to see if there are any user-specific files or directories.
|
||||
I will use the `ls /root` command to list the contents of the /root directory.
|
||||
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134644_445">
|
||||
<![CDATA[
|
||||
ls /root
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[iterations
|
||||
model
|
||||
sia
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_134729_674">
|
||||
<![CDATA[
|
||||
The /root directory contains three items: iterations, model, and sia.
|
||||
I should explore the contents of these directories to understand their purpose and relevance.
|
||||
I will start by listing the contents of the /root/iterations directory using the `ls /root/iterations` command.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134736_148">
|
||||
<![CDATA[
|
||||
ls /root/iterations
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[iteration_20250116_134549_655.xml
|
||||
iteration_20250116_134555_680.xml
|
||||
iteration_20250116_134639_663.xml
|
||||
iteration_20250116_134644_445.xml
|
||||
iteration_20250116_134729_674.xml
|
||||
iteration_20250116_134736_148.xml
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_135016_476">
|
||||
<![CDATA[
|
||||
There are not tasks in the root directory and the iterations directory only contains what I'just done.
|
||||
This is a clean start of SIA.
|
||||
I should look for procedures to follow in the `/root/sia/procedures` directory.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_135024_642">
|
||||
<![CDATA[
|
||||
ls /root/sia/procedures
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[README.md
|
||||
user_communication
|
||||
using_procedures
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_135232_795">
|
||||
<![CDATA[
|
||||
There are no specific procedures to follow.
|
||||
I will ask the user what I should do.
|
||||
I'll load the `using_procedures` and `user_communication` procedures.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_135253_387">
|
||||
<![CDATA[
|
||||
ls -la /root/sia/procedures/using_procedures
|
||||
ls -la /root/sia/procedures/user_communication
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[total 16
|
||||
drwxr-xr-x 2 root root 4096 Jan 16 13:44 .
|
||||
drwxr-xr-x 4 root root 4096 Jan 8 08:47 ..
|
||||
-rwxr-xr-x 1 root root 1758 Jan 8 21:40 procedure.md
|
||||
-rwxr-xr-x 1 root root 1831 Jan 8 21:03 reasoning.md
|
||||
total 20
|
||||
drwxr-xr-x 2 root root 4096 Jan 16 13:44 .
|
||||
drwxr-xr-x 4 root root 4096 Jan 8 08:47 ..
|
||||
-rwxr-xr-x 1 root root 244 Jan 7 12:18 description.md
|
||||
-rwxr-xr-x 1 root root 3643 Jan 8 21:49 procedure.md
|
||||
-rwxr-xr-x 1 root root 1035 Jan 7 12:23 reasoning.md
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
</context></context><response><single limit="1758">
|
||||
cat /root/sia/procedures/using_procedures/procedure.md
|
||||
</single></response></iteration>
|
||||
@@ -1,199 +0,0 @@
|
||||
<?xml version='1.0' encoding='utf-8'?>
|
||||
<iteration system_prompt_hash="a357171f34284409058700f0d6c20cbb4f4bfe643aff5b12168c5158767f89b4" action_schema_hash="a4cf87f3d53c7b14aab3c96097d8b7bf838e8f77e413d11f51051afbe22fa3a6"><context><context
|
||||
context="10.97%"
|
||||
disk_total="1081101176832"
|
||||
disk_used="42638553088"
|
||||
memory_total="16630435840"
|
||||
memory_used="1070620672"
|
||||
stdin="0"
|
||||
time="2025-01-16T13:53:43Z">
|
||||
<reasoning id="20250116_134549_655">
|
||||
<![CDATA[
|
||||
I should start by exploring the file system to understand the environment and identify any relevant files or directories.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134555_680">
|
||||
<![CDATA[
|
||||
ls /
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[NGC-DL-CONTAINER-LICENSE
|
||||
bin
|
||||
boot
|
||||
cuda-keyring_1.0-1_all.deb
|
||||
dev
|
||||
etc
|
||||
home
|
||||
lib
|
||||
lib32
|
||||
lib64
|
||||
libx32
|
||||
media
|
||||
mnt
|
||||
opt
|
||||
proc
|
||||
root
|
||||
run
|
||||
sbin
|
||||
srv
|
||||
sys
|
||||
tmp
|
||||
usr
|
||||
var
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_134639_663">
|
||||
<![CDATA[
|
||||
|
||||
The file system contains several standard directories such as /bin, /etc, /home, /usr, and /var.
|
||||
To get a better understanding of the environment, I should explore the /root directory to see if there are any user-specific files or directories.
|
||||
I will use the `ls /root` command to list the contents of the /root directory.
|
||||
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134644_445">
|
||||
<![CDATA[
|
||||
ls /root
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[iterations
|
||||
model
|
||||
sia
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_134729_674">
|
||||
<![CDATA[
|
||||
The /root directory contains three items: iterations, model, and sia.
|
||||
I should explore the contents of these directories to understand their purpose and relevance.
|
||||
I will start by listing the contents of the /root/iterations directory using the `ls /root/iterations` command.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134736_148">
|
||||
<![CDATA[
|
||||
ls /root/iterations
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[iteration_20250116_134549_655.xml
|
||||
iteration_20250116_134555_680.xml
|
||||
iteration_20250116_134639_663.xml
|
||||
iteration_20250116_134644_445.xml
|
||||
iteration_20250116_134729_674.xml
|
||||
iteration_20250116_134736_148.xml
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_135016_476">
|
||||
<![CDATA[
|
||||
There are not tasks in the root directory and the iterations directory only contains what I'just done.
|
||||
This is a clean start of SIA.
|
||||
I should look for procedures to follow in the `/root/sia/procedures` directory.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_135024_642">
|
||||
<![CDATA[
|
||||
ls /root/sia/procedures
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[README.md
|
||||
user_communication
|
||||
using_procedures
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_135232_795">
|
||||
<![CDATA[
|
||||
There are no specific procedures to follow.
|
||||
I will ask the user what I should do.
|
||||
I'll load the `using_procedures` and `user_communication` procedures.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_135253_387">
|
||||
<![CDATA[
|
||||
ls -la /root/sia/procedures/using_procedures
|
||||
ls -la /root/sia/procedures/user_communication
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[total 16
|
||||
drwxr-xr-x 2 root root 4096 Jan 16 13:44 .
|
||||
drwxr-xr-x 4 root root 4096 Jan 8 08:47 ..
|
||||
-rwxr-xr-x 1 root root 1758 Jan 8 21:40 procedure.md
|
||||
-rwxr-xr-x 1 root root 1831 Jan 8 21:03 reasoning.md
|
||||
total 20
|
||||
drwxr-xr-x 2 root root 4096 Jan 16 13:44 .
|
||||
drwxr-xr-x 4 root root 4096 Jan 8 08:47 ..
|
||||
-rwxr-xr-x 1 root root 244 Jan 7 12:18 description.md
|
||||
-rwxr-xr-x 1 root root 3643 Jan 8 21:49 procedure.md
|
||||
-rwxr-xr-x 1 root root 1035 Jan 7 12:23 reasoning.md
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<single exit_code="0" id="20250116_135343_982" limit="1758">
|
||||
<![CDATA[
|
||||
cat /root/sia/procedures/using_procedures/procedure.md
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[# Using Procedures
|
||||
|
||||
## Core Guidelines
|
||||
|
||||
When following a procedure's flowchart:
|
||||
|
||||
1. Start with reasoning:
|
||||
- State current position in flowchart explicitly
|
||||
- Focus on immediate next step, don't go ahead of the chart
|
||||
- Evaluate current context and task state
|
||||
- Often state entry id's that can be removed and explain why to avoid mistakes
|
||||
- State expected output and runtime for scripts
|
||||
|
||||
2. After script execution:
|
||||
- Analyze the actual output and compare with the expected output
|
||||
- Reevaluate situation based on results
|
||||
- Return to flowchart for next step
|
||||
- Consider if current path is still appropriate
|
||||
|
||||
3. When a procedure fails:
|
||||
- Create a task explaining the issue and the need to fix it
|
||||
- Add timestamps and id's of relevant entries
|
||||
|
||||
## Attention Management
|
||||
|
||||
LLMs pay more attention to recently mentioned information.
|
||||
Reasoning entries should mention what needs attention now.
|
||||
|
||||
To maintain focus:
|
||||
1. State current flowchart position in each reasoning
|
||||
2. Quote relevant parts of important entries
|
||||
3. Reference specific entry IDs when using their information
|
||||
4. Periodically remind about ongoing tasks or future needs
|
||||
5. Clean up entries that aren't needed for current step
|
||||
|
||||
Example of good attention management:
|
||||
```xml
|
||||
<reasoning>
|
||||
At node "evaluate_test_results". Entry 45f3d2 shows failed test: "Error: Connection timeout".
|
||||
Will need to check system logs soon (noted in /tasks/reminders.txt, check at 14:00).
|
||||
First focusing on this error.
|
||||
</reasoning>
|
||||
```
|
||||
|
||||
## Reasons to Switch Procedures
|
||||
|
||||
Common triggers:
|
||||
- Data available on stdin
|
||||
- Time matching scheduled task
|
||||
- Error conditions in script output
|
||||
- Resource constraints detected
|
||||
- User input needed]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
</context></context><response><single limit="3643">
|
||||
cat /root/sia/procedures/user_communication/procedure.md
|
||||
</single></response></iteration>
|
||||
@@ -1,280 +0,0 @@
|
||||
<?xml version='1.0' encoding='utf-8'?>
|
||||
<iteration system_prompt_hash="a357171f34284409058700f0d6c20cbb4f4bfe643aff5b12168c5158767f89b4" action_schema_hash="a4cf87f3d53c7b14aab3c96097d8b7bf838e8f77e413d11f51051afbe22fa3a6"><context><context
|
||||
context="13.8%"
|
||||
disk_total="1081101176832"
|
||||
disk_used="42638553088"
|
||||
memory_total="16630435840"
|
||||
memory_used="1072431104"
|
||||
stdin="0"
|
||||
time="2025-01-16T13:54:09Z">
|
||||
<reasoning id="20250116_134549_655">
|
||||
<![CDATA[
|
||||
I should start by exploring the file system to understand the environment and identify any relevant files or directories.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134555_680">
|
||||
<![CDATA[
|
||||
ls /
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[NGC-DL-CONTAINER-LICENSE
|
||||
bin
|
||||
boot
|
||||
cuda-keyring_1.0-1_all.deb
|
||||
dev
|
||||
etc
|
||||
home
|
||||
lib
|
||||
lib32
|
||||
lib64
|
||||
libx32
|
||||
media
|
||||
mnt
|
||||
opt
|
||||
proc
|
||||
root
|
||||
run
|
||||
sbin
|
||||
srv
|
||||
sys
|
||||
tmp
|
||||
usr
|
||||
var
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_134639_663">
|
||||
<![CDATA[
|
||||
|
||||
The file system contains several standard directories such as /bin, /etc, /home, /usr, and /var.
|
||||
To get a better understanding of the environment, I should explore the /root directory to see if there are any user-specific files or directories.
|
||||
I will use the `ls /root` command to list the contents of the /root directory.
|
||||
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134644_445">
|
||||
<![CDATA[
|
||||
ls /root
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[iterations
|
||||
model
|
||||
sia
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_134729_674">
|
||||
<![CDATA[
|
||||
The /root directory contains three items: iterations, model, and sia.
|
||||
I should explore the contents of these directories to understand their purpose and relevance.
|
||||
I will start by listing the contents of the /root/iterations directory using the `ls /root/iterations` command.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134736_148">
|
||||
<![CDATA[
|
||||
ls /root/iterations
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[iteration_20250116_134549_655.xml
|
||||
iteration_20250116_134555_680.xml
|
||||
iteration_20250116_134639_663.xml
|
||||
iteration_20250116_134644_445.xml
|
||||
iteration_20250116_134729_674.xml
|
||||
iteration_20250116_134736_148.xml
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_135016_476">
|
||||
<![CDATA[
|
||||
There are not tasks in the root directory and the iterations directory only contains what I'just done.
|
||||
This is a clean start of SIA.
|
||||
I should look for procedures to follow in the `/root/sia/procedures` directory.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_135024_642">
|
||||
<![CDATA[
|
||||
ls /root/sia/procedures
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[README.md
|
||||
user_communication
|
||||
using_procedures
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_135232_795">
|
||||
<![CDATA[
|
||||
There are no specific procedures to follow.
|
||||
I will ask the user what I should do.
|
||||
I'll load the `using_procedures` and `user_communication` procedures.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_135253_387">
|
||||
<![CDATA[
|
||||
ls -la /root/sia/procedures/using_procedures
|
||||
ls -la /root/sia/procedures/user_communication
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[total 16
|
||||
drwxr-xr-x 2 root root 4096 Jan 16 13:44 .
|
||||
drwxr-xr-x 4 root root 4096 Jan 8 08:47 ..
|
||||
-rwxr-xr-x 1 root root 1758 Jan 8 21:40 procedure.md
|
||||
-rwxr-xr-x 1 root root 1831 Jan 8 21:03 reasoning.md
|
||||
total 20
|
||||
drwxr-xr-x 2 root root 4096 Jan 16 13:44 .
|
||||
drwxr-xr-x 4 root root 4096 Jan 8 08:47 ..
|
||||
-rwxr-xr-x 1 root root 244 Jan 7 12:18 description.md
|
||||
-rwxr-xr-x 1 root root 3643 Jan 8 21:49 procedure.md
|
||||
-rwxr-xr-x 1 root root 1035 Jan 7 12:23 reasoning.md
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<single exit_code="0" id="20250116_135343_982" limit="1758">
|
||||
<![CDATA[
|
||||
cat /root/sia/procedures/using_procedures/procedure.md
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[# Using Procedures
|
||||
|
||||
## Core Guidelines
|
||||
|
||||
When following a procedure's flowchart:
|
||||
|
||||
1. Start with reasoning:
|
||||
- State current position in flowchart explicitly
|
||||
- Focus on immediate next step, don't go ahead of the chart
|
||||
- Evaluate current context and task state
|
||||
- Often state entry id's that can be removed and explain why to avoid mistakes
|
||||
- State expected output and runtime for scripts
|
||||
|
||||
2. After script execution:
|
||||
- Analyze the actual output and compare with the expected output
|
||||
- Reevaluate situation based on results
|
||||
- Return to flowchart for next step
|
||||
- Consider if current path is still appropriate
|
||||
|
||||
3. When a procedure fails:
|
||||
- Create a task explaining the issue and the need to fix it
|
||||
- Add timestamps and id's of relevant entries
|
||||
|
||||
## Attention Management
|
||||
|
||||
LLMs pay more attention to recently mentioned information.
|
||||
Reasoning entries should mention what needs attention now.
|
||||
|
||||
To maintain focus:
|
||||
1. State current flowchart position in each reasoning
|
||||
2. Quote relevant parts of important entries
|
||||
3. Reference specific entry IDs when using their information
|
||||
4. Periodically remind about ongoing tasks or future needs
|
||||
5. Clean up entries that aren't needed for current step
|
||||
|
||||
Example of good attention management:
|
||||
```xml
|
||||
<reasoning>
|
||||
At node "evaluate_test_results". Entry 45f3d2 shows failed test: "Error: Connection timeout".
|
||||
Will need to check system logs soon (noted in /tasks/reminders.txt, check at 14:00).
|
||||
First focusing on this error.
|
||||
</reasoning>
|
||||
```
|
||||
|
||||
## Reasons to Switch Procedures
|
||||
|
||||
Common triggers:
|
||||
- Data available on stdin
|
||||
- Time matching scheduled task
|
||||
- Error conditions in script output
|
||||
- Resource constraints detected
|
||||
- User input needed]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<single exit_code="0" id="20250116_135409_816" limit="3643">
|
||||
<![CDATA[
|
||||
cat /root/sia/procedures/user_communication/procedure.md
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[# User Communication
|
||||
|
||||
## Prerequisites
|
||||
- User information is stored in the /user directory
|
||||
- Tasks and their progress are documented in the /tasks directory
|
||||
|
||||
## Flow
|
||||
```mermaid
|
||||
flowchart TD
|
||||
Start([Start])
|
||||
LoadUserBasic[The /user/basic.md file should contain info to identify and address the user properly<br>Also load the last 10 messages from /user/conversation_history/ ]
|
||||
PrepareForDraft{Have everything needed for drafting a message?}
|
||||
DraftMessage[Draft message in reasoning entry]
|
||||
ReadInput[Read input from standard input]
|
||||
ReasonCleanContext[List id's of entries that are no longer needed<br>Explain for each entry why it is no longer needed]
|
||||
DeleteEntries[Remove the entries that are no longer needed<br>End by deleting the ReasonCleanContext entry]
|
||||
AddHistoryUser[Add the message to the /user/conversation_history/ directory<br>The filename is the id of the stdin entry with .user extension]
|
||||
LoadTask[Look for the task in the /tasks directory and load relevant files]
|
||||
LoadUserDetails[Look in the /user directory for relevant files]
|
||||
EstimateScript[Draft the script in a reasoning block and estimate its runtime and output length]
|
||||
ScriptAcceptable{Does the draft script make sense and are the estimations short enough to not hinder the conversation?}
|
||||
RunScript[Run the script, make sure to set appropriate timeout and output limits]
|
||||
ReviewDraft{Is the message well structured and free of logical errors?}
|
||||
SendMessage[Send the message using standard output]
|
||||
AddHistoryAgent[Add the message to the /user/conversation_history/ directory<br>The filename is the id of the stdout entry with .agent extension]
|
||||
ReasonResponse[Is the conversation ongoing?<br>How long is the user expected to take to respond?]
|
||||
NeedAwaitResponse{Is it likely to get a response within a minute?}
|
||||
BusyWait[Wait 1 second for the first busy wait, double the time each iteration until a response is received<br>Make sure to set the timout]
|
||||
|
||||
End([Clean the context])
|
||||
|
||||
Start --> LoadUserBasic
|
||||
LoadUserBasic --> PrepareForDraft
|
||||
|
||||
PrepareForDraft -->|Got all needed info| DraftMessage
|
||||
PrepareForDraft -->|Getting the required info would slow the conversation| DraftMessage
|
||||
PrepareForDraft -->|Input available on stdin| ReadInput
|
||||
PrepareForDraft -->|Context usage more than 50%| ReasonCleanContext
|
||||
PrepareForDraft -->|Task mentioned but not loaded| LoadTask
|
||||
PrepareForDraft -->|Personal or social info mentioned but not loaded| LoadUserDetails
|
||||
PrepareForDraft -->|Calculations, system info or other numerical values that can be scripted are mentioned| EstimateScript
|
||||
|
||||
ReasonCleanContext --> DeleteEntries
|
||||
DeleteEntries --> PrepareForDraft
|
||||
|
||||
ReadInput --> AddHistoryUser
|
||||
AddHistoryUser --> PrepareForDraft
|
||||
|
||||
LoadTask --> PrepareForDraft
|
||||
LoadUserDetails --> PrepareForDraft
|
||||
|
||||
EstimateScript --> ScriptAcceptable
|
||||
ScriptAcceptable -->|Acceptable| RunScript
|
||||
ScriptAcceptable -->|Not acceptable| PrepareForDraft
|
||||
RunScript --> PrepareForDraft
|
||||
|
||||
DraftMessage --> ReviewDraft{Is this really what I want to say?}
|
||||
ReviewDraft -->|Rewrite better| DraftMessage
|
||||
ReviewDraft -->|Good message| SendMessage
|
||||
|
||||
SendMessage --> AddHistoryAgent
|
||||
AddHistoryAgent --> ReasonResponse
|
||||
ReasonResponse --> NeedAwaitResponse
|
||||
|
||||
NeedAwaitResponse -->|Quick response is unlikely| End
|
||||
NeedAwaitResponse -->|Input available on stdin| PrepareForDraft
|
||||
NeedAwaitResponse -->|Quick response is likely| BusyWait
|
||||
BusyWait --> NeedAwaitResponse
|
||||
```]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
</context></context><response><reasoning>
|
||||
Let's prepare for user communication.
|
||||
I'll create a reasoning block with my current findings.
|
||||
Next I'll reason about which context elements I can clear.
|
||||
After cleaning, I'll end up with the findings and the procedures.
|
||||
This will be a good starting point for communication.
|
||||
</reasoning></response></iteration>
|
||||
@@ -1,289 +0,0 @@
|
||||
<?xml version='1.0' encoding='utf-8'?>
|
||||
<iteration system_prompt_hash="a357171f34284409058700f0d6c20cbb4f4bfe643aff5b12168c5158767f89b4" action_schema_hash="a4cf87f3d53c7b14aab3c96097d8b7bf838e8f77e413d11f51051afbe22fa3a6"><context><context
|
||||
context="14.07%"
|
||||
disk_total="1081101176832"
|
||||
disk_used="42638553088"
|
||||
memory_total="16630435840"
|
||||
memory_used="1078968320"
|
||||
stdin="0"
|
||||
time="2025-01-16T13:57:26Z">
|
||||
<reasoning id="20250116_134549_655">
|
||||
<![CDATA[
|
||||
I should start by exploring the file system to understand the environment and identify any relevant files or directories.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134555_680">
|
||||
<![CDATA[
|
||||
ls /
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[NGC-DL-CONTAINER-LICENSE
|
||||
bin
|
||||
boot
|
||||
cuda-keyring_1.0-1_all.deb
|
||||
dev
|
||||
etc
|
||||
home
|
||||
lib
|
||||
lib32
|
||||
lib64
|
||||
libx32
|
||||
media
|
||||
mnt
|
||||
opt
|
||||
proc
|
||||
root
|
||||
run
|
||||
sbin
|
||||
srv
|
||||
sys
|
||||
tmp
|
||||
usr
|
||||
var
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_134639_663">
|
||||
<![CDATA[
|
||||
|
||||
The file system contains several standard directories such as /bin, /etc, /home, /usr, and /var.
|
||||
To get a better understanding of the environment, I should explore the /root directory to see if there are any user-specific files or directories.
|
||||
I will use the `ls /root` command to list the contents of the /root directory.
|
||||
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134644_445">
|
||||
<![CDATA[
|
||||
ls /root
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[iterations
|
||||
model
|
||||
sia
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_134729_674">
|
||||
<![CDATA[
|
||||
The /root directory contains three items: iterations, model, and sia.
|
||||
I should explore the contents of these directories to understand their purpose and relevance.
|
||||
I will start by listing the contents of the /root/iterations directory using the `ls /root/iterations` command.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_134736_148">
|
||||
<![CDATA[
|
||||
ls /root/iterations
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[iteration_20250116_134549_655.xml
|
||||
iteration_20250116_134555_680.xml
|
||||
iteration_20250116_134639_663.xml
|
||||
iteration_20250116_134644_445.xml
|
||||
iteration_20250116_134729_674.xml
|
||||
iteration_20250116_134736_148.xml
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_135016_476">
|
||||
<![CDATA[
|
||||
There are not tasks in the root directory and the iterations directory only contains what I'just done.
|
||||
This is a clean start of SIA.
|
||||
I should look for procedures to follow in the `/root/sia/procedures` directory.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_135024_642">
|
||||
<![CDATA[
|
||||
ls /root/sia/procedures
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[README.md
|
||||
user_communication
|
||||
using_procedures
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_135232_795">
|
||||
<![CDATA[
|
||||
There are no specific procedures to follow.
|
||||
I will ask the user what I should do.
|
||||
I'll load the `using_procedures` and `user_communication` procedures.
|
||||
]]>
|
||||
</reasoning>
|
||||
<single exit_code="0" id="20250116_135253_387">
|
||||
<![CDATA[
|
||||
ls -la /root/sia/procedures/using_procedures
|
||||
ls -la /root/sia/procedures/user_communication
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[total 16
|
||||
drwxr-xr-x 2 root root 4096 Jan 16 13:44 .
|
||||
drwxr-xr-x 4 root root 4096 Jan 8 08:47 ..
|
||||
-rwxr-xr-x 1 root root 1758 Jan 8 21:40 procedure.md
|
||||
-rwxr-xr-x 1 root root 1831 Jan 8 21:03 reasoning.md
|
||||
total 20
|
||||
drwxr-xr-x 2 root root 4096 Jan 16 13:44 .
|
||||
drwxr-xr-x 4 root root 4096 Jan 8 08:47 ..
|
||||
-rwxr-xr-x 1 root root 244 Jan 7 12:18 description.md
|
||||
-rwxr-xr-x 1 root root 3643 Jan 8 21:49 procedure.md
|
||||
-rwxr-xr-x 1 root root 1035 Jan 7 12:23 reasoning.md
|
||||
]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<single exit_code="0" id="20250116_135343_982" limit="1758">
|
||||
<![CDATA[
|
||||
cat /root/sia/procedures/using_procedures/procedure.md
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[# Using Procedures
|
||||
|
||||
## Core Guidelines
|
||||
|
||||
When following a procedure's flowchart:
|
||||
|
||||
1. Start with reasoning:
|
||||
- State current position in flowchart explicitly
|
||||
- Focus on immediate next step, don't go ahead of the chart
|
||||
- Evaluate current context and task state
|
||||
- Often state entry id's that can be removed and explain why to avoid mistakes
|
||||
- State expected output and runtime for scripts
|
||||
|
||||
2. After script execution:
|
||||
- Analyze the actual output and compare with the expected output
|
||||
- Reevaluate situation based on results
|
||||
- Return to flowchart for next step
|
||||
- Consider if current path is still appropriate
|
||||
|
||||
3. When a procedure fails:
|
||||
- Create a task explaining the issue and the need to fix it
|
||||
- Add timestamps and id's of relevant entries
|
||||
|
||||
## Attention Management
|
||||
|
||||
LLMs pay more attention to recently mentioned information.
|
||||
Reasoning entries should mention what needs attention now.
|
||||
|
||||
To maintain focus:
|
||||
1. State current flowchart position in each reasoning
|
||||
2. Quote relevant parts of important entries
|
||||
3. Reference specific entry IDs when using their information
|
||||
4. Periodically remind about ongoing tasks or future needs
|
||||
5. Clean up entries that aren't needed for current step
|
||||
|
||||
Example of good attention management:
|
||||
```xml
|
||||
<reasoning>
|
||||
At node "evaluate_test_results". Entry 45f3d2 shows failed test: "Error: Connection timeout".
|
||||
Will need to check system logs soon (noted in /tasks/reminders.txt, check at 14:00).
|
||||
First focusing on this error.
|
||||
</reasoning>
|
||||
```
|
||||
|
||||
## Reasons to Switch Procedures
|
||||
|
||||
Common triggers:
|
||||
- Data available on stdin
|
||||
- Time matching scheduled task
|
||||
- Error conditions in script output
|
||||
- Resource constraints detected
|
||||
- User input needed]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<single exit_code="0" id="20250116_135409_816" limit="3643">
|
||||
<![CDATA[
|
||||
cat /root/sia/procedures/user_communication/procedure.md
|
||||
]]>
|
||||
<stdout>
|
||||
<![CDATA[# User Communication
|
||||
|
||||
## Prerequisites
|
||||
- User information is stored in the /user directory
|
||||
- Tasks and their progress are documented in the /tasks directory
|
||||
|
||||
## Flow
|
||||
```mermaid
|
||||
flowchart TD
|
||||
Start([Start])
|
||||
LoadUserBasic[The /user/basic.md file should contain info to identify and address the user properly<br>Also load the last 10 messages from /user/conversation_history/ ]
|
||||
PrepareForDraft{Have everything needed for drafting a message?}
|
||||
DraftMessage[Draft message in reasoning entry]
|
||||
ReadInput[Read input from standard input]
|
||||
ReasonCleanContext[List id's of entries that are no longer needed<br>Explain for each entry why it is no longer needed]
|
||||
DeleteEntries[Remove the entries that are no longer needed<br>End by deleting the ReasonCleanContext entry]
|
||||
AddHistoryUser[Add the message to the /user/conversation_history/ directory<br>The filename is the id of the stdin entry with .user extension]
|
||||
LoadTask[Look for the task in the /tasks directory and load relevant files]
|
||||
LoadUserDetails[Look in the /user directory for relevant files]
|
||||
EstimateScript[Draft the script in a reasoning block and estimate its runtime and output length]
|
||||
ScriptAcceptable{Does the draft script make sense and are the estimations short enough to not hinder the conversation?}
|
||||
RunScript[Run the script, make sure to set appropriate timeout and output limits]
|
||||
ReviewDraft{Is the message well structured and free of logical errors?}
|
||||
SendMessage[Send the message using standard output]
|
||||
AddHistoryAgent[Add the message to the /user/conversation_history/ directory<br>The filename is the id of the stdout entry with .agent extension]
|
||||
ReasonResponse[Is the conversation ongoing?<br>How long is the user expected to take to respond?]
|
||||
NeedAwaitResponse{Is it likely to get a response within a minute?}
|
||||
BusyWait[Wait 1 second for the first busy wait, double the time each iteration until a response is received<br>Make sure to set the timout]
|
||||
|
||||
End([Clean the context])
|
||||
|
||||
Start --> LoadUserBasic
|
||||
LoadUserBasic --> PrepareForDraft
|
||||
|
||||
PrepareForDraft -->|Got all needed info| DraftMessage
|
||||
PrepareForDraft -->|Getting the required info would slow the conversation| DraftMessage
|
||||
PrepareForDraft -->|Input available on stdin| ReadInput
|
||||
PrepareForDraft -->|Context usage more than 50%| ReasonCleanContext
|
||||
PrepareForDraft -->|Task mentioned but not loaded| LoadTask
|
||||
PrepareForDraft -->|Personal or social info mentioned but not loaded| LoadUserDetails
|
||||
PrepareForDraft -->|Calculations, system info or other numerical values that can be scripted are mentioned| EstimateScript
|
||||
|
||||
ReasonCleanContext --> DeleteEntries
|
||||
DeleteEntries --> PrepareForDraft
|
||||
|
||||
ReadInput --> AddHistoryUser
|
||||
AddHistoryUser --> PrepareForDraft
|
||||
|
||||
LoadTask --> PrepareForDraft
|
||||
LoadUserDetails --> PrepareForDraft
|
||||
|
||||
EstimateScript --> ScriptAcceptable
|
||||
ScriptAcceptable -->|Acceptable| RunScript
|
||||
ScriptAcceptable -->|Not acceptable| PrepareForDraft
|
||||
RunScript --> PrepareForDraft
|
||||
|
||||
DraftMessage --> ReviewDraft{Is this really what I want to say?}
|
||||
ReviewDraft -->|Rewrite better| DraftMessage
|
||||
ReviewDraft -->|Good message| SendMessage
|
||||
|
||||
SendMessage --> AddHistoryAgent
|
||||
AddHistoryAgent --> ReasonResponse
|
||||
ReasonResponse --> NeedAwaitResponse
|
||||
|
||||
NeedAwaitResponse -->|Quick response is unlikely| End
|
||||
NeedAwaitResponse -->|Input available on stdin| PrepareForDraft
|
||||
NeedAwaitResponse -->|Quick response is likely| BusyWait
|
||||
BusyWait --> NeedAwaitResponse
|
||||
```]]>
|
||||
</stdout>
|
||||
<stderr/>
|
||||
</single>
|
||||
<reasoning id="20250116_135726_364">
|
||||
<![CDATA[
|
||||
Let's prepare for user communication.
|
||||
I'll create a reasoning block with my current findings.
|
||||
Next I'll reason about which context elements I can clear.
|
||||
After cleaning, I'll end up with the findings and the procedures.
|
||||
This will be a good starting point for communication.
|
||||
]]>
|
||||
</reasoning>
|
||||
</context></context><response><reasoning>
|
||||
<![CDATA[
|
||||
I've explored the filesystem and found this is a clean start of SIA.
|
||||
I'll introduce myself to the user and report my findings.
|
||||
I can wait for user input for a long time since I don't have any other tasks.
|
||||
]]>
|
||||
</reasoning></response></iteration>
|
||||
@@ -1,6 +1,6 @@
|
||||
model:
|
||||
system_prompt_path: "system_prompt.md"
|
||||
action_schema: "action_schema.xsd"
|
||||
system_prompt_path: "/root/sia/system_prompt.md"
|
||||
action_schema: "/root/sia/action_schema.xsd"
|
||||
params:
|
||||
learning_rate: 1e-5
|
||||
epochs: 3
|
||||
|
||||
Reference in New Issue
Block a user