GitHub Copilot Workspace: la IDE conversacional de GitHub

javi
Pantalla de desarrollo con múltiples ventanas de código en entorno moderno

GitHub Copilot Workspace (announced April 2024, preview later) es GitHub’s attempt a reimaginar development workflow: en vez de “inline completion”, propone task-first. Describe qué quieres, Copilot genera plan multi-file, applies changes, tests. Compite con Cursor Composer pero nativo GitHub. Aún en technical preview al momento.

El modelo

Workflow:

  1. Open GitHub Issue: describes el problem.
  2. Launch Workspace: Copilot reads issue + codebase.
  3. Plan phase: Copilot proposes steps.
  4. Edit phase: Copilot implements changes.
  5. Test phase: runs tests, iterates.
  6. Create PR: with summary.

Esencialmente AI dev completing tasks end-to-end.

Integración GitHub

Native:

  • Issues as task source.
  • PRs as output.
  • Codespaces como workspace.
  • Actions: CI triggers on changes.
  • Projects: task management.

Enterprise-friendly workflow.

Copilot Workspace vs Cursor Composer

Aspect Copilot Workspace Cursor Composer
Primary interface Browser + GitHub VS Code fork
Task source GitHub Issue Text prompt
Planning phase Explicit Implicit
Multi-file Yes Yes
Ecosystem GitHub-first IDE-first
Maturity Preview GA
Model OpenAI (presumably) Multi-provider

Copilot Workspace: team/GitHub workflow. Cursor Composer: solo developer productivity.

Features

Plan preview

Antes de changes, Copilot muestra:

  • Files affected.
  • Steps to implement.
  • Dependencies.

User can edit plan before execution.

Multi-file edits

Single task can touch many files:

  • Add feature en backend + frontend + tests.
  • Refactor across modules.
  • Upgrade library version.

Plan-first approach helps.

Test integration

After changes:

  • Runs existing tests.
  • Generates new tests.
  • Iterates si fails.

Closed loop testing.

Codespace execution

  • Workspace runs en GitHub Codespace.
  • Full dev environment.
  • Standard tools available.
  • Ephemeral.

Typical session

Issue: "Add user deletion endpoint with soft-delete"

Copilot Workspace:
  Plan:
    1. Add soft_deleted column to User model
    2. Create migration
    3. Add DELETE /users/:id endpoint
    4. Update User serializer
    5. Add tests

  Execute? (user reviews, approves)

Executing...
  - Modified: models/user.py
  - Created: migrations/0005_soft_delete.py
  - Modified: api/users.py
  - Modified: tests/test_users.py

Running tests...
  - All passing.

Creating PR...
  - PR #124: "feat: add soft-delete to user endpoint"

Smooth pero quality varies per task.

Donde brilla

  • Issues bien descritos → clean PRs.
  • Well-tested codebases: Copilot uses tests como spec.
  • Standard tasks: CRUD, bug fixes, simple features.
  • Team workflows: devs review generated PRs.

Donde falla

  • Ambiguous requirements: needs clearer issue.
  • Complex architecture: misses big picture.
  • Legacy codebases sin tests: stumbles.
  • Non-standard patterns: suggestion low-quality.
  • Large refactors: limited context.

Pricing

Availability phases:

  • Technical preview: free limited access.
  • Copilot Enterprise ($39/user/mes): includes workspace features.

Pricing eventually likely to match Copilot Enterprise tier.

vs Cursor para teams

Cursor:

  • Individual productivity: excellent.
  • Team workflows: limited.

Copilot Workspace:

  • Individual: less streamlined.
  • Team workflows: built-in via GitHub.

Para enterprises con GitHub-centric workflow, Copilot Workspace makes sense. Para individuals, Cursor sigue mejor.

Evolution esperada

GitHub/Microsoft roadmap:

  • Agent mode: autonomous longer-running agents.
  • Custom models: enterprise bring-your-own-LLM.
  • Enhanced testing: more autonomous test generation.
  • Code review: AI reviewer with deeper analysis.

Direction is Copilot → more autonomous.

Security considerations

  • Code en Microsoft backend: enterprise agreements cover.
  • No training with enterprise code (per terms).
  • IP attribution: clear.
  • Audit logs: available enterprise tier.

Similar concerns a Copilot standard.

Limitations actuales

  • Preview: features changing.
  • Quality variance: sometimes perfect, sometimes off.
  • Slow: planning phase adds latency.
  • GitHub-only: no GitLab/Bitbucket equivalents.
  • English primarily: issues/PRs en otros languages limitados.

Para empezar

Requires:

  • GitHub Copilot subscription.
  • Waitlist access for Workspace preview.
  • Repository enrolled in feature.

Request access en GitHub.

Impact en workflow

Team adopting Copilot Workspace:

  • More PRs: AI generates proposals.
  • More review: human validates.
  • Issue quality matters more: vague issues → bad PRs.
  • Test coverage critical: tests as spec.

Changes incentives en direction útil.

Comparación con AI agents

Copilot Workspace es “agent” específico:

  • Goal: complete task from issue.
  • Tools: code edit, test, commit.
  • Feedback loop: test → iterate.
  • Scope: single PR typically.

Para multi-repo o cross-project, otras approaches.

Conclusión

Copilot Workspace es bet interesante de GitHub en task-first AI development. Para GitHub-centric teams, fit natural. Para individual productivity, Cursor probably más refined. Preview state significa evolution expected. La direction industry — AI doing more autonomously vs just completing inline — es clara. Workspace está posicionando GitHub/Microsoft para ese future. Worth evaluating si tienes Copilot Enterprise o estás in GitHub ecosystem.

Síguenos en jacar.es para más sobre AI coding, GitHub y development workflows.

Entradas relacionadas