solidtime is an open-source time tracking application designed for freelancers and agencies. It provides a full-stack solution with a PHP backend (using a custom Laravel-like framework with strict typing) and a Vue 3 frontend served via Inertia.js. The system supports multi-tenant organizations with role-based permissions (Owner, Admin, Employee, Placeholder), project and task management, client and tag tracking, billable rates, goals, and detailed reporting with export to CSV, PDF, ODS, and XLSX. It also includes importers for Toggl, Clockify, Harvest, and generic CSV formats, as well as a native solidtime format. The architecture is a monolith with a RESTful API (versioned under /api/v1) and web controllers driven by Inertia.js. The backend uses a custom PHP framework that resembles Laravel but employs non-standard syntax (declare strict_types, use traits, fn closures). Key entry points include API controllers for time entries, projects, clients, tags, goals, reports, and import/export; console commands for administrative tasks, telemetry, and database consistency checks; and a Filament admin panel for CRUD operations. The frontend is built with Vue 3, Pinia stores, TanStack Query for caching, and a shared UI component library (packages/ui) that provides reusable primitives like dialogs, selects, calendars, and context menus. Data flows center around time entries, which are created via a timer or manual entry, associated with projects, tasks, clients, and tags, and aggregated for reporting and goal tracking. The system uses PostgreSQL as its primary database, with Redis for caching and queueing. External dependencies include a mail driver (Mailpit in dev), storage drivers (local/S3), and optional services like Gotenberg for PDF rendering and Paddle for subscriptions. The codebase is extensively tested with PHPUnit (unit/feature), Vitest (JS unit), and Playwright (E2E), and includes CI/CD pipelines for building, linting, and testing.
OpenCrew is a multi-agent operating system designed to extend OpenClaw into a manageable AI team. It enables users to create specialized agents (Chief of Staff, CTO, Builder, CIO, Knowledge Officer, Operations, Research) that collaborate through messaging platforms like Slack, Discord, and Feishu. The system implements structured collaboration through role-based channels, thread-based task isolation, and agent-to-agent communication protocols. Key features include autonomy levels (L0-L3), task classification (QAPS), two-mode agent collaboration (delegation and discussion), and three-layer knowledge distillation. The application is actively maintained with recent updates focusing on cross-agent collaboration capabilities.
This repository is a curated collection of management and engineering leadership resources, not a software application or data pipeline. It contains a personal README detailing the author's management philosophy, recommended readings on topics like AI, burnout, inclusivity, and technical leadership, a blog post on managing teams during COVID-19, documentation outlining expectations and meeting practices, and reusable templates for goal setting, artifacts, and one-on-one meetings. The content serves as a practical guide for managers to improve team dynamics, feedback processes, and leadership effectiveness. While it lacks executable code or data processing components, the resources are well-organized and actionable, offering value as a reference for engineering leadership practices.
AgentHub (also known as Maestro) is an Electron desktop application that orchestrates a virtual software development team of 46 AI agents powered by Claude Code CLI. The system enforces a 'Harness Engineering' methodology: Skills (standardized slash commands), Hooks (pre/post tool interceptors), Gates (quality checkpoints G0–G6), and FileWatchers (auto-sync markdown files to database). The GUI is intentionally limited to monitoring and three core operations—most workflow is driven by slash commands within Claude Code sessions. Architecture follows a three-layer pattern: Vue 3 + TypeScript renderer communicates via Electron IPC (contextBridge) to a main process with ~16 singleton services (session-manager, task-manager, gate-keeper, hook-manager, etc.). Persistence uses sql.js (SQLite in-memory) with a debounced disk save and 13 migrations. The source of truth is markdown files in `.knowledge/` and `.tasks/` directories, which are watched by chokidar and synced to the database. The app supports bilingual UI (zh-TW/en) and runs on Windows, macOS, and Linux. Key features include: sprint-based project management with task dependency tracking, interactive terminal sessions (xterm.js + node-pty), cost tracking per session, Git integration, a gate pipeline with review workflows, and a skill/hook management system with hash-based idempotent deployment. The codebase is well-structured with reusable components and services, though it shows some technical drift (alpha dependencies, brand name mismatch, Windows-specific paths) and high complexity from the extensive agent definitions and knowledge base.
This repository is a comprehensive curated knowledge base and reference directory focused on time tracking, productivity methodologies, and related tools. The dominant character is a flat collection of over 3000 markdown files under `details/`, each describing a specific software tool, productivity technique, author, or research finding in a structured format (overview, features, pricing, use cases). While primarily a reference resource, the repo also contains a few functional software components, including a Spring Boot + Vaadin reporting app for Toggl (toggl-reporter), a Django monorepo with REST API and Keycloak auth for time tracking (timed), a Home Assistant custom component (ha-toggl-track), and a Lua SDK (Qmonix). These are small reference implementations that demonstrate integration patterns. The repository serves as a one-stop guide for individuals and teams evaluating time tracking solutions, learning productivity methods, or building integrations. It cites numerous statistics and studies, but many entries are stale or incomplete (e.g., research stub pages with placeholder text). The code components are basic and not production-ready without further development.