Repository navigation
feat(code): discover workspace context and preserve concurrent file changes - #680
Open
blakebauman wants to merge 10 commits into
Open
blakebauman wants to merge 10 commits into
blakebauman wants to merge 10 commits into
Conversation
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.
local_infofor terminal and browser, and sharedlocal_instructionsdiscovery with traversal checks, ancestor ordering, bounded text, and explicit continuation offsets.local_edit; recheck after terminal confirmation and before committing a staged browser write.Validation
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
codeas 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
codeturns 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
/workopens 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
Fixed