Feature Description
When we call ClaudeCode, it creates a terminal
local terminal_ok, terminal = pcall(require, "claudecode.terminal")
but the only way to access it is via user commands.
Feature would be to expose it.
Use Case
Anyone who wants to make any code interacting with claude API.
Example:
ilan-schemoul/nvim-config@e95797a#diff-7a87cf1458c4f35acd87b922d094f8f80580bdbf2fee6b36dc332db086e1b289R30
User commands are not to be made for programatic interactions as the name suggests.
If I require("claudecode/terminal") it spans up another terminal if I do toggle or whatever.
Proposed Solution
require("claude").get_terminal() (or get_terminal_interface()) would return the created terminal
Alternatives Considered
workaround is calling user commands. It sucks, you are limited compared to API, you have no LSP helping you, it's weird and you have to escape characters sometimes (or i think you can provide with { args = txt } the text and no need to escape. but anyway it's confusing).
Feature Description
When we call ClaudeCode, it creates a terminal
local terminal_ok, terminal = pcall(require, "claudecode.terminal")but the only way to access it is via user commands.
Feature would be to expose it.
Use Case
Anyone who wants to make any code interacting with claude API.
Example:
ilan-schemoul/nvim-config@e95797a#diff-7a87cf1458c4f35acd87b922d094f8f80580bdbf2fee6b36dc332db086e1b289R30
User commands are not to be made for programatic interactions as the name suggests.
If I require("claudecode/terminal") it spans up another terminal if I do toggle or whatever.
Proposed Solution
require("claude").get_terminal() (or get_terminal_interface()) would return the created terminal
Alternatives Considered
workaround is calling user commands. It sucks, you are limited compared to API, you have no LSP helping you, it's weird and you have to escape characters sometimes (or i think you can provide with { args = txt } the text and no need to escape. but anyway it's confusing).