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
Tmux is a better option visually than using screen. To turn it on, you use the experiment_use_tmux = true option within your template.
When using this option, you are no longer to access the claude code logs located at .claude-code.log. When attempting to look at the logs, the only entries into the log file are "Attaching to existing Claude Code tmux session".
We are currently working with Anthropic on an issue related to Bedrock, where we are getting API Error: 400 Input is too long for requested model but unable to provide Anthropic with the logs due to the bug above. See Screen shot for result in attempting to cat the .claude-code.log.
Relevant Log Output
coder@coder-5b6fc268-a48f-48e1-a17b-2c0c30639b34-6fb5bd54c-n7tg2:~$ cat .claude-code.log
Attaching to existing Claude Code tmux session.
Attaching to existing Claude Code tmux session.
Expected Behavior
.claude-code.log should contain claude output for debugging purposes, like it does when using screen
Steps to Reproduce
create a template with claude code. Within the claude code module, include the experiment_use_tmux = true attribute
Run the template and request Claude Code to perform an action
Is there an existing issue for this?
Current Behavior
Tmux is a better option visually than using screen. To turn it on, you use the experiment_use_tmux = true option within your template.
When using this option, you are no longer to access the claude code logs located at .claude-code.log. When attempting to look at the logs, the only entries into the log file are "Attaching to existing Claude Code tmux session".
We are currently working with Anthropic on an issue related to Bedrock, where we are getting API Error: 400 Input is too long for requested model but unable to provide Anthropic with the logs due to the bug above. See Screen shot for result in attempting to cat the .claude-code.log.
Relevant Log Output
coder@coder-5b6fc268-a48f-48e1-a17b-2c0c30639b34-6fb5bd54c-n7tg2:~$ cat .claude-code.log Attaching to existing Claude Code tmux session. Attaching to existing Claude Code tmux session.
Expected Behavior
.claude-code.log should contain claude output for debugging purposes, like it does when using screen
Steps to Reproduce
Environment
PRETTY_NAME="Ubuntu 22.04.5 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.5 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
coder@coder-5b6fc268-a48f-48e1-a17b-2c0c30639b34-6fb5bd54c-n7tg2:~$ coder version
Coder v2.21.0+9b6067c Wed Apr 2 01:26:31 UTC 2025
coder/coder@9b6067c
Slim build of Coder, does not support the server subcommand.
Additional Context
No response
The text was updated successfully, but these errors were encountered: