Skip to content

feat(code): discover workspace context and preserve concurrent file changes - #680

Open
blakebauman wants to merge 10 commits into
mainfrom
feat/code-workflow
Open

blakebauman wants to merge 10 commits into
mainfrom
feat/code-workflow

Conversation

@blakebauman

@blakebauman blakebauman commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Summary

The coding agent can now discover whether its client supports real commands and read the repository instructions applicable to a target file. File operations also detect common concurrent changes instead of silently overwriting or removing newer work.

  • Implement local_info for terminal and browser, and shared local_instructions discovery with traversal checks, ancestor ordering, bounded text, and explicit continuation offsets.
  • Pass original content through local_edit; recheck after terminal confirmation and before committing a staged browser write.
  • Recheck terminal delete/rename sources and create rename destinations exclusively. Browser rename retains a source changed during copying.
  • Document behavior, compatibility, and recovery from partial moves.

Validation

Shared client: 460 passed
Browser filesystem: 215 passed
Full TUI: 396 pass, 0 fail
Web chat: 1659 passed
Repository-wide type checks: 10 successful, 10 total
Protocol parity, API drift, payload shape checks: passed
Web and TUI builds: passed
Web first load: 448.4 kB gzipped / 450 kB budget
Biome and git diff whitespace checks: passed
Real harness/API/durable-worker/TUI smoke: passed, 4 scripted model calls, 0 vendor calls

Limits and rollout

These are optimistic filesystem checks, not locks against other programs. Terminal rename requires hard links and refuses cross-filesystem moves; failure after destination creation may leave both names. Browser rename remains a non-atomic copy/delete operation, and destination creation is constrained by the browser filesystem API.

Harness companion: felix-run/felix#776

The harness companion versions code as 1.1.0 and binds the new tools. Deploy this client first; the manifest includes fallback guidance for older clients. No production deployment was performed.

Release scope

Keep the coding manifest, persisted plans, workspace capabilities/instructions, concurrent-change protections, and TUI results summary in the same release. Finish the coding feature work before rollout; an intermediate production deployment is not a prerequisite for further implementation. Companion-first deployment order, if needed, is within that shared release window. No staging environment is assumed.

Coding results summary

Completed code turns now show observed file operations, completed commands, issues, unconfirmed operations, and remaining plan steps. The summary never infers passing tests from model prose, keeps failed retries visible, and does not count pending approvals or missing results as completed work. Other agents retain their existing layout.

Validation of the summary-only changes in an isolated checkout: 405 TUI tests passed, type checks and build passed. The real API/durable-worker/TUI smoke passed with coding_summary_verified: true, four scripted calls and zero vendor calls. Concurrent UI and sandbox changes in the shared checkout were excluded from this update.

Cross-turn coding report

/work opens a read-only report from loaded thread history in the existing pager. It combines recorded file operations and command attempts across continuation turns, keeps failed attempts visible after retries, and shows unfinished steps from each plan's latest observed state. It does not infer checks from model prose or fetch a live Git diff. The command makes no model call and changes no project files; the pager uses a private temporary report file. Large sections are bounded with an explicit remainder count, and control bytes in labels are neutralized.

The isolated follow-up passed 410 TUI tests, type checks and build. The real API/durable-worker/TUI smoke passed with coding_work_report_verified: true, four scripted model calls, zero vendor calls, and a clean exit. This remains part of the same coding release and the same two PRs.

Changelog

Added

  • Read-only workspace capability reporting and scoped repository instruction discovery for the coding agent.

Fixed

  • Preserve newer work when edits conflict, delete/rename sources change during confirmation, or a rename destination appears during terminal approval.

Rename apps/chat-ui to apps/web and @felix/chat-ui to @felix/web. Update workspace scripts, CI, tooling, docs, and the terminal secrets lookup. Group app setup, API code, styles, and feature logic into dedicated folders. Keep the deployed Cloudflare Worker name.

Validation: web production build and 1,676 tests pass; Tailwind, API drift, protocol parity, payload shapes, palette, and bundle budget checks pass.
Keep AppShell focused on layout, extract the header and conversation controller, and move preferences, manifests, thread indexing, workspace panes, approvals, notifications, clocks, recovery, and side questions into focused hooks. Normalize shared hook filenames to kebab-case. Keep tab-level state mounted above the route outlet.

Validation: all 1,676 web tests pass; production build, app-file Biome checks, Tailwind, and bundle budget checks pass. TypeScript also passes on the isolated commit contents. Existing workspace, sandbox, and terminal edits remain uncommitted.
…de-workflow

# Conflicts:
#	apps/web/tests/github-login.test.tsx

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant