# Welcome to Codaro
Source: https://docs.codaro.dev/index
Codaro boosts developer efficiency, enhances team visibility, and drives better cooperation. Don't miss deadlines, eliminate time-wasting status meetings, and proactively prevent issues from escalating with real-time, AI-driven insights.
## Codaro: Your Helper for Agentic Team Management
Codaro ends the **Dashboard Era**. We shift your engineering organization from passive, retrospective reporting to **proactive, Agentic Orchestration**. We don't just measure past work; we intervene to ensure continuous developer flow, prevent bottlenecks, and guarantee on-time delivery. This empowers team managers to gain crucial visibility and focus on true team leadership and strategic resource allocation, not micromanagement or chasing status updates.
## Quick Setup Guide
Getting started is simple. Follow our integrated setup guide to connect your Version Control System (VCS), Task Management, and your team's IDEs to start receiving actionable insights immediately.
Detailed steps for connecting GitHub/BitBucket, Jira, and installing the Codaro IDE Plugin for full functionality.
***
## Problems Solved & Benefits Gained
Codaro’s Agentic approach solves the daily chaos and complexity that traditional, retrospective tools cannot. This is the structural shift from passive measurement to proactive intervention.
Learn how Codaro eliminates status meetings, prevents deadline risks and ensures AI-generated code translates directly into business value, not technical debt.
***
## Codaro Functions: Feature Deep-Dive
Explore the primary components that make up the Codaro Agentic Management Platform.
The central intelligence layer. Details on the catalog of real-time alerts (`COLLISION_WARNING`, `DEADLINE_RISK`) and how they are delivered.
Explaining the structure and content of AI-generated reports (General, Technical, Workflow) that provide instant team status.
**Strategic View.** Daily Impact Briefings (Highlights/Lowlights) and Team Pulse Summaries that replace status meetings.
Data privacy, retention policies, and compliance details, including options for On-Premise deployment.
# Alert System
Source: https://docs.codaro.dev/product/alerts
A complete catalog of Codaro's real-time interventions, how they are triggered, and the value they provide.
## The Smart Alert System
The Smart Alert System is the core of Codaro's real-time philosophy. Unlike passive dashboards that wait for you to look at them, Smart Alerts proactively push high-signal information to you the moment it happens.
We classify alerts into three categories: **Collaboration**, **Risk**, and **Process**.
***
## 1. Collaboration Alerts
*Preventing friction and merge conflicts before they happen.*
### 🤝 Collision Warning (`COLLISION_WARNING`)
The "Air Traffic Control" for your codebase. This alert fires when two developers are heading towards a merge conflict.
* **Trigger Logic:**
* Two or more active editing sessions are detected on the **same file** (or overlapping file paths).
* Activity must occur within the same **5-minute sliding window**.
* **The Problem Solved:** Merge conflicts waste hours of time and cause regressions. Developers often don't know a teammate is touching the same file until they try to push.
* **The Value:** Immediate coordination. Developers can Slack each other ("Hey, I see you're on `auth.ts`, let's sync") before writing incompatible code.
### 📦 Code Merged (`CODE_MERGED`)
A positive reinforcement loop that keeps the team in sync without status meetings.
* **Trigger Logic:** A Pull Request is successfully merged into the target branch (e.g., `main` or `develop`).
* **The Value:** Instant awareness. Dependent tasks can be unblocked immediately without waiting for the next stand-up.
***
## 2. Health & Risk Alerts
*Identifying invisible struggle and technical debt in real-time.*
### ⚠️ High Code Churn (`HIGH_CODE_CHURN`)
This is our "Struggle Detection" mechanic. It identifies when a developer is working hard but making little forward progress.
* **Trigger Logic:**
* **Duration:** Session lasts > **45 minutes**.
* **Pattern:** High volume of lines changed (Churn) but low Net Progress (final file size change).
* **Concentration:** Activity is focused on 1-3 "hot files."
* **The Problem Solved:** Developers often spin their wheels on refactoring or complex bugs, afraid to ask for help.
* **The Value:** Empathy and Support. It prompts a manager or lead to check in: *"I see you're wrestling with the payment module. Want to pair on it?"*
### 🔥 Critical Risk Detected (`CRITICAL_RISK_DETECTED`)
An automated quality gate powered by the AI Technical Report.
* **Trigger Logic:**
* Triggered when the **AI Technical Report** analyzes a commit.
* A specific risk (security vulnerability, breaking change, anti-pattern) is identified with a **Severity Score ≥ 8/10**.
* **The Value:** Safety. Prevents bad code from sitting in the repository unnoticed. It acts as an instant, automated code review for high-severity issues.
***
## 3. Process & Workflow Alerts
*Automating the "boring" parts of project management.*
### 🚀 Task Started (`TASK_STARTED`)
Eliminates the need for manual Jira updates or "I'm starting this now" messages.
* **Trigger Logic:**
* The first **Heartbeat** is detected on a git branch associated with a specific Task ID (e.g., `feature/PROJ-101`).
* **The Value:** Visibility. Everyone knows exactly what is actively being worked on right now.
### 🔄 Task Reopened (`TASK_REOPENED`)
A critical alert for preventing scope creep and zombie tasks.
* **Trigger Logic:**
* Code activity (Heartbeat) is detected on a task that was previously marked as **Done/Completed**.
* **The Problem Solved:** "Zombie tasks" that come back to life often indicate hidden bugs, regressions, or scope creep that wasn't planned.
* **The Value:** Control. Managers can instantly ask: *"Why are we working on the login page again? I thought that was shipped last week."*
### ⏳ Stalled Task (`STALLED_TASK`)
Finds work that has fallen through the cracks.
* **Trigger Logic:**
* A task has a status of **In Progress**.
* No Git activity (Commits or Heartbeats) has been detected for this task for a configured threshold (default: **48 hours**).
* **The Value:** Flow. Prevents tasks from rotting in the "Doing" column and helps unblock developers who might have context-switched away.
### ✅ Task Completed (`TASK_COMPLETED`)
Closes the loop on value delivery.
* **Trigger Logic:**
* A task status changes to a completion state (e.g., `Done`, `Deployed`, `Closed`) in the external system (Jira/Linear).
* **The Value:** Celebration and Closure. Confirms that the code has translated into business value.
***
## 4. Smart Summaries
*AI-driven synthesis of complex activities.*
### ✅ New Commit (`NEW_COMMIT`)
The "Smart Commit Message."
* **Trigger Logic:** A new commit is pushed.
* **The Value:** Instead of a cryptic message like *"fix bug"*, Codaro's AI generates a clear, human-readable summary of the business impact: *"Fixed null pointer exception in user login flow."*
# Intelligence Briefings
Source: https://docs.codaro.dev/product/briefing
How Codaro's Impact Briefing replaces daily status meetings with a single, stateful source of truth.
## The Impact Briefing
Codaro synthesizes thousands of data points—commits, alerts, and heartbeat metrics—into a single, high-signal view called the **Impact Briefing**.
Designed for Engineering Managers and CTOs, the Impact Briefing answers the two most important questions in software delivery: *"What value did we ship?"* and *"What risks are currently active?"*
***
## The "Stateful" Philosophy
Most engineering reports are **ephemeral** (e.g., a Jira message that scrolls away) or **stateless** (e.g., a dashboard that resets every sprint).
The Impact Briefing is **Stateful**.
* **Persistent Risks:** If a critical issue triggers on Monday and isn't fixed, it remains pinned to your briefing on Tuesday, Wednesday, and Thursday. It effectively "haunts" the briefing until resolved.
* **Value Ledger:** It creates a permanent record of value delivered, separating "busy work" (chore commits) from "shipped value" (feature completion).
***
## 1. Highlights: What We Shipped (The Value Ledger)
*Replacing the "What did you do yesterday?" stand-up question.*
The **Highlights** section filters out the noise of daily development to show only the work that moves the business forward.
### How It Works
* **Noise Filtering:** Codaro’s AI analyzes every commit. It automatically suppresses low-value activity (e.g., "fix typo", "update readme", "merge branch") from the strategic view.
* **Value Extraction:** It highlights significant changes: Feature completions, Bug fixes, and Performance improvements.
### The Briefing View
> **✅ Shipped Today:**
>
> * **Sarah (Checkout Team):** Enhanced payment validation to prevent fraudulent transactions. *(Feature)*
> * **Mike (Platform):** Migrated the User Auth service to the new API, reducing latency by 200ms. *(Performance)*
> * **Alex (Frontend):** Fixed the crashing bug on the settings page reported by Customer Support. *(Bug Fix)*
***
## 2. Lowlights: Active Risks (The blockers)
*Replacing the "Any blockers?" stand-up question.*
The **Lowlights** section is your daily "Call to Action." It lists **Active Unresolved Alerts** that require management intervention.
### The Persistence Engine
A Lowlight only disappears when the underlying issue is resolved in the code.
* **Auto-Resolution:** If a `CRITICAL_RISK` alert was triggered by a bad commit, pushing a fix (a new commit that resolves the risk) automatically clears the Lowlight.
* **Manual Resolution:** Managers can dismiss alerts that are false positives or "won't fix."
### Urgency Markers
The briefing visually prioritizes risks based on how long they have been ignored:
* ⚠️ **Warning (>4h):** The issue is fresh but unaddressed.
* 🚨 **Critical (>8h):** The issue has persisted through a full work day. Immediate intervention required.
### The Briefing View
> **🚨 Active Lowlights (Action Required):**
>
> * **\[8h ago] Critical Security Risk:** SQL Injection vulnerability detected in `user.controller.ts`. *Owner: Pending*
> * **\[5h ago] High Code Churn:** Developer Tom has been struggling with `billing-logic.ts` for 5 hours with zero net progress. *Action: Schedule Pair Programming.*
> * **\[4h ago] Stalled Task:** The "Q3 Reporting" task has had no activity for 48 hours but is marked "In Progress."
# AI Reports
Source: https://docs.codaro.dev/product/reports
How Codaro's multi-agent system analyzes every commit to provide deep technical, workflow, and business insights.
## AI Reports: From Diff to Wisdom
Every time code is pushed to your repository, Codaro triggers a chain of AI agents to analyze the work. We don't just look at *lines changed*; we analyze intent, quality, and behavior.
These reports are generated automatically and stored permanently, creating a "living history" of your project's evolution.
***
## 1. The General Report (The "CEO Translator")
**Audience:** Product Managers, Stakeholders, Non-Technical Leadership.
Most engineering updates are unintelligible to business leaders ("Updated the polymorphic association in the user model"). The General Report translates this technical work into business value.
### How It Works
* **Input:** The raw Git diff + linked Jira task context.
* **The "Translator" Agent:** An AI model instructed to strip out all technical jargon (e.g., refactoring, endpoints, payloads) and focus purely on *user impact*.
* **Output Example:**
* *Raw Commit:* `feat: refactor auth.service.ts to handle null token payload`
* *General Report:* "Fixed a critical bug that caused the login page to crash for some users, improving system stability."
### Key Metrics
* **Impact Level:** Low / Medium / High (Is this a trivial tweak or a major release?)
* **Estimated Effort:** Trivial / Moderate / Significant (Did this take 5 minutes or 5 hours?)
***
## 2. The Technical Report (The "Staff Engineer")
**Audience:** Developers, Tech Leads, QA.
This report acts as an automated, asynchronous code review. It doesn't replace human review but augments it by catching complexity and risks instantly.
### How It Works
* **Input:** The raw Git diff + Static Analysis Metrics.
* **The "Reviewer" Agent:** An AI model adopting the persona of a strict Staff Engineer. It performs a **Proportional Review**:
* *Low Impact Changes:* Brief sanity check.
* *High Impact Changes:* Deep analysis of architecture and security.
* **Critical Risk Detection:** If the agent identifies a risk with a severity score ≥ 8/10 (e.g., SQL Injection, Breaking API Change), it triggers a `CRITICAL_RISK_DETECTED` alert immediately.
### Key Metrics
* **Severity Score (0-10):** A quantitative risk assessment.
* **Complexity Delta:** Did this commit make the codebase cleaner or more complex?
* **Code Smells:** Automated detection of anti-patterns (e.g., God Classes, Magic Numbers).
***
## 3. The Workflow Report (The "Team Mentor")
**Audience:** Engineering Managers, Developers.
This is Codaro's unique capability. We analyze *how* the code was written to understand developer experience and flow.
### How It Works
* **Input:** The Git diff + Real-time Heartbeat data (from the IDE plugin).
* **The "Mentor" Agent:** Reconstructs the work session to answer questions like: *Was this a focused deep-work session, or a fragmented struggle?*
### Key Metrics
* **Flow State %:** The percentage of time spent in deep, uninterrupted work (vs. context switching).
* **Productivity Score:** A synthesis of output volume and focus quality.
* **Context Switches:** How many times the developer had to jump between files or tasks (a high number indicates distraction or poor task definition).
> **Why this matters:** A developer might ship a small PR but have a low productivity score because they were interrupted 15 times. The Workflow Report reveals this hidden cost.
# Complete Setup Guide
Source: https://docs.codaro.dev/quickstart
Get Codaro connected to your version control, task management, and IDE in three simple steps to unlock real-time Agentic Intelligence.
## 4-Steps Setup Guide
**Integration is very simple and takes around 3 minutes.** Our platform is designed for rapid deployment. If we don't currently support an app you use, please contact us at [**info@codaro.dev**](mailto:info@codaro.dev) and we commit to providing support for it within 24-48 hours.
Follow these four steps to fully connect your engineering ecosystem and begin experiencing the benefits of Agentic Management.
Codaro requires read-access to your VCS to track code changes, commits, and Pull Request (PR) activity. This data forms the **ground-truth** of all engineering work.
You must be an **Owner** or **Admin** of the organization to authorize this step.
1. Navigate to **Integrations** Tab in your Team in the Codaro web app.
2. Select your provider: **GitHub** or **BitBucket**.
3. Follow the OAuth prompt and select the repositories you want Codaro to analyze.
* **Why we need this:** This allows us to generate code activity reports and summaries, find issues in the code, and have the best data-driven insights. More strategically, this raw data is the input for the Smart Alert System and Agentic Engine, giving us the huge context necessary to predict and intervene *before* problems occur.
Connecting your TMS is vital for providing **business context**. This step links code activity (from Step 1) to specific project goals and deadlines, which is essential for our predictive AI.
You must have the necessary **Admin** rights within your TMS to configure the connection and map projects.
1. In the Codaro web app, navigate to **Integrations** Tab.
2. Select your provider: **Jira** (contact [info@codaro.dev](mailto:info@codaro.dev), if your App is missing).
3. Authenticate and select your TMS Project Identifiers (e.g., `PROJ`, `MVP`, `APP`) in the popup.
* **Why we need this:** This enables Codaro to link commits to your tasks, allowing for progress tracking and aggregation of **business context** for the Agentic Engine. This context is critical for predictive alerts like `TASK_STARTED` or `TASK_STALLED`.
**Context Linking Tip:** To ensure accurate linking between your code and tasks, include the Project Identifier (e.g., `PROJ-692`) in your commit message or branch name (e.g., `features/PROJ-692-new-api`).
While Steps 1 and 2 activate the core platform, inviting your team is how Codaro begins to deliver value at scale.
1. Go to the **Team** tab in Codaro and click the **Invite Team Member** button.
2. Invite team members via their email addresses. They will need to accept the invitation from the mail they recieve to gain access.
3. Once logged in, individual team members can connect their personal integrations (e.g., Jira/Github) and, crucially, download the IDE Plugin (Step 4).
For developers, the IDE Plugin is the primary interaction point with Codaro. It is the tool that preserves **flow state** and provides hyperlocal, real-time data to the Agentic Engine for comprehensive workflow analysis.
1. Search for **"Codaro"** in the [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=Codaro.Codaro), [VSX Registry Marketplace](https://open-vsx.org/extension/Codaro/Codaro) or [JetBrains Marketplace](https://plugins.jetbrains.com/plugin/28408-codaro) and click **Install**.
2. Use the shortcut `Ctrl+Shift+P` (or `Cmd+Shift+P` on Mac) and type **"View: Show Codaro"** to open the sidebar.
3. Copy your **UID** from the **Integrations > IDE Extension** tab of your dashboard, paste it into the sidebar input, and click **Save UID** to link your workspace.
* **Why we need this:** The plugin sends a silent 'heartbeat' (activity data) which is crucial for determining **Flow State Index** and generating hyperlocal alerts like the `COLLISION_WARNING`. This deep, real-time context allows Codaro to **analyze developer workflow** and provide insights into who is online or may potentially need a quick sync or assistance.
**Verify Your Extension**\
To avoid malicious clones, ensure you are using the official extension with the unique identifier: `codaro.codaro`
See the full list of supported Apps for Integrations in Codaro web app
## Security and Privacy
Codaro is built on a foundation of **enterprise-grade security** and strict data privacy standards. We commit to maximum data isolation and control, and we never use your proprietary code for training AI models.
Detailed documentation on data isolation, compliance (GDPR/CCPA), PII handling, retention policies, and our options for On-Premise and Self-Hosted deployment.
# Value Proposition
Source: https://docs.codaro.dev/valueprop
Why engineering leaders are switching from passive dashboards to Agentic Management.
Engineering management is broken. As teams scale, leaders are forced into a toxic choice: **micromanage to stay informed** or **fly blind and hope for the best**.
Codaro exists to solve the three structural gaps in modern engineering. We replace reactive firefighting with proactive, automated clarity, shifting your organization from the "Dashboard Era" to the era of **Agentic Orchestration**.
***
## 1. The Visibility Gap
### You can't manage what you can't see.
**The Pain:** Without clear traction data, leadership feels forced to interrupt developers just to get a pulse check on the project. "How is the API coming along?" becomes a distraction that pulls a senior engineer out of focus.
**The Codaro Solution: Automated Clarity.** We provide **Zero-Touch Reporting**. Codaro converts raw Git & Jira activity into clear, real-time progress signals.
* **For Leaders:** You get total project visibility without asking a single question.
* **For Teams:** Total autonomy. No one has to "report" progress because the work itself reports the progress.
***
## 2. The "Quick Sync" Tax
### Meetings are the enemy of flow.
**The Pain:** Every status meeting, stand-up, and "quick update" breaks the deep work flow state. It costs your developers an average of **23 minutes of recovery time** per interruption to get back into the zone.
**The Codaro Solution: Flow State Protection.** We enable **Asynchronous Alignment**. Codaro works silently in the background to handle the reporting.
* **The Shift:** We move status updates out of the meeting room and into the background.
* **The Result:** Developers stay in their IDE, solving hard problems, while you stay fully informed via AI-generated summaries.
***
## 3. Reactive Firefighting
### Bad news travels too slowly.
**The Pain:** In traditional teams, you often discover critical bottlenecks, stuck PRs, technical debt, poor code quality, or high code churn only when the deadline is already at risk. By the time the dashboard shows red, it's too late to fix it without crunch time.
**The Codaro Solution: Proactive Health Check.** We identify invisible blockers and struggle early. Codaro alerts you to deviations before they become delays.
* **Early Detection:** We flag specific risks in real-time:
* **Stuck PRs:** Identifying reviews that are idling and blocking the pipeline.
* **Rework Loops:** Spotting tasks with abnormally high churn (writing/rewriting).
* **Code Issues & Bugs:** Detecting potential logical errors and bugs before they even reach the QA stage.
* **Intervention:** Solve coordination problems and resource gaps days before they impact the sprint goal.
***
## Why Top Teams Choose Codaro
Real-time clarity that cuts distractions and frees up your calendar.
We provide early warnings when tasks stall. By detecting bottlenecks before they become critical, Codaro keeps your projects on track automatically, giving you the confidence to commit to dates.
We eliminate friction. By helping your team avoid merge conflicts and reducing status pings, developers stay in deep, productive flow, shipping code significantly faster.
Stop chasing status updates. Replace manual reporting with proactive insights so you can focus on strategy, architecture, and team growth instead of micromanagement.
Know exactly what moved forward with every commit without sitting through status meetings. You get a real-time feed of value delivery, not just code volume.
