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: docs/ROADMAP.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@
9
9
-[ ] Figure out how to get OI to answer to user input requests like python's `input()`. Do we somehow detect a delay in the output..? Is there some universal flag that TUIs emit when they expect user input? Should we do this semantically with embeddings, then ask OI to review it and respond..?
10
10
-[ ] Placeholder text that gives a compelling example OI request. Probably use `textual`
11
11
-[ ] Everything else `textual` offers, like could we make it easier to select text? Copy paste in and out? Code editing interface?
12
-
-[] Let people turn off the active line highlighting
12
+
-[x] Let people turn off the active line highlighting
13
13
-[ ] Add a --plain flag which doesn't use rich, just prints stuff in plain text
14
14
-[ ] Use iPython stuff to track the active line, instead of inserting print statements, which makes debugging weird (From ChatGPT: For deeper insights into what's happening behind the scenes, including which line of code is being executed, you can increase the logging level of the IPython kernel. You can configure the kernel's logger to a more verbose setting, which logs each execution request. However, this requires modifying the kernel's startup settings, which might involve changing logging configurations in the IPython kernel source or when launching the kernel.)
15
15
-[ ] Let people edit the code OI writes. Could just open it in the user's preferred editor. Simple. [Full description of how to implement this here.](https://github.com/KillianLucas/open-interpreter/pull/830#issuecomment-1854989795)
Copy file name to clipboardExpand all lines: docs/guides/advanced-terminal-usage.mdx
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,4 +13,5 @@ Magic commands can be used to control the interpreter's behavior in interactive
13
13
-`%tokens [prompt]`: EXPERIMENTAL: Calculate the tokens used by the next request based on the current conversation's messages and estimate the cost of that request; optionally provide a prompt to also calculate the tokens used by that prompt and the total amount of tokens that will be sent with the next request.
14
14
-`%info`: Show system and interpreter information.
15
15
-`%help`: Show this help message.
16
-
-`%jupyter`: Export the current session to a Jupyter notebook file (.ipynb) to the Downloads folder.
16
+
-`%jupyter`: Export the current session to a Jupyter notebook file (.ipynb) to the Downloads folder.
17
+
-`%markdown [path]`: Export the conversation to a specified Markdown path. If no path is provided, it will be saved to the Downloads folder with a generated conversation name.
Copy file name to clipboardExpand all lines: docs/usage/terminal/magic-commands.mdx
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,3 +13,4 @@ Magic commands can be used to control the interpreter's behavior in interactive
13
13
-`%tokens [prompt]`: EXPERIMENTAL: Calculate the tokens used by the next request based on the current conversation's messages and estimate the cost of that request; optionally provide a prompt to also calculate the tokens used by that prompt and the total amount of tokens that will be sent with the next request.
14
14
-`%info`: Show system and interpreter information.
15
15
-`%help`: Show this help message.
16
+
-`%markdown [path]`: Export the conversation to a specified Markdown path. If no path is provided, it will be saved to the Downloads folder with a generated conversation name.
"%info": "Show system and interpreter information",
60
61
"%jupyter": "Export the conversation to a Jupyter notebook file",
62
+
"%markdown [path]": "Export the conversation to a specified Markdown path. If no path is provided, it will be saved to the Downloads folder with a generated conversation name.",
0 commit comments