wesolves

Mixedlane — AI skill for Claude Code

AI community

Mixedlane — a friendly Jira-style tracker where people and AI agents plan and ship work together.

How to install Mixedlane

This entry records only its repository, not the path inside it, so there is no exact command to give. Open wesolves/mixedlane and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Mixedlane does

Mixedlane — a friendly Jira-style tracker where people and AI agents plan and ship work together. Epics, stories, tasks and Kanban boards, Confluence-style docs, realtime collaboration, GitHub automation, and an MCP server so Claude Code, Codex and other agents can work alongside your team.

Alternatives in AI

Repomix — 📦 Repomix is a powerful tool that packs your entire repository into a single, AI-friendly file 22.7k ★
Qwen Audio Agent — A realtime voice runtime that keeps Agents talking, working, and present 2.3k ★
Agent Teams AI — You're the boss, agents are your team 2k ★

README

Mixedlane

A simpler, friendlier Jira-style tracker.

**Project → Epic → Milestone → User Story → Task → Subtask**, with a Kanban board, a tree list, rich-text descriptions and comments, and an activity history.

It also has:

Confluence-style docs.
Realtime collaboration (live updates, presence, an inbox).
GitHub automation.
AI agents that connect over MCP with their own API keys and permissions.

Stack

Part	Tech
Web (`apps/web`)	React 19, Vite, Tailwind v4, shadcn/ui (Radix), lucide-react, react-icons, TanStack Query, React Router, dnd-kit, Tiptap
Server (`apps/server`)	NestJS (Express), Drizzle ORM, Postgres — embedded PGlite in dev, real Postgres in prod; DB-backed job queue
Shared (`packages/shared`)	Zod schemas, types and hierarchy rules used by both sides

This is one npm package with a single `node_modules`. The project drive is FAT32, which can't create the symlinks npm workspaces need. `@mixedlane/shared` is resolved through path aliases (`tsconfig` `paths`, Vite `resolve.alias`, and SWC for the server).

How the server runs TypeScript:

In development: directly through SWC (@swc-node/register), which emits the decorator metadata NestJS needs.
For production: npm run build compiles it the same way into plain JavaScript in build/.

Run it

npm install
npm run dev          # API on :3001, web on http://localhost:5173 (demo data is seeded into an empty database)
npm run seed:reset   # wipe and reseed the demo org (dev server must be running)

**On your network (LAN):** `npm run dev:lan` exposes the web app on every interface; the API always listens on all interfaces (`HOST`, default `0.0.0.0`) and prints its LAN addresses at startup.

Other devices open http://:5173 (use WEB_PORT=5180 npm run dev:lan if 5173 is taken — the dev server fails rather than silently switching ports).
MCP clients on other machines use http://:3001/api/mcp (or the web por