Guide: Run Omni and Claude Engineer Inside Daytona Workspaces

[ESTEBANTRAN]

Writer's Checklist

Writing Structure

• Use short sentences and paragraphs, and include bucket brigades.
• Include more than two descriptive H2 headings to organize content (Why Devcontainers + Daytona, Step 1-5, Troubleshooting, Conclusion).
• Capitalize headings according to the AP Stylebook.
• Include an introduction with at least two paragraphs before the first H2 section.
• Use appropriate formatting (bold, italic), notes, TLDRs, and key points.
• Incorporate code elements and Markdown formatting throughout.
• Visual elements: code blocks, numbered walkthrough steps, tables-free but structured sections.

Fact-Checking

• Verified against actual repository contents of omni-engineer and claude-engineer (requirements.txt, .env.example, entry points).

Linked Issue

Closes #36

Summary

Step-by-step guide (~1600 words) covering:

1. devcontainer.json contributions for Doriandarko/omni-engineer (PR Building a Codespaces-like Experience with Daytona and GitLab #47) and Doriandarko/claude-engineer (PR Guide: AI Transcription Tool — Complete Guide with OpenAI, Groq, and Azure #273)
2. Workspace creation with daytona create
3. A real Omni Engineer session (file editing with diff/undo + web search)
4. Claude Engineer behind Flask in a workspace
5. Troubleshooting section

Includes new author profile authors/esteban_aulestia.md.