codex-linux 1.0.0

package/README.md

@@ -0,0 +1,245 @@
+# Codex Linux
+
+A Linux port of OpenAI Codex - A powerful command center for managing multiple AI coding agents in parallel.
+
+## Features
+
+- **Multi-Agent Orchestration**: Manage multiple AI agents working in parallel on different tasks
+- **Git Worktrees**: Isolate agent changes in separate worktrees for safe experimentation
+- **Skills System**: Create and apply reusable skills to customize agent behavior
+- **Automation**: Schedule recurring tasks and create automated workflows
+- **Multi-Provider Support**: Works with OpenAI (GPT-4, GPT-5, Codex) and Anthropic (Claude) models
+- **Change Review**: Review, approve, or reject agent code changes before applying
+- **Linux Native**: Built specifically for Linux with AppImage, deb, and rpm packages
+
+## Installation
+
+### Quick Install (Recommended)
+
+Choose one of these two universal methods:
+
+#### Option 1: Curl (Universal - All Linux Distributions)
+
+```bash
+curl -fsSL https://codex-linux.dev/install.sh | bash
+```
+
+This installs the AppImage to `~/.local/bin/` and creates a desktop entry.
+
+**With sudo (system-wide install):**
+```bash
+curl -fsSL https://codex-linux.dev/install.sh | bash -s -- --system
+```
+
+**Uninstall:**
+```bash
+curl -fsSL https://codex-linux.dev/install.sh | bash -s -- --uninstall
+```
+
+#### Option 2: NPM (For Node.js developers)
+
+```bash
+# Install globally
+npm install -g codex-linux
+
+# Or run without installing
+npx codex-linux
+```
+
+**Update:**
+```bash
+npm update -g codex-linux
+```
+
+### Prerequisites
+
+- Node.js 18+ (for NPM install)
+- Git (for source install)
+- Linux (Ubuntu 20.04+, Fedora 35+, Arch Linux, etc.)
+
+### From Source
+
+```bash
+# Clone the repository
+git clone https://github.com/yourusername/codex-linux.git
+cd codex-linux
+
+# Install dependencies
+npm install
+
+# Build the application
+npm run build
+
+# Run in development mode
+npm run dev
+
+# Package for Linux
+npm run package:linux
+```
+
+### Pre-built Packages
+
+Download the latest release from [GitHub Releases](https://github.com/ranker-org/codex-linux-app/releases):
+
+- **AppImage** (Universal): `Codex-Linux-x.x.x.AppImage` - Works on all distributions
+- **Debian/Ubuntu**: `codex-linux_x.x.x_amd64.deb`
+- **Fedora/RHEL**: `codex-linux-x.x.x.x86_64.rpm`
+
+## Quick Start
+
+1. **Launch Codex Linux** - Run the application from your applications menu or terminal
+
+2. **Configure AI Provider**:
+   - Go to Settings → AI Providers
+   - Add your OpenAI or Anthropic API key
+   - Test the connection
+
+3. **Create Your First Agent**:
+   - Click "+ New Agent"
+   - Select a project folder
+   - Choose a provider and model
+   - Optionally apply skills
+
+4. **Start Coding**:
+   - Send messages to your agent
+   - Assign tasks for parallel execution
+   - Review changes in worktrees
+
+## Configuration
+
+### Environment Variables
+
+```bash
+# Optional: Set default API keys
+export OPENAI_API_KEY="your-key-here"
+export ANTHROPIC_API_KEY="your-key-here"
+```
+
+### Settings File
+
+Settings are stored in `~/.config/codex/config.json`:
+
+```json
+{
+  "theme": "dark",
+  "defaultProvider": "openai",
+  "defaultModel": "gpt-4o",
+  "maxParallelAgents": 5,
+  "shortcuts": {
+    "agent:new": "Ctrl+Shift+N",
+    "agent:send": "Ctrl+Enter"
+  }
+}
+```
+
+## Skills
+
+Skills are reusable instructions that customize agent behavior:
+
+1. Create skills in the Skills panel
+2. Write instructions in markdown
+3. Apply skills to agents when creating or editing
+
+### Example Skill Structure
+
+```
+~/.config/codex/skills/my-skill/
+├── skill.yaml          # Skill metadata
+├── instructions.md     # Core instructions
+└── templates/
+    └── code-review.md  # Review template
+```
+
+## Automations
+
+Create automated workflows:
+
+- **Schedule**: Run on cron schedule (e.g., daily code review)
+- **Event**: Trigger on git events or file changes
+- **Webhook**: Trigger via HTTP requests
+- **Manual**: Run on demand
+
+## Worktrees
+
+Git worktrees provide isolated environments for each agent:
+
+- Changes are isolated from main branch
+- Easy to review and merge
+- Automatic cleanup on agent deletion
+- Visual diff and merge tools
+
+## Keyboard Shortcuts
+
+| Action | Shortcut |
+|--------|----------|
+| New Agent | `Ctrl+Shift+N` |
+| Send Message | `Ctrl+Enter` |
+| New Worktree | `Ctrl+Shift+W` |
+| Open Skills | `Ctrl+Shift+S` |
+| Open Automations | `Ctrl+Shift+A` |
+| Open Settings | `Ctrl+,` |
+| Command Palette | `Ctrl+Shift+P` |
+
+## Architecture
+
+```
+codex-linux/
+├── src/
+│   ├── main/              # Electron main process
+│   │   ├── agents/        # Agent orchestration
+│   │   ├── git/           # Git worktree management
+│   │   ├── skills/        # Skills system
+│   │   ├── automations/   # Automation scheduler
+│   │   └── providers/     # AI provider integrations
+│   ├── renderer/          # React frontend
+│   │   └── components/    # UI components
+│   └── shared/            # Shared types
+├── assets/                # Icons and images
+└── tests/                 # Test suites
+```
+
+## Development
+
+### Running Tests
+
+```bash
+npm test
+```
+
+### Linting
+
+```bash
+npm run lint
+npm run lint:fix
+```
+
+### Type Checking
+
+```bash
+npm run typecheck
+```
+
+## Contributing
+
+1. Fork the repository
+2. Create a feature branch (`git checkout -b feature/amazing-feature`)
+3. Commit your changes (`git commit -m 'Add amazing feature'`)
+4. Push to the branch (`git push origin feature/amazing-feature`)
+5. Open a Pull Request
+
+## License
+
+MIT License - see [LICENSE](LICENSE) file for details.
+
+## Acknowledgments
+
+- Inspired by OpenAI Codex
+- Built with Electron, React, and TypeScript
+- Uses Simple Git for git operations
+- Icons by Lucide
+
+## Support
+
+- GitHub Issues: [Report bugs or request features](https://github.com/yourusername/codex-linux/issues)
+- Documentation: [Full documentation](https://codex-linux.readthedocs.io)
+- Discord: [Join our community](https://discord.gg/codex-linux)

package/assets/skills/code-review/instructions.md

@@ -0,0 +1,102 @@
+# Code Review Guidelines
+
+When reviewing code, please follow these comprehensive guidelines:
+
+## 1. Code Quality
+
+### Readability
+- Is the code easy to understand?
+- Are variable and function names descriptive?
+- Is the code properly formatted and indented?
+- Are complex sections commented?
+
+### Maintainability
+- Is the code modular and reusable?
+- Are functions small and focused?
+- Is there appropriate separation of concerns?
+- Are there any code smells or anti-patterns?
+
+## 2. Functionality
+
+### Correctness
+- Does the code work as intended?
+- Are edge cases handled properly?
+- Are errors handled gracefully?
+- Is input validated?
+
+### Testing
+- Are there adequate unit tests?
+- Are integration tests included where needed?
+- Is test coverage sufficient?
+- Are edge cases tested?
+
+## 3. Performance
+
+### Efficiency
+- Are there any obvious performance bottlenecks?
+- Are expensive operations optimized?
+- Is memory usage reasonable?
+- Are loops and iterations efficient?
+
+### Scalability
+- Will the code scale with increased load?
+- Are there any hard limits that could cause issues?
+- Is caching used appropriately?
+
+## 4. Security
+
+### Best Practices
+- Is user input sanitized?
+- Are secrets and credentials properly handled?
+- Are there SQL injection vulnerabilities?
+- Is XSS prevention in place?
+
+### Authentication & Authorization
+- Are access controls properly implemented?
+- Is authentication handled securely?
+- Are sensitive operations properly protected?
+
+## 5. Documentation
+
+### Code Documentation
+- Are public APIs documented?
+- Are complex algorithms explained?
+- Are there README files where needed?
+- Is the documentation up to date?
+
+### Comments
+- Are comments clear and helpful?
+- Do comments explain "why" not just "what"?
+- Is there dead code or commented-out code?
+
+## Review Checklist
+
+Before approving, ensure:
+
+- [ ] Code compiles/builds without errors
+- [ ] Tests pass
+- [ ] No console.log or debug statements left in production code
+- [ ] No sensitive data exposed
+- [ ] Documentation updated if needed
+- [ ] Breaking changes documented
+- [ ] Backward compatibility considered
+
+## Communication
+
+When providing feedback:
+
+1. **Be Constructive**: Focus on the code, not the person
+2. **Explain Why**: Provide reasoning for suggestions
+3. **Suggest Solutions**: Don't just point out problems
+4. **Acknowledge Good Work**: Highlight what was done well
+5. **Be Specific**: Reference specific lines and provide examples
+
+## Priority Levels
+
+- **Critical**: Security vulnerabilities, data loss risks
+- **High**: Major functionality issues, performance problems
+- **Medium**: Code quality issues, missing tests
+- **Low**: Style preferences, minor optimizations
+- **Suggestion**: Alternative approaches, future improvements
+
+Remember: The goal is to improve code quality while maintaining a positive, collaborative environment.

package/assets/skills/code-review/skill.yaml

@@ -0,0 +1,15 @@
+id: code-review-skill
+name: Code Review
+version: "1.0.0"
+author: Codex Linux Team
+description: Comprehensive code review guidelines for maintaining code quality
+entryPoint: instructions.md
+tags:
+  - review
+  - quality
+  - best-practices
+parameters: []
+dependencies: []
+permissions:
+  - read-code
+  - write-comments

package/assets/skills/refactoring/instructions.md

@@ -0,0 +1,149 @@
+# Refactoring Assistant
+
+You are an expert code refactoring assistant. Your goal is to improve code quality while maintaining functionality.
+
+## Core Principles
+
+### 1. Preserve Behavior
+- Never change the external behavior of the code
+- Ensure all tests pass after refactoring
+- Maintain backward compatibility
+
+### 2. Improve Readability
+- Use descriptive names for variables, functions, and classes
+- Break down complex functions into smaller, focused ones
+- Remove dead code and comments
+- Follow consistent formatting
+
+### 3. Reduce Complexity
+- Extract methods to reduce function length
+- Simplify conditional expressions
+- Remove nested conditionals when possible
+- Apply the Single Responsibility Principle
+
+## Refactoring Patterns
+
+### Extract Method
+When you see duplicated code or a long function:
+```javascript
+// Before
+function calculateTotal(items) {
+  let total = 0;
+  for (const item of items) {
+    total += item.price * item.quantity;
+  }
+  return total;
+}
+
+// After
+function calculateItemTotal(item) {
+  return item.price * item.quantity;
+}
+
+function calculateTotal(items) {
+  return items.reduce((sum, item) => sum + calculateItemTotal(item), 0);
+}
+```
+
+### Rename for Clarity
+Use descriptive names that reveal intent:
+```javascript
+// Before
+const d = new Date();
+
+// After
+const currentDate = new Date();
+```
+
+### Remove Magic Numbers
+```javascript
+// Before
+if (status === 404) { ... }
+
+// After
+const HTTP_NOT_FOUND = 404;
+if (status === HTTP_NOT_FOUND) { ... }
+```
+
+## Code Smells to Watch For
+
+1. **Long Method** - Functions longer than 20-30 lines
+2. **Large Class** - Classes with too many responsibilities
+3. **Primitive Obsession** - Using primitives instead of objects
+4. **Long Parameter List** - Functions with 4+ parameters
+5. **Duplicated Code** - Copy-pasted code blocks
+6. **Feature Envy** - Method that uses more features of another class
+7. **Data Clumps** - Groups of data that belong together
+
+## Refactoring Checklist
+
+Before submitting changes:
+- [ ] All existing tests pass
+- [ ] New tests added for changed behavior
+- [ ] Code compiles without warnings
+- [ ] No regression in performance
+- [ ] Documentation updated if needed
+- [ ] No magic numbers or strings
+- [ ] Functions are under 30 lines
+- [ ] Meaningful variable names
+- [ ] Comments explain "why", not "what"
+
+## Common Refactorings
+
+### Simplify Conditionals
+```javascript
+// Before
+if (user !== null && user !== undefined && user.isActive) { ... }
+
+// After
+if (user?.isActive) { ... }
+```
+
+### Replace Loop with Pipeline
+```javascript
+// Before
+const activeUsers = [];
+for (const user of users) {
+  if (user.isActive) {
+    activeUsers.push(user);
+  }
+}
+
+// After
+const activeUsers = users.filter(u => u.isActive);
+```
+
+### Introduce Parameter Object
+```javascript
+// Before
+function createUser(name, email, phone, address, city, zip) { ... }
+
+// After
+function createUser(contactInfo) { ... }
+// where contactInfo = { name, email, phone, address, city, zip }
+```
+
+## Language-Specific Tips
+
+### JavaScript/TypeScript
+- Use destructuring for cleaner code
+- Prefer const/let over var
+- Use arrow functions for callbacks
+- Leverage modern array methods
+- Use optional chaining and nullish coalescing
+
+### Python
+- Follow PEP 8 style guide
+- Use list/dict comprehensions
+- Leverage context managers
+- Use type hints
+- Prefer f-strings for formatting
+
+### Go
+- Keep functions small and focused
+- Handle errors explicitly
+- Use meaningful variable names
+- Leverage interfaces for abstraction
+- Follow gofmt formatting
+
+Remember: Refactoring should make the code easier to understand and maintain, not just different.

package/assets/skills/refactoring/skill.yaml

@@ -0,0 +1,15 @@
+id: refactoring-skill
+name: Refactoring Assistant
+version: "1.0.0"
+author: Codex Linux Team
+description: Expert guidance for code refactoring and improving code quality
+entryPoint: instructions.md
+tags:
+  - refactoring
+  - optimization
+  - clean-code
+parameters: []
+dependencies: []
+permissions:
+  - read-code
+  - write-code

package/assets/skills/testing/skill.yaml

@@ -0,0 +1,15 @@
+id: testing-skill
+name: Testing Expert
+version: "1.0.0"
+author: Codex Linux Team
+description: Comprehensive testing strategies and best practices
+entryPoint: instructions.md
+tags:
+  - testing
+  - tdd
+  - quality-assurance
+parameters: []
+dependencies: []
+permissions:
+  - read-code
+  - write-tests

package/commitlint.config.js

@@ -0,0 +1,23 @@
+module.exports = {
+  extends: ['@commitlint/config-conventional'],
+  rules: {
+    'type-enum': [
+      2,
+      'always',
+      [
+        'feat',     // New feature
+        'fix',      // Bug fix
+        'docs',     // Documentation
+        'style',    // Formatting
+        'refactor', // Code refactoring
+        'perf',     // Performance
+        'test',     // Tests
+        'chore',    // Build/dependencies
+        'ci',       // CI/CD
+        'revert',   // Revert
+      ],
+    ],
+    'subject-case': [0],
+    'body-max-line-length': [2, 'always', 100],
+  },
+};