Skip to content

Commit 7028c78

Browse files
committed
readme: support codex
1 parent dc6daa9 commit 7028c78

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

README.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# AgentAPI
22

3-
Control Claude Code, Goose, and Aider with an HTTP API.
3+
Control [Claude Code](https://github.com/anthropics/claude-code), [Goose](https://github.com/block/goose), [Aider](https://github.com/Aider-AI/aider), and [Codex](https://github.com/openai/codex) with an HTTP API.
44

55
![chat demo](https://github.com/user-attachments/assets/11685cf3-324b-4e72-b8e9-5bb8ceede785)
66

@@ -44,7 +44,6 @@ curl localhost:3284/messages
4444

4545
We host a demo web chat interface at https://coder.github.io/agentapi/chat which will connect to your local AgentAPI server and let you test it out.
4646

47-
4847
## CLI Commands
4948

5049
### `agentapi server`
@@ -115,7 +114,7 @@ AgentAPI automatically removes these.
115114
- For user input, we strip the lines that contain the text from the user's last message.
116115
- For the input box, we look for lines at the end of the message that contain common TUI elements, like `>` or `------`.
117116

118-
### What will happen when Claude Code, Aider, or Goose update their TUI?
117+
### What will happen when Claude Code, Goose, Aider, or Codex update their TUI?
119118

120119
Splitting the terminal output into a sequence of messages should still work, since it doesn't depend on the TUI structure. The logic for removing extra bits may need to be updated to account for new elements. AgentAPI will still be usable, but some extra TUI elements may become visible in the agent messages.
121120

0 commit comments

Comments
 (0)