Project Details

The Project Details page defines the structural identity of a project inside Origin. While tasks, agents, and the workspace handle day-to-day execution, this page manages the project's long-term configuration, ownership, planning structure, and lifecycle state.

Everything here is project-scoped and remains stable even as tasks are created, branches change, or agent executions increase.

Project Header

At the top of the page, you’ll see:

• Project Name
• Last Updated timestamp
• Team
• Save Changes button

This is where the project's visible identity is defined.

For example, if you are managing multiple similar repositories, such as a production chatbot, a staging version, and an experimental fork, renaming the project here helps avoid confusion when switching between environments in the sidebar.

Changing the project name:

• Updates how it appears in navigation and dashboards
• Does not modify the connected GitHub repository
• Does not affect tasks, agent history, or execution logs

The Team selector determines which team owns and manages the project. This impacts visibility and configuration access. In organizations where engineers belong to multiple teams, this prevents accidental cross-project execution.

Description

The Description field allows you to define what this project represents.

Typical examples include:

• “Next.js AI chatbot deployed on Vercel”
• “Internal API gateway service”
• “Client-specific customization of core platform”

This description is informational. It does not influence agent reasoning or execution behavior. Its purpose is clarity, especially when onboarding new contributors or reviewing archived projects months later.

Milestones

The Milestones section lets you group tasks into larger deliverables.

You can create milestones to track progress toward objectives, such as:

• “v1 Public Launch”
• “Performance Optimization Phase”
• “Authentication Refactor”

When AI Task Discovery generates multiple related tasks (for example, around performance improvements), assigning them to a milestone makes it easier to monitor progress toward that larger goal.

Milestones are organizational. They do not alter how agents execute tasks.

Cycles

The Cycles section is used for time-based planning.

Cycles typically represent:

• Weekly sprints
• Two-week iterations
• Stabilization windows

For example, if you are running a two-week sprint, you can create a cycle called:

Sprint 8 – February Week 3–4

Tasks can then be assigned to that cycle to reflect planned delivery. This is especially useful when balancing manually created tasks with AI-generated recommendations and deciding which tasks actually get executed within a specific timeframe.

Cycle structure planning, but do not change agent capabilities.

Project Metrics

The Project Metrics section provides stable identifiers and summary data.

API Key

The API Key shown here is project-scoped. It serves as an internal credential for the project context.

Currently, it:

• Does not trigger external execution
• Does not allow direct repository access
• Does not bypass Origin’s permission model

It exists as a stable reference point and for forward compatibility with programmatic workflows.

Project ID

The Project ID is a unique, immutable identifier assigned at creation.

This ID is used internally to:

• Associate execution history
• Track usage
• Identify the project during support or debugging

Even if the project name changes, the Project ID remains constant.

Total Tasks

The Total Tasks counter shows how many tasks are associated with this project.

This includes:

• Manually created tasks
• AI-discovered tasks

It gives a quick sense of project activity. For example:

• A newly imported repository may show only a handful of tasks.
• A mature project undergoing continuous AI-assisted development may show dozens.

Additional Information

This section confirms the repository association and creation date.

It includes:

• Connected repository (e.g., User/nextjs-ai-chatbot)
• Default branch (e.g., main)
• Created date

This is important for verification.

For example, if you accidentally connect a fork instead of the production repository, this section immediately reveals that mismatch.

Agents read code, generate diffs, and create pull requests against the repository shown here. If this is incorrect, agent output will target the wrong codebase.

Repository switching itself is handled elsewhere, but this page confirms what is currently active.

Archive Project

The Archive Project control allows you to remove the project from active views while preserving all data.

Archiving keeps:

• Tasks and history
• Milestones and cycles
• Execution logs
• Usage metrics

This is useful when:

• A feature has been fully delivered
• A client engagement has concluded
• A repository is no longer actively maintained

Archived projects can be restored later.

Move to Trash

Under the Danger Zone, you can move the project to Trash.

This action:

• Removes it from normal project views
• Makes it recoverable from the Trash section
• Signals intent to retire the project

This is commonly used for:

• Test imports
• Short-lived experiments
• Accidental repository connections

Once permanently deleted from Trash, all project data, including tasks and execution history, is removed.

How This Page Is Used in Practice

Teams typically use the Project Details page to:

• Clarify project identity and ownership
• Organize work into milestones and cycles
• Confirm repository association
• Review task volume and project maturity
• Archive completed initiatives
• Remove experimental or test projects

While agents drive execution through tasks and workspace activity, this page defines the stable structural backbone of the project inside Origin.