Vibecode Aight

You are building a lean indie version of Aight.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# Aight indie build

## Goal

Build the smallest trustworthy replacement for the core Aight workflow for one developer or a tiny team.

## Scope

Build one SwiftUI client and a local adapter service that can start, resume, stream, interrupt, and approve work across Codex, Claude Code, OpenClaw, and Hermes.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- managed encrypted relay and push notifications
- voice mode with local speech models
- cross-agent teams and group-chat orchestration
- pre-built agent/team templates and community skill browsing
- multi-device sync and App Store polish

If those capabilities are essential, use Happy instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build me a local-first iPhone client for Codex, Claude Code, OpenClaw,
and Hermes. Requirements:

- Use Swift 6, SwiftUI, and iOS 18. Generate Xcode from a checked-in
  XcodeGen project.yml so `xcodegen && xcodebuild` works on a clean clone.
- Build the Node.js 22 TypeScript companion with Fastify and WebSockets. Expose
  start, resume, prompt, event, approval, interrupt, and capability operations;
  session listing is optional and capability-gated.
- Ship real adapters for all four. Disable unavailable agents at runtime; all
  adapters must compile and pass fixture tests without every agent installed.
- Codex: pin the CLI version, run `codex app-server generate-ts`, and supervise
  app-server over stdio using the generated v2 types.
- Claude Code: use `@anthropic-ai/claude-agent-sdk`, its session APIs,
  async-iterable input for interrupt(), and canUseTool for permissions.
- OpenClaw: use the official Gateway WebSocket client, pair once, request only
  read/write/approvals/questions scopes, and store its device token securely.
- Hermes: use /v1/runs and its event, approval, and stop endpoints; use
  session headers for continuity and discover features from /v1/capabilities.
- Keep backend models in the companion and expose one versioned protocol. The
  iOS app stores its wss:// endpoint and bridge bearer token in Keychain.
- Provide backend/session pickers, streamed Markdown and tool events, approval
  cards, Stop, capability-aware controls, and deny approvals on disconnect.
- Bind to 127.0.0.1 and compare the random `.env` token in constant time;
  expose it only through private Tailscale Serve HTTPS, and never enable Funnel.
- Add bounded reconnects and local completion notifications. No app accounts,
  cloud database, analytics, or telemetry; agent model-provider calls remain.
- Out of scope: hosted relay, voice, cross-backend groups, templates, community
  skills, themes, multi-device sync, and a macOS client.
- Test adapter fixtures plus denial, interruption, and reconnection. README:
  setup for all four, `.env.example`, Tailscale, signing, permissions, limits.

## Required capabilities

- Mac with Xcode
- iPhone running iOS 18
- Node.js 22
- at least one supported agent installed
- Apple ID for device signing
- credentials for each enabled agent
- Tailscale on both devices

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a lean indie version of Aight.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# Aight indie build

## Goal

Build the smallest trustworthy replacement for the core Aight workflow for one developer or a tiny team.

## Scope

Build one SwiftUI client and a local adapter service that can start, resume, stream, interrupt, and approve work across Codex, Claude Code, OpenClaw, and Hermes.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- managed encrypted relay and push notifications
- voice mode with local speech models
- cross-agent teams and group-chat orchestration
- pre-built agent/team templates and community skill browsing
- multi-device sync and App Store polish

If those capabilities are essential, use Happy instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build me a local-first iPhone client for Codex, Claude Code, OpenClaw,
and Hermes. Requirements:

- Use Swift 6, SwiftUI, and iOS 18. Generate Xcode from a checked-in
  XcodeGen project.yml so `xcodegen && xcodebuild` works on a clean clone.
- Build the Node.js 22 TypeScript companion with Fastify and WebSockets. Expose
  start, resume, prompt, event, approval, interrupt, and capability operations;
  session listing is optional and capability-gated.
- Ship real adapters for all four. Disable unavailable agents at runtime; all
  adapters must compile and pass fixture tests without every agent installed.
- Codex: pin the CLI version, run `codex app-server generate-ts`, and supervise
  app-server over stdio using the generated v2 types.
- Claude Code: use `@anthropic-ai/claude-agent-sdk`, its session APIs,
  async-iterable input for interrupt(), and canUseTool for permissions.
- OpenClaw: use the official Gateway WebSocket client, pair once, request only
  read/write/approvals/questions scopes, and store its device token securely.
- Hermes: use /v1/runs and its event, approval, and stop endpoints; use
  session headers for continuity and discover features from /v1/capabilities.
- Keep backend models in the companion and expose one versioned protocol. The
  iOS app stores its wss:// endpoint and bridge bearer token in Keychain.
- Provide backend/session pickers, streamed Markdown and tool events, approval
  cards, Stop, capability-aware controls, and deny approvals on disconnect.
- Bind to 127.0.0.1 and compare the random `.env` token in constant time;
  expose it only through private Tailscale Serve HTTPS, and never enable Funnel.
- Add bounded reconnects and local completion notifications. No app accounts,
  cloud database, analytics, or telemetry; agent model-provider calls remain.
- Out of scope: hosted relay, voice, cross-backend groups, templates, community
  skills, themes, multi-device sync, and a macOS client.
- Test adapter fixtures plus denial, interruption, and reconnection. README:
  setup for all four, `.env.example`, Tailscale, signing, permissions, limits.

## Required capabilities

- Mac with Xcode
- iPhone running iOS 18
- Node.js 22
- at least one supported agent installed
- Apple ID for device signing
- credentials for each enabled agent
- Tailscale on both devices

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a production product version of Aight.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== PRODUCT.md =====
# Aight product brief

## Problem

A focused multi-backend iPhone prototype is a realistic multi-day build when a local companion normalizes each agent protocol, but hardening all four adapters plus Aight's hosted relay, voice, orchestration, sync, and App Store polish is multi-week product work.

## Product outcome

Build one SwiftUI client and a local adapter service that can start, resume, stream, interrupt, and approve work across Codex, Claude Code, OpenClaw, and Hermes.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- Mac with Xcode
- iPhone running iOS 18
- Node.js 22
- at least one supported agent installed
- Apple ID for device signing
- credentials for each enabled agent
- Tailscale on both devices

## Explicit non-goals for v1

- managed encrypted relay and push notifications
- voice mode with local speech models
- cross-agent teams and group-chat orchestration
- pre-built agent/team templates and community skill browsing
- multi-device sync and App Store polish

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

===== ARCHITECTURE.md =====
# Architecture

## Starting brief

Build me a local-first iPhone client for Codex, Claude Code, OpenClaw,
and Hermes. Requirements:

- Use Swift 6, SwiftUI, and iOS 18. Generate Xcode from a checked-in
  XcodeGen project.yml so `xcodegen && xcodebuild` works on a clean clone.
- Build the Node.js 22 TypeScript companion with Fastify and WebSockets. Expose
  start, resume, prompt, event, approval, interrupt, and capability operations;
  session listing is optional and capability-gated.
- Ship real adapters for all four. Disable unavailable agents at runtime; all
  adapters must compile and pass fixture tests without every agent installed.
- Codex: pin the CLI version, run `codex app-server generate-ts`, and supervise
  app-server over stdio using the generated v2 types.
- Claude Code: use `@anthropic-ai/claude-agent-sdk`, its session APIs,
  async-iterable input for interrupt(), and canUseTool for permissions.
- OpenClaw: use the official Gateway WebSocket client, pair once, request only
  read/write/approvals/questions scopes, and store its device token securely.
- Hermes: use /v1/runs and its event, approval, and stop endpoints; use
  session headers for continuity and discover features from /v1/capabilities.
- Keep backend models in the companion and expose one versioned protocol. The
  iOS app stores its wss:// endpoint and bridge bearer token in Keychain.
- Provide backend/session pickers, streamed Markdown and tool events, approval
  cards, Stop, capability-aware controls, and deny approvals on disconnect.
- Bind to 127.0.0.1 and compare the random `.env` token in constant time;
  expose it only through private Tailscale Serve HTTPS, and never enable Funnel.
- Add bounded reconnects and local completion notifications. No app accounts,
  cloud database, analytics, or telemetry; agent model-provider calls remain.
- Out of scope: hosted relay, voice, cross-backend groups, templates, community
  skills, themes, multi-device sync, and a macOS client.
- Test adapter fixtures plus denial, interruption, and reconnection. README:
  setup for all four, `.env.example`, Tailscale, signing, permissions, limits.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

===== AGENTS.md =====
# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

===== MILESTONES.md =====
# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

===== OPERATIONS.md =====
# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted Aight capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

# Aight indie build

## Goal

Build the smallest trustworthy replacement for the core Aight workflow for one developer or a tiny team.

## Scope

Build one SwiftUI client and a local adapter service that can start, resume, stream, interrupt, and approve work across Codex, Claude Code, OpenClaw, and Hermes.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- managed encrypted relay and push notifications
- voice mode with local speech models
- cross-agent teams and group-chat orchestration
- pre-built agent/team templates and community skill browsing
- multi-device sync and App Store polish

If those capabilities are essential, use Happy instead of pretending the gap is solved.

# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

# Build plan

## Original build brief

Build me a local-first iPhone client for Codex, Claude Code, OpenClaw,
and Hermes. Requirements:

- Use Swift 6, SwiftUI, and iOS 18. Generate Xcode from a checked-in
  XcodeGen project.yml so `xcodegen && xcodebuild` works on a clean clone.
- Build the Node.js 22 TypeScript companion with Fastify and WebSockets. Expose
  start, resume, prompt, event, approval, interrupt, and capability operations;
  session listing is optional and capability-gated.
- Ship real adapters for all four. Disable unavailable agents at runtime; all
  adapters must compile and pass fixture tests without every agent installed.
- Codex: pin the CLI version, run `codex app-server generate-ts`, and supervise
  app-server over stdio using the generated v2 types.
- Claude Code: use `@anthropic-ai/claude-agent-sdk`, its session APIs,
  async-iterable input for interrupt(), and canUseTool for permissions.
- OpenClaw: use the official Gateway WebSocket client, pair once, request only
  read/write/approvals/questions scopes, and store its device token securely.
- Hermes: use /v1/runs and its event, approval, and stop endpoints; use
  session headers for continuity and discover features from /v1/capabilities.
- Keep backend models in the companion and expose one versioned protocol. The
  iOS app stores its wss:// endpoint and bridge bearer token in Keychain.
- Provide backend/session pickers, streamed Markdown and tool events, approval
  cards, Stop, capability-aware controls, and deny approvals on disconnect.
- Bind to 127.0.0.1 and compare the random `.env` token in constant time;
  expose it only through private Tailscale Serve HTTPS, and never enable Funnel.
- Add bounded reconnects and local completion notifications. No app accounts,
  cloud database, analytics, or telemetry; agent model-provider calls remain.
- Out of scope: hosted relay, voice, cross-backend groups, templates, community
  skills, themes, multi-device sync, and a macOS client.
- Test adapter fixtures plus denial, interruption, and reconnection. README:
  setup for all four, `.env.example`, Tailscale, signing, permissions, limits.

## Required capabilities

- Mac with Xcode
- iPhone running iOS 18
- Node.js 22
- at least one supported agent installed
- Apple ID for device signing
- credentials for each enabled agent
- Tailscale on both devices

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

# Aight product brief

## Problem

A focused multi-backend iPhone prototype is a realistic multi-day build when a local companion normalizes each agent protocol, but hardening all four adapters plus Aight's hosted relay, voice, orchestration, sync, and App Store polish is multi-week product work.

## Product outcome

Build one SwiftUI client and a local adapter service that can start, resume, stream, interrupt, and approve work across Codex, Claude Code, OpenClaw, and Hermes.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- Mac with Xcode
- iPhone running iOS 18
- Node.js 22
- at least one supported agent installed
- Apple ID for device signing
- credentials for each enabled agent
- Tailscale on both devices

## Explicit non-goals for v1

- managed encrypted relay and push notifications
- voice mode with local speech models
- cross-agent teams and group-chat orchestration
- pre-built agent/team templates and community skill browsing
- multi-device sync and App Store polish

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

# Architecture

## Starting brief

Build me a local-first iPhone client for Codex, Claude Code, OpenClaw,
and Hermes. Requirements:

- Use Swift 6, SwiftUI, and iOS 18. Generate Xcode from a checked-in
  XcodeGen project.yml so `xcodegen && xcodebuild` works on a clean clone.
- Build the Node.js 22 TypeScript companion with Fastify and WebSockets. Expose
  start, resume, prompt, event, approval, interrupt, and capability operations;
  session listing is optional and capability-gated.
- Ship real adapters for all four. Disable unavailable agents at runtime; all
  adapters must compile and pass fixture tests without every agent installed.
- Codex: pin the CLI version, run `codex app-server generate-ts`, and supervise
  app-server over stdio using the generated v2 types.
- Claude Code: use `@anthropic-ai/claude-agent-sdk`, its session APIs,
  async-iterable input for interrupt(), and canUseTool for permissions.
- OpenClaw: use the official Gateway WebSocket client, pair once, request only
  read/write/approvals/questions scopes, and store its device token securely.
- Hermes: use /v1/runs and its event, approval, and stop endpoints; use
  session headers for continuity and discover features from /v1/capabilities.
- Keep backend models in the companion and expose one versioned protocol. The
  iOS app stores its wss:// endpoint and bridge bearer token in Keychain.
- Provide backend/session pickers, streamed Markdown and tool events, approval
  cards, Stop, capability-aware controls, and deny approvals on disconnect.
- Bind to 127.0.0.1 and compare the random `.env` token in constant time;
  expose it only through private Tailscale Serve HTTPS, and never enable Funnel.
- Add bounded reconnects and local completion notifications. No app accounts,
  cloud database, analytics, or telemetry; agent model-provider calls remain.
- Out of scope: hosted relay, voice, cross-backend groups, templates, community
  skills, themes, multi-device sync, and a macOS client.
- Test adapter fixtures plus denial, interruption, and reconnection. README:
  setup for all four, `.env.example`, Tailscale, signing, permissions, limits.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted Aight capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

$ choose a build depth, inspect the files, then open the complete pack in your agent