Skip to content

Conversation

@35C4n0r
Copy link
Collaborator

@35C4n0r 35C4n0r commented Dec 9, 2025

Description

  • Use $HOME variable instead of hardcoded path in symlink creation

Type of Change

  • New module
  • New template
  • Bug fix
  • Feature/enhancement
  • Documentation
  • Other

Module Information

Path: registry/[namespace]/modules/[module-name]
New version: v1.0.0
Breaking change: [ ] Yes [x] No

Template Information

Path: registry/[namespace]/templates/[template-name]

Testing & Validation

  • Tests pass (bun test)
  • Code formatted (bun fmt)
  • Changes tested locally

Related Issues

@35C4n0r 35C4n0r force-pushed the fix-figma-issues-1 branch from a758b67 to 8766ec2 Compare December 9, 2025 18:19
@DevelopmentCats
Copy link
Contributor

I think just exporting the bin to path in the install script achieves what we want without needing the symlink at all

@DevelopmentCats
Copy link
Contributor

@35C4n0r let me know what you think on this tomorrow

@35C4n0r
Copy link
Collaborator Author

35C4n0r commented Dec 10, 2025

@DevelopmentCats instead of using export in start.sh let's use:

resource "coder_env" "claude_binary_path" {
  agent_id = var.agent_id
  name     = "PATH"
  value    = "$HOME/.local/bin:$PATH"
}

This would ensure the path is updated globally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants