Project Details & Configuration
Manage your project's core configuration in the Project Details tab. Update the project name, description, connected repository, and runtime settings for your Origin environment.
The Project Details page defines the structural identity of a project inside Origin. While tasks, agents, and sandboxes 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 the project name, its last updated timestamp, and a Save Changes button. Any edits made on this page, to the name, description, team, or other fields, are only committed when you click Save Changes.
Project Name and Team
The Project Name field controls how the project appears in navigation and dashboards. Renaming it here does not modify the connected GitHub repository, and does not affect tasks, agent history, or execution logs.
The Team selector determines which team owns and manages the project. This affects visibility and configuration access. In organizations where engineers belong to multiple teams, keeping this accurate prevents accidental cross-project access.
Description
The Description field lets you record what this project represents. For example:
- "Next.js AI chatbot deployed on Vercel"
- "Internal API gateway service"
- "Client-specific customization of core platform"
This field is informational. It does not influence agent reasoning or task execution.
Milestones
The Milestones section lets you group tasks around larger deliverables. Each milestone has a name and a target date. You can add milestones using the + Add button.
Examples of milestones:
- Post-Launch Pushes
- Launch Scaling
- Pre-Launch Check
When AI Task Discovery generates multiple related tasks, assigning them to a milestone makes it easier to track progress toward a larger goal. Milestones are organizational, they do not alter how agents execute tasks.
Cycles
The Cycles section is used for time-based planning. Each cycle has a name, a date range, a duration, and a status badge, either Active or Upcoming.
For example, a project might run weekly cycles:
- Cycle 1 — Active — Mar 31 → Apr 7
- Cycle 2 — Upcoming — Apr 7 → Apr 14
- Cycle 3 — Upcoming — Apr 14 → Apr 21
Tasks can be assigned to a cycle to reflect planned delivery. This is especially useful when balancing manually created tasks with AI-generated ones and deciding what gets executed within a given window. Cycles structure planning but do not change agent behavior.
Project Metrics
The Project Metrics block provides three read-only values:
- API Key: a project-scoped key, masked by default with a copy button. Used as an internal project credential.
- Project ID: a unique, immutable identifier assigned at creation. This ID is used internally to track usage, associate execution history, and identify the project during support or debugging. It stays constant even if the project name changes.
- Total Tasks: the total number of tasks associated with this project, including both manually created and AI-discovered tasks.
Additional Information
This section confirms the repository association and creation date:
- Repository: the connected GitHub repository and active branch (for example,
Sid-Lais/lens-view-05, branch:main) - Created: the date the project was first created in Origin
If the wrong repository is connected, agent output will target the wrong codebase. This section makes it easy to verify the association at a glance.
Archive Project
The Archive Project option hides the project from the main view while preserving all data and tasks.
Archiving is appropriate 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.
Danger Zone
The Danger Zone section contains the Move to Trash action. This removes the project from normal project views. Trashed projects can be restored from Settings → Trash.
This is commonly used for test imports, short-lived experiments, or accidental repository connections.
Project Settings Overview
Explore all Project Settings in Origin, including model configuration, secrets management, sandbox setup, context documents, and logging integrations for your AI development environment.
Project Context & Knowledge Files
Explore the Context section in Origin, where you can add and manage supporting documents that help AI agents understand your project's requirements and documentation.