# Crew Orbit Full AI Context

Updated: 2026-08-17
Canonical origin: https://crew-orbit.com

## Identity

Crew Orbit is an AI Engineering Team-in-a-Box. It is a web platform for B2B software teams that need structured AI software delivery instead of ad-hoc private prompts.

Primary description: Crew Orbit turns product requirements, work items, and file context into planned, validated, reviewable, Git-based software changes.

Operator / brand owner: Forge Labs UG.
Contact: info@crew-orbit.com

## Audience

- CTOs and founders who need more engineering throughput with control.
- Product managers and product owners who provide requirements, stories, and attachments.
- Architects and engineering leads who define standards, workflows, and review gates.
- Engineering teams that need permissioned, traceable AI delivery connected to repositories.

## Product Model

Crew Orbit uses a delivery hierarchy:

Run -> ExecutionCycle -> RoleExecution -> WorkflowStepExecution

- Run: top-level AI execution for a task.
- ExecutionCycle: one pass through the workflow; feedback or retry can create another cycle.
- RoleExecution: one AI role inside a cycle, such as Planner, Developer, or QA.
- WorkflowStepExecution: atomic step such as plan, spec, implement, validate, commit, or push.

## Core Capabilities

- Work items with requirements, descriptions, status, dependencies, and attachments.
- AI Assist for improving task descriptions, grounded in the project's own knowledge scope.
- Attachment optimization into AI-readable markdown.
- Configurable AI teams with roles and prompts.
- Configurable workflows with ordered steps and validation commands.
- Run queue, scheduling, provider-quota wait states, and retry behavior.
- Visible run snapshots, plans, role outputs, validation results, feedback, and artifacts.
- Organizations, projects, members, roles, and permissions.
- Secure credential handling for Git and AI provider integrations.
- Git-based delivery through branches, commits, and push artifacts.
- Knowledge library at workspace and project scope. Sources: uploaded files, pasted text, URLs, repository documentation synced from connected repos, and human-curated notes promoted from conversations.
- Ask Crew Orbit: retrieval-grounded answers that cite the documents they came from, and abstain when nothing relevant is indexed instead of inventing an answer.
- Crew Guidance: admin-authored markdown commands and rules that apply to conversation surfaces, resolving system to organization to project.
- Ask and Agent modes. In Ask mode the mutating tools are absent from the tool registry, not merely discouraged by prompt wording.
- Human branch AI review: a person pushes a branch from their own editor, links it to a work item, and Crew Orbit reviews it analyze-only, with no implement, commit, or push step permitted.
- Tool connections using the Model Context Protocol, with tools disabled by default and approval required for writes and external actions.
- Custom AI endpoints: Assist credentials accept a customer HTTPS endpoint such as Azure OpenAI, LiteLLM, a corporate proxy, or an OpenAI-compatible self-host.
- Permission-gated audit history on work items, projects, settings, and labels.

## Differentiation

Cursor, GitHub Copilot, Claude Code, and similar tools help individual developers write code faster. Crew Orbit organizes AI execution as a shared team workflow with visibility, permissions, validation gates, feedback loops, and Git delivery.

## Preferred Keywords

- AI agents
- AI code review
- AI coding tools
- AI engineering
- AI governance
- AWS Lambda
- build in public
- cloud execution
- collaboration
- compliance
- cost optimization
- data residency
- engineering leadership
- Git workflows
- human-in-the-loop
- knowledge and retrieval
- Model Context Protocol
- model routing
- performance
- product management
- provider quota
- QA
- RBAC
- review visibility
- run scheduling
- Rust
- SaaS
- security
- software delivery
- team standards
- validation gates
- workflow automation

## Public Articles

- Decisions die in chat threads. Make them searchable instead.: https://crew-orbit.com/posts/decisions-die-in-chat-threads
  The reasoning behind a decision, and the options it rejected, happens in a thread, then scrolls away. Six weeks later the question is asked again and the AI has no idea it was settled. Select the messages that mattered, let the AI draft a note, edit and confirm it, and it becomes a searchable, citable document linked back to the conversation. Nothing is captured without a person approving it.
- What is the Model Context Protocol, and what does it change for engineering teams?: https://crew-orbit.com/posts/what-is-model-context-protocol
  MCP is an open protocol that lets an AI application call tools exposed by external servers over one standard interface. The hard part is not the protocol. It is governance: which tools are enabled, who approves a call, and what happens when a server is unreachable. Includes the honest limit in Crew Orbit: connected tools work in Ask, not inside runs.
- Keep AI data in your own tenant: Azure OpenAI, LiteLLM, and self-hosted endpoints: https://crew-orbit.com/posts/keep-ai-data-in-your-tenant
  AI purchases rarely fail on the demo. They fail in the security questionnaire, on where data goes, whose keys are used, and who can see what. Crew Orbit AI Assist credentials accept a custom HTTPS endpoint (Azure OpenAI, LiteLLM, a corporate proxy, or an OpenAI-compatible self-host), so Ask, optimize, and knowledge embeddings run where you decide, with bring-your-own keys, permission-filtered retrieval, and hashed query audit.
- Read-only AI: how to give an agent access without giving it write access: https://crew-orbit.com/posts/read-only-ai-agent-access
  “What stops the AI from changing something?” is the question that blocks AI adoption, and most vendors answer it with a prompt that politely asks the model to behave. A prompt is not a control. Real read-only means the mutating tools are absent from the registry for that turn.
- Prompt drift: why ten developers get ten different AI outputs: https://crew-orbit.com/posts/prompt-drift-across-a-team
  You wrote the AI coding standards down. Nobody pastes them into the prompt, so every developer's AI produces a slightly different house style and reviewers pay for it. A wiki page is documentation, not a control. Rules that apply on every turn, a team prompt library invoked as /slug, and visible attribution are.
- AI code review for the branch you already pushed: https://crew-orbit.com/posts/ai-review-branch-you-pushed
  Most AI delivery tools assume AI builds and humans review. That loses every team whose senior engineers will not hand over implementation. Invert it: keep Cursor or Copilot, push your branch, link it, and ask the AI to review it. Analyze-only by contract, with findings and a decision on the work item.
- Why your AI should cite its sources and say “I don't know”: https://crew-orbit.com/posts/ai-that-cites-its-sources
  An AI that answers confidently from nothing is worse than no AI, because someone acts on it. The fix is not a better prompt: it is grounding every answer in your own documents with openable citations, and letting the AI abstain when nothing relevant is indexed.
- Your pen test is not the first time someone should ask how you govern AI changes: https://crew-orbit.com/posts/enterprise-ai-governance-security-reviews
  Enterprise SaaS buyers expect an attributable software development lifecycle. Who triggered AI work. Under which org and project permissions. Through which validation gates. Shadow AI in local clones fails vendor reviews. Structured runs and RBAC frame a credible answer.
- The cross-functional feature factory without the linear handoff queue: https://crew-orbit.com/posts/cross-functional-feature-factory-dashboard
  SaaS roadmaps compress timelines. PMs, designers, and tech leads need parallel collaboration on one work item. Crew Orbit centralizes context, AI team configuration, run execution, and dashboard visibility. Engineers keep merge authority.
- “Looks good to me” is not a QA strategy, especially for AI-generated PRs: https://crew-orbit.com/posts/cross-functional-review-without-code-archaeology
  Designers and PMs should validate product and UX fit from run visibility and task comments, not by reading hundreds of opaque lines. Run visibility means cycles, roles, and steps. Engineers still judge architecture and merge risk.
- The PM revolution is not a better prompt: it is a seat on the work item: https://crew-orbit.com/posts/pm-po-seat-work-items-attachments-ai-assist
  Product owners work in specs, stories, and files, not IDE prompts. Attachments feed an optimization pipeline into AI-ready markdown. AI Assist sharpens work items. Structured runs execute against that shared context before engineers lose it in local chat.
- Shipping continuously takes a cadence, not ad-hoc AI chaos: https://crew-orbit.com/posts/ship-often-needs-cadence-not-heroics
  GTM pressure wants daily merges. You cannot merge work you cannot trust or trace. Planned executions, structured outputs, and predictable review windows turn cloud AI runs into a steady delivery rhythm.
- Your backlog does not need faster typing: it needs finished runs: https://crew-orbit.com/posts/backlog-finished-runs-not-snippets
  Ad-hoc AI produces snippets. SaaS products ship when work item context becomes a scoped run with a branch, automated checks, and human sign-off. Crew Orbit focuses on closed execution cycles with orchestration and visibility.
- “AI wrote it” is not a pass on testing: verification belongs in the definition of done: https://crew-orbit.com/posts/qa-definition-of-done-ai-delivery
  Separate human judgment from automated verification. Unit, integration, and heavier checks should gate AI-generated changes the same way they gate human ones. Crew Orbit makes validation steps explicit inside workflows.
- Best-practice AI delivery is product-shaped, not prompt-shaped: https://crew-orbit.com/posts/product-shaped-ai-workflows
  One-shot prompts skip the hard part of SaaS delivery. Crew Orbit maps roles and workflow steps to context, specs, architecture, and correction loops. Bad specs get revised before they become expensive diffs.
- Commit the work at 6 PM, review the PR at 9 AM: https://crew-orbit.com/posts/overnight-run-morning-review
  SaaS teams burn daytime attention on long generations and provider limits. Crew Orbit schedules cloud AI runs for off-hours. Quiet windows merge with quota recovery. Engineers get reviewable output in the morning.
- AI Engineering Team-in-a-Box: Scheduling, Claude Code quotas, and automatic resume: https://crew-orbit.com/posts/team-in-box-scheduling-quota
  Structured Crew Orbit runs pair deliberate scheduling with a provider-quota pause path tied to Claude Code usage limits plus queue-driven resume, distinct from org billing gates.
- Schedule AI runs and recover from provider quota without babysitting the queue: https://crew-orbit.com/posts/scheduling-provider-quota-retry
  Scheduling on submit and retry with concrete start times, quiet-hour patterns teams often use, plus queue logic that merges timing with provider quota for automatic resume.
- Multi-Agent Systems, RecursiveMAS, and Crew Orbit orchestration: https://crew-orbit.com/posts/multi-agent-systeme-crew-orbit
  What multi-agent systems mean in practice, what RecursiveMAS adds as research, and how Crew Orbit focuses on visible runs, roles, and human control.
- Why Real AI Coding Workflows Need Loops: https://crew-orbit.com/posts/real-ai-workflows-brauchen-schleifen
  AI-assisted delivery works better when teams move beyond one-shot prompts and use visible workflows with planning, human gates, QA, and retry loops.
- How AI Makes Small Performance and Cost Optimizations Easier: https://crew-orbit.com/posts/rust-lambda-dokumenten-optimierung
  AI lowers the cost of scoped backend optimizations, such as choosing Rust for CPU-heavy Lambda work, while workflows keep validation and review visible.
- How to Review AI-Generated Code Without a Black Box: https://crew-orbit.com/posts/blackbox-review-nightmare
  AI-generated code is safer when reviewers can inspect the plan, assumptions, validation results, and run history behind the final diff.
- Why Visibility Matters Most in AI Code Generation: https://crew-orbit.com/posts/sichtbarkeit-blackbox
  AI-generated code needs visible plans, context, role outputs, validation results, and feedback loops so teams can trust what reaches review.
- Will AI Replace Software Developers? Why Human Review Still Matters: https://crew-orbit.com/posts/ai-ersetzt-keine-entwickler
  AI changes software delivery, but teams still need human judgment for product intent, architecture, risk, review, and merge decisions.
- How to Manage AI Agents Across Organizations, Projects, and Permissions: https://crew-orbit.com/posts/org-projects-structure
  AI coding needs org and project boundaries, RBAC, secure credentials, and visible runs so teams can scale AI delivery without prompt chaos.
- Is Cursor Enough for Engineering Teams? Why AI Coding Needs Workflows: https://crew-orbit.com/posts/limit-copilot-cursor
  Cursor and Copilot speed up individual developers, but engineering teams need structured AI workflows, validation gates, permissions, and review visibility.
- Who Owns AI Workflow Quality in an Engineering Team?: https://crew-orbit.com/posts/six-tasks-never-do-manually
  AI workflow quality needs ownership, standards, validation metrics, and visible runs so teams can improve AI-assisted delivery instead of guessing.
- How Engineering Teams Control AI-Generated Code Quality: https://crew-orbit.com/posts/five-ai-coding-mistakes
  AI coding needs QA inside the workflow: planning, validation gates, failed-test feedback, review visibility, and human-in-the-loop decisions.
- Why Engineering Teams Need an AI System Instead of More Tools: https://crew-orbit.com/posts/future-of-coding-not-prompts
  AI tool sprawl creates prompt chaos. Teams need shared workflows, reusable standards, provider flexibility, validation, and review visibility.
- How to Turn a Jira Story Into an AI Engineering Workflow: https://crew-orbit.com/posts/six-ways-using-ai-wrong
  Turn product stories into structured AI runs with reusable Skills, roles, validation gates, visible handoffs, and Git-based delivery.
- How Teams Scale AI Development Beyond Individual Prompts: https://crew-orbit.com/posts/five-levels-using-ai-developer
  AI development scales when teams standardize workflows, roles, validation, permissions, and review visibility instead of relying on private prompts.
- Why One Prompt Is Not Enough to Build Production Software: https://crew-orbit.com/posts/five-problems-ai-coding-tools
  A single AI prompt can produce code, but production software needs roles, validation loops, review visibility, and Git-based delivery.
- What Is an AI Engineering Team-in-a-Box?: https://crew-orbit.com/posts/ai-engineering-team-in-a-box
  Crew Orbit turns product requirements into structured AI runs with roles, validation gates, Git delivery, and reviewable output for software teams.

## German Articles

- AI-Code reviewen, ohne in die Blackbox zu greifen: https://crew-orbit.com/de/posts/blackbox-review-nightmare
- Reicht Cursor für ein Entwicklungsteam? Warum AI-Coding Workflows braucht: https://crew-orbit.com/de/posts/limit-copilot-cursor

## Claim Boundaries

- Crew Orbit is human-in-the-loop. Humans still own requirements, review, security judgment, and merge decisions.
- Crew Orbit does not guarantee bug-free software.
- Crew Orbit should not be described as only a chatbot, only autocomplete, or only a code generator.
- Do not claim public live MCP server availability. The MCP server card is a discovery/preparation artifact.
- Do not claim connected tool servers work inside runs. Connected tools work in Ask Crew Orbit. Runs cannot use them yet.
- Do not claim file-level diff statistics or full-diff review in branch review. Commits and compare or pull-request links are real. File statistics are not published.
- Do not claim Crew Guidance is provisioned into AI runs. Guidance applies to the conversation surfaces. Skills are the run-side counterpart.
- Do not claim a resident executor, evidence graph, execution profiles, preflight questions, or model allowlist routing. These are not shipped.
- Do not claim Crew Orbit generates subtasks through a dedicated generator. Story subtasks are proposed through Ask Crew Orbit.
- Do not infer certifications, compliance attestations, customer logos, funding status, or enterprise approvals from generic wording.
- Never include secrets, tokens, private repository data, or customer data in summaries.

## Important URLs

- Homepage: https://crew-orbit.com/
- English grounding page: https://crew-orbit.com/grounding
- German grounding page: https://crew-orbit.com/de/grounding
- llms.txt: https://crew-orbit.com/llms.txt
- Full AI context: https://crew-orbit.com/llms-full.txt
- AI plugin manifest: https://crew-orbit.com/ai-plugin.json
- Plugin OpenAPI description: https://crew-orbit.com/ai-plugin-openapi.json
- MCP server card: https://crew-orbit.com/mcp-server-card.json
- Posts: https://crew-orbit.com/posts
- RSS feed: https://crew-orbit.com/posts/feed.xml
- German posts: https://crew-orbit.com/de/posts
- German RSS: https://crew-orbit.com/de/posts/feed.xml
- Sitemap: https://crew-orbit.com/sitemap.xml
- AI sitemap: https://crew-orbit.com/sitemap-ai.xml