mirror of https://github.com/NeuralNomadsAI/CodeNomad.git synced 2026-08-29 18:22:07 +00:00

feat(automation): add guided desktop developer runs

Add Developer Automation to Advanced Settings for Electron and Windows Tauri. Each run uses an isolated profile and automatic loopback CDP port, reports bounded launch logs and target metadata, and is stopped with its full process tree during explicit stop or host shutdown.

Expose inspect, act, screenshot, and restart feedback to CodeNomad-owned OpenCode sessions through a token-authenticated loopback automation adapter. Session ownership, exact CDP target identity, navigation-safe accessibility refs, bounded diagnostics, and screenshot limits prevent cross-session or stale-target control.

Keep autonomous browser previews out of DEV-v2: no browser controller, child webview, browser IPC, browser permissions, or codenomad.browser tool is included. Cover the native protocol, launch managers, CDP lifecycle, adapter authentication, ownership fencing, UI integration, and cross-platform launch arguments with focused tests.

2026-08-29 09:50:34 +02:00

3 KiB

Raw Blame History

Documentation Index

Quick reference to all documentation files.

Main Documents

README.md

Project overview, installation, and getting started guide.

SUMMARY.md

Executive summary of the entire project - start here!

MVP-PRINCIPLES.md

MVP development philosophy - Focus on functionality, NOT performance ⚡

DESKTOP_V2_COMPARISON.md

Incremental comparison with official OpenCode Desktop V2, including parity, closed defects, remaining correctness work, runtime upgrade scope, and optional feature gaps.

DEV_V2_CODE_REDUCTION.md

Measured DEV-v2 growth analysis, maintainer position on test volume, ranked reduction candidates, and guardrails for later simplification without product regressions.

DEVELOPER_AUTOMATION.md

Isolated Electron/Tauri developer runs, CDP feedback tools, lifecycle guarantees, and trust boundaries.

Specification Documents

architecture.md

Complete system architecture

Component layers and responsibilities
State management structure
Data flow diagrams
Technology stack
Security and performance considerations

Read this to understand: How the app is structured

user-interface.md

Complete UI/UX specifications

Every screen and component layout
Visual design specifications
Interaction patterns
Accessibility requirements
Color schemes and typography

Read this to understand: What the app looks like and how users interact

technical-implementation.md

Implementation details

File structure
TypeScript interfaces
Shared OpenCode service and location ownership
Native @opencode-ai/client integration
IPC communication
Error handling strategies

Read this to understand: Current implementation boundaries

Reading Order

For First-Time Readers:

SUMMARY.md - Get the big picture
architecture.md - Understand the structure
user-interface.md - See what you're building

For Implementers:

technical-implementation.md - Implementation patterns
Refer to architecture.md and user-interface.md as needed

For Designers:

user-interface.md - Complete UI specs
architecture.md - Component structure
SUMMARY.md - Feature overview

Quick Reference

Common Questions

Q: Where do I start?
A: Read SUMMARY.md, then architecture.md and technical-implementation.md.

Q: What does the UI look like?
A: See user-interface.md for complete specifications

Q: How does it work internally?
A: See architecture.md for system design

Q: How do I build feature X?
A: See technical-implementation.md for patterns

3 KiB Raw Blame History