Parsec is a fast, terminal-based file inspector that provides immediate summaries of source code files. Built for developers who need rapid context-aware code browsing.
Parsec's split-screen interface showing file navigation and executable help display
- Split-screen interface with file tree and detailed summary view
- Directory navigation with live content preview
- Real-time fuzzy search capabilities
- Multi-language support: Go, Python, JavaScript, TypeScript, Rust, Java, C/C++
- Enhanced file parsing:
- Markdown rendering with syntax highlighting
- Configuration file parsing (JSON, YAML, INI, ENV)
- Text file preview with line counts
- Executable help text extraction
- Intelligent parsing of functions, imports, types, and structs
- Responsive design with terminal resize handling
- Keyboard-driven interface with vim-style bindings
- Asynchronous operations for smooth performance
git clone https://github.com/Cod-e-Codes/parsec.git
cd parsec
go build .
# Scan current directory
./parsec
# Scan specific directory
./parsec /path/to/project
# Windows paths
./parsec "C:\Users\username\Projects"
# Unix paths
./parsec /home/user/code
# Show help
./parsec -h
Key | Action |
---|---|
↑/↓ or k/j |
Navigate file list |
Enter |
Enter directory or open file |
/ |
Start fuzzy search |
PgUp/PgDn |
Scroll summary content |
Home/End |
Jump to first/last file |
t |
Toggle directory visibility |
r |
Refresh current directory |
q or Ctrl+C |
Quit |
Category | Extensions | Features |
---|---|---|
Programming | .go .py .js .ts .rs .java .c .cpp |
Functions, types, imports |
Documentation | .md .markdown .rst |
Headers, links, rendered content |
Configuration | .json .yaml .ini .env |
Keys, structure |
Data | .xml .csv .log |
Content preview |
Executables | .exe .bin |
Help text extraction |
parsec/
├── main.go # Application entrypoint
├── ui/ # Interface components
├── core/ # Analysis engine
├── utils/ # Utilities
└── docs/ # Documentation
Parsec welcomes contributions from the community. Please review our contribution guidelines before getting started:
- Fork the repository
- Create a feature branch
- Make your changes
- Test thoroughly
- Submit a pull request
When reporting bugs, please include:
- Operating system details
- Steps to reproduce
- Expected vs actual behavior
- Error messages if applicable
For security concerns, please review our Security Policy before submitting a report.
Dependencies are managed through Go modules and automatically updated via Dependabot. Major version updates are handled manually to ensure stability.
MIT License - see LICENSE file for details.
Parsec follows semantic versioning. The first stable release will be tagged as v1.0.0 once all core features are thoroughly tested.