Skip to content

Commit f5993e4

Browse files
committed
Tool Use updates
1 parent 790f744 commit f5993e4

File tree

2 files changed

+27
-11
lines changed

2 files changed

+27
-11
lines changed

README.md

Lines changed: 14 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -232,17 +232,23 @@ There are [many more examples](test/corpus) to look at...
232232

233233
### Use as a refactoring language / _diff_ format
234234

235-
One can use `CEDARScript` to concisely and unambiguously represent code modifications at a higher level than a standard diff format can.
235+
One can use `CEDARScript` to _concisely_ and _unambiguously_ represent code modifications at a _higher_ level than a standard `diff` format can.
236236

237-
IDEs can store the local history of files in CEDARScript format, and this can also be used for searches.
237+
IDEs can store the local history of files in `CEDARScript` format, and this can also be used for searches.
238238

239239
### Tool Use
240-
If **explicit** configuration is set, the [**CEDARScript runtime**](https://github.com/CEDARScript/cedarscript-editor-python) can act as
241-
a gateway through which an LLM can:
242-
1. Call local commands (`ls`, `grep`, `find`, `open`)
243-
2. Run scripts
244-
3. Call external HTTP API services
245-
4. See the user's screen and take control of the mouse and keyboard
240+
If **explicit** configuration is set, the [**CEDARScript runtime**](https://github.com/CEDARScript/cedarscript-editor-python)
241+
can act as a **unified gateway** through which _any_ LLM can call external commands and obtain their output
242+
(a.k.a. **Tool Use** support).
243+
244+
This includes:
245+
1. **Web browsing**
246+
2. **Code Interpreter**
247+
- Run scripts written in Python, Bash, Javascript, Lua, etc
248+
3. **Function Calling**
249+
- Call local commands (`ls`, `grep`, `find`, `open`)
250+
- Call external HTTP API services
251+
4. **Computer Use**: See the user's screen and take control of the mouse and keyboard
246252
5. Possibilities are numerous...
247253

248254
The output from the external tool is captured and sent back to the LLM.

proposals/capture-external-command-output/README.md

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,23 @@
11
# External command calls to allow LLMs to experiment and learn
22

33
## Summary
4-
I propose a language extension to `CEDARScript` to allow arbitrary command execution.
4+
I propose a language extension to `CEDARScript` to allow arbitrary command execution, a.k.a. **Tool Use** support.
55
It would work as an escape hatch that connects the LLM to the external environment.
66

7+
This includes:
8+
1. **Web browsing**
9+
2. **Code Interpreter**
10+
- Run scripts written in Python, Bash, Javascript, Lua, etc
11+
3. **Function Calling**
12+
- Call local commands (`ls`, `grep`, `find`, `open`)
13+
- Call external HTTP API services
14+
4. **Computer Use**: See the user's screen and take control of the mouse and keyboard
15+
5. Possibilities are numerous...
16+
717
Security implications aside, it holds a lot of potential.
818

9-
The firs application could be a benchmark to see if the LLM would be able to perform better than the baseline
10-
when solving complex mathematical challenges, e. g. https://epoch.ai/frontiermath
19+
The first application could be a benchmark to see if the LLM would be able to perform better than the baseline
20+
when solving complex mathematical challenges, e.g. https://epoch.ai/frontiermath
1121

1222
## Examples
1323

0 commit comments

Comments
 (0)