Skip to main content

Overview

Cubent Coder can directly interact with files in your workspace, making it a powerful tool for code generation, refactoring, and project management. The AI can read existing files to understand context, create new files, and modify existing ones with precision.

Reading Files

Automatic Context Awareness

Cubent Coder automatically understands your project structure:
  • Project scanning: Analyzes your workspace on startup
  • File relationships: Understands imports, dependencies, and references
  • Code patterns: Learns from your existing codebase style
  • Configuration files: Reads package.json, tsconfig.json, etc.

Explicit File References

You can explicitly reference files in your conversations:

File Content Analysis

Ask Cubent to analyze specific files:

Creating Files

New File Generation

Cubent can create complete files from scratch:

Template-Based Creation

Generate files based on existing patterns:

Multiple File Creation

Create several related files at once:

Modifying Files

Targeted Updates

Make specific changes to existing files:

Refactoring Operations

Perform complex refactoring across multiple files:

Code Style Updates

Apply consistent formatting and style:

File Management

Directory Operations

Organize your project structure:

File Organization

Reorganize existing files:

Cleanup Operations

Remove unused code and files:

Advanced File Operations

Batch Processing

Process multiple files with similar operations:

Cross-File Analysis

Analyze relationships between files:

Migration Tasks

Handle large-scale code migrations:

File Safety and Best Practices

Backup and Version Control

Always use version control when working with file operations:
  1. Commit before major changes: Create a checkpoint
  2. Review changes: Use git diff to see what changed
  3. Test after modifications: Ensure everything still works
  4. Incremental changes: Make small, focused updates

Approval Settings

Configure what file operations require approval:
  • Auto-approve: Reading files, analyzing code
  • Require approval: Creating new files, major refactoring
  • Always confirm: Deleting files, destructive operations

File Patterns and Exclusions

Configure which files Cubent Coder can access:

Integration with Development Tools

IDE Integration

Cubent Coder works seamlessly with VS Code:
  • Syntax highlighting: Maintains proper formatting
  • IntelliSense: Preserves type information
  • Extensions: Compatible with linters and formatters
  • Git integration: Tracks all file changes

Build Tools

Integrates with your build pipeline:
  • TypeScript: Respects tsconfig.json settings
  • ESLint: Follows your linting rules
  • Prettier: Maintains code formatting
  • Webpack/Vite: Understands build configuration

Testing Frameworks

Works with testing tools:
  • Jest: Generates tests following your patterns
  • Cypress: Creates E2E tests for new features
  • Storybook: Generates component stories
  • Testing Library: Follows testing best practices

Troubleshooting

Common Issues

File not found errors:
  • Check file paths are relative to workspace root
  • Ensure files exist and are not excluded
  • Verify file permissions
Permission denied:
  • Check file system permissions
  • Ensure VS Code has necessary access
  • Review workspace trust settings
Unexpected file changes:
  • Review approval settings
  • Check auto-save configuration
  • Use version control to track changes

Performance Considerations

Large file handling:
  • Cubent Coder can handle large files efficiently
  • Consider breaking very large files into smaller modules
  • Use file exclusion patterns for build artifacts
Workspace scanning:
  • Initial scan may take time for large projects
  • Exclude unnecessary directories to improve performance
  • Use .gitignore patterns to guide file selection

Next Steps

Terminal Integration

Execute commands and manage your development environment

MCP Integration

Extend capabilities with Model Context Protocol