google-deepmind / google-deepmind/concordia
Consolidate visual editor, project authoring and attached CLI improvements
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 367
- PR merge metrics
- No merged PRs in 30d
Description
## Category consolidation
Requested by Joel Z. Leibo in [issue #373](https://github.com/google-deepmind/concordia/issues/373#issuecomment-5621250114). This is the single continuing issue for this category. Implementation and subsequent improvements stay in [PR #314](https://github.com/google-deepmind/concordia/pull/314). Approved PRs #297, #302, #304 and #332 are exempt and remain unchanged.
## Scope
- Preserve card/inspector identity and literal multiline component text.
- Keep lifecycle status, counters and controls authoritative across tabs and reconnects; return readable errors for rejected requests.
- Edit, save, reopen and explicitly run a supported initial project through the existing editor and a shared normalized Config.
- Discover/query/dispatch validated operations from the existing browser UI and `concordia-session`; retain revision checks, retry protection and scoped listeners.
- Reuse attached browser sessions, lazy received-snapshot inspection and coalesced SSE wakeups.
- Resolve the integration between project authoring and lifecycle controls: a fresh run discards the previous run's terminal state and controls before the next Simulation binds.
Bellwether-specific service handlers, fixtures and integration demonstrations belong to PR #372, not this category. This remains a bounded authoring/shared-operation foundation, not full checkpoint continuation, arbitrary project serialization, general component CRUD, or complete GUI/CLI parity.
## Consolidated review history
[#308](https://github.com/google-deepmind/concordia/pull/308), [#310](https://github.com/google-deepmind/concordia/pull/310), [#312](https://github.com/google-deepmind/concordia/pull/312), [#316](https://github.com/google-deepmind/concordia/pull/316), [#328](https://github.com/google-deepmind/concordia/pull/328), [#362](https://github.com/google-deepmind/concordia/pull/362), [#368](https://github.com/google-deepmind/concordia/pull/368)
Superseded issues and PRs retain their original descriptions and point here. Consolidation closes duplicate review threads, not claims that pending code has landed upstream.
## Follow-up improvements — 2026-09-13
Alice now uses the standard minimal prefab and Bob the standard basic prefab. Save/reopen retains Bob’s goal, and the real runtime inspector exposes his SelfPerception, SituationPerception and PersonBySituation components. New projects use conversation-v2; existing conversation-v1 documents retain their exact original two-minimal-actor configuration and saved instructions. The README explains document schema versus template revision.
[Follow-up commit](https://github.com/concordia-claw/concordia/commit/aae8251671a7dc7595787d29463905000e5b8f71) · [Combined validated checkout](https://github.com/concordia-claw/concordia/tree/5e672ab200be3d31ecc4f34d6165f6eab6f2514c).
Contributor guide
Research direction
Start by reviewing PR #314 and the consolidated review history, then compare the bounded scope with the follow-up commit and combined validated checkout linked in the issue. The work is done when the listed editor, project-authoring, lifecycle, browser UI, and concordia-session requirements are integrated without expanding into the explicitly excluded areas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 15/100