Papers › Generative Agents: Interactive Simulacra of Human Behavior

Generative Agents: Interactive Simulacra of Human Behavior

7 Apr 2023arXiv:2304.03442archive 2025-07-28

Joon Sung Park, Joseph C. O'Brien, Carrie J. Cai, Meredith Ringel Morris, Percy Liang, Michael S. Bernstein

Believable proxies of human behavior can empower interactive applications ranging from immersive environments to rehearsal spaces for interpersonal communication to prototyping tools. In this paper, we introduce generative agents--computational software agents that simulate believable human behavior. Generative agents wake up, cook breakfast, and head to work; artists paint, while authors write; they form opinions, notice each other, and initiate conversations; they remember and reflect on days past as they plan the next day. To enable generative agents, we describe an architecture that extends a large language model to store a complete record of the agent's experiences using natural language, synthesize those memories over time into higher-level reflections, and retrieve them dynamically to plan behavior. We instantiate generative agents to populate an interactive sandbox environment inspired by The Sims, where end users can interact with a small town of twenty five agents using natural language. In an evaluation, these generative agents produce believable individual and emergent social behaviors: for example, starting with only a single user-specified notion that one agent wants to throw a Valentine's Day party, the agents autonomously spread invitations to the party over the next two days, make new acquaintances, ask each other out on dates to the party, and coordinate to show up for the party together at the right time. We demonstrate through ablation that the components of our agent architecture--observation, planning, and reflection--each contribute critically to the believability of agent behavior. By fusing large language models with computational, interactive agents, this work introduces architectural and interaction patterns for enabling believable simulations of human behavior.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 12 code samples harvested from 4 repositories linked to this paper: 10 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 1 violated, 8 with no contract checked; 1 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 3 samples from 1 repository, 3 ran (2 with no instrument failure; 1 where Syntology's instrument failed); community (archive-listed): 9 samples from 3 repositories, 7 ran (7 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

joonspk-research/generative_agents officialmentioned in papermentioned on GitHubApache-2.0Syntology: 3 samples, 3 ran (1 instrument-failed) · 0 unverified report
ZhangYiqun018/StickerConv mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Visual Instruction Tuning (arXiv:2304.08485; that paper's own run record: 16 ran (of which 6 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 1 violated, 7 with no contract checked; 8 where Syntology's instrument failed) · 35 unverified); nothing checks that they implement this paper's method. report
a16z-infra/ai-town mentioned on GitHubMITSyntology: not harvested report
ejunprung/llm-agents mentioned on GitHubSyntology: not harvested report
jina-ai/thinkgpt mentioned on GitHubApache-2.0Syntology: 3 samples, 1 ran (0 instrument-failed) · 2 unverified report
litanlitudan/skyagi mentioned on GitHubApache-2.0Syntology: 3 samples, 3 ran (0 instrument-failed) · 0 unverified report
nickm980/smallville mentioned on GitHubMITSyntology: not harvested report
renmengjie7/aisimutoolkit mentioned on GitHubApache-2.0Syntology: 3 samples, 3 ran (0 instrument-failed) · 0 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

12 samples harvested: 10 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 1 violated, 8 with no contract checked; 1 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · violated contract
1ran · our draft was wrong
8ran
2unverified

Licence: 5 of the 12 samples are pointer only, meaning Syntology does not serve that copy's text. For 5 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 4 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

joonspk-research/generative_agents official repository 3 samples, 3 ran (1 instrument-failed) · 0 unverified
create_folder_if_not_there environment/frontend_server/global_methods.py ran · violated contract Apache-2.0 (permissive) here; the stored copy is pointer only · 04d3df25d420010e · report fixture: signature curr_path:str/0/str · returned bool · level recorded 2026-09-24
read_file_to_list in 5 papers environment/frontend_server/global_methods.py ran Apache-2.0 (permissive) here; the stored copy is pointer only · 48476b17bdfd0043 · report fixture: signature curr_file:str/0/str, header:bool/0/bool, strip_trail:bool/0/bool · returned list · level recorded 2026-09-24
read_file_to_set environment/frontend_server/global_methods.py ran · our draft was wrong Apache-2.0 (permissive) here; the stored copy is pointer only · 219bfa7864169c24 · report fixture: signature curr_file:str/0/str, col:int/0/int · returned set · level recorded 2026-09-24
jina-ai/thinkgpt community (archive-listed) 3 samples, 1 ran (0 instrument-failed) · 2 unverified
format_options in 5 papers thinkgpt/gpt_select.py ran Apache-2.0 (permissive) · d52b33b77d35e4ed · report fixture: signature options:list/1/str · returned str · level recorded 2026-09-24
fit_context thinkgpt/helper.py unverified Apache-2.0 (permissive) · ea817e6b698cf08e · report
get_n_tokens thinkgpt/helper.py unverified Apache-2.0 (permissive) · 4c2c52a526fb9a29 · report
litanlitudan/skyagi community (archive-listed) 3 samples, 3 ran (0 instrument-failed) · 0 unverified
relevance_score_fn skyagi/src/skyagi/simulation/simulation.py ran fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only · 545ba72b86f890f5 · report fixture: signature score:float/0/float · returned float · level recorded 2026-09-24
verify_openai_ skyagi/src/skyagi/util.py ran fingerprinted Apache-2.0 (permissive) · f1c5580780f0e534 · report fixture: signature token:str/0/str · returned str · level recorded 2026-09-24
verify_pinecone_token skyagi/src/skyagi/util.py ran fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only · 2d779390d2d954c2 · report fixture: signature token:str/0/str · returned str · level recorded 2026-09-24
renmengjie7/aisimutoolkit community (archive-listed) 3 samples, 3 ran (0 instrument-failed) · 0 unverified
get_file_stream AISimuToolKit/utils/utils.py ran Apache-2.0 (permissive) · 2793537d25115ebc · report fixture: signature file:str/0/str · returned BufferedReader · level recorded 2026-09-24
get_fromat_len AISimuToolKit/utils/utils.py ran fingerprinted Apache-2.0 (permissive) · 56a62d76a2e1fb94 · report fixture: signature num:int/0/int · returned int · level recorded 2026-09-25
parse_yaml_config AISimuToolKit/utils/utils.py ran Apache-2.0 (permissive) · ff183b964718e88e · report fixture: signature path:str/0/str · returned dict · level recorded 2026-09-24

Tasks

Language ModellingLarge Language Model

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections