Claude Code
Work on tasks with unified Floor context from Claude Code on your computer.
Lit Factory MCP
Connect tasks, conversations, and knowledge across your work apps. People and agents share the context and keep the work moving.
The operating problem
A ticket in Linear, a review in GitHub, and a decision in Slack describe the same work. Bring them together so your team and agents can act with the full story.
Connected evidence used across delivery decisions
GitHub, Linear, and native work can appear on the Floor. Slack portals bring work discussions into a dedicated channel; supported replies can return to the Floor and their connected destination.
Light is Lit Factory’s built-in agent. MCP connections supply available tools; the Brain keeps shared knowledge and source context accessible. External agent clients can contribute to the same work without rebuilding every brief from scratch.
Compare Jira AI and Rovo with coordinating your existing agents on a Lit Factory Floor. Keep Jira connected while choosing where your team shares decisions, reviews, and responsibility.
Jira + Rovo vs. Lit FactoryFirst-class AI coding agent support
Keep your skills, tools, and team instructions. Connect Claude Code, Codex, or Cursor to shared tasks and knowledge through MCP. Choose task autonomy to guide collaboration or independent execution.
Work on tasks with unified Floor context from Claude Code on your computer.
Lit Factory MCP
Work on tasks with unified Floor context from Codex on your computer.
Lit Factory MCP
Work on tasks with unified Floor context inside Cursor on your computer.
Lit Factory MCP
Your tools. Connected work.
Priorities, issues, ownership
Carry plans, status, and decisions between Linear and the Floor.
Tickets, owners, delivery state
Bring Jira work into implementation and delivery briefs.
Code, checks, pull requests
Connect implementation, review feedback, and release evidence.
Conversations, clarifications, handoffs
Connect work discussions and keep decisions with the work.
Designs and product decisions
Bring design intent into planning and implementation reviews.
Errors and operational signals
Connect reported errors to related changes and response owners.
Product usage and behavior
Use product signals to inform priorities and delivery decisions.
Accounts, deals, pipeline
Bring customer context into planning, follow-up, and pipeline work.
From context to delivery
A tool connection contributes shared context or an allowed action. The Floor keeps the cross-tool operating story visible while each source remains the system of record.
A ticket, review, interruption, design change, or operational signal marks the work for attention.
The agent follows configured MCP connections and workspace permissions to assemble the evidence needed for this decision.
The agent summarizes the evidence, names uncertainty, and prepares a source-specific update, handoff, or follow-up.
The owner approves, changes, or rejects the proposed move. Lit Factory records the decision with its operating context.
Automate execution
Synchronize connected work, route handoffs, and follow up on recurring requests.
Human in Control
Keep the tools and coding agents your team knows. Task autonomy guides how you collaborate and delegate; configured permissions define tool access.
connected evidence becomes a traceable operating decision, not another disconnected notification.