{"version":"2.1.265","anchor":"artifact-result-text-can-be-returned-inline-instead-of-requi","canonical_anchor":"artifact-result-text-can-be-returned-inline-instead-of-requi","heading":"Artifact result text can be returned inline instead of requiring a Read, when multi-file mode is on","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/artifact-result-text-can-be-returned-inline-instead-of-requi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Artifact result text can be returned inline instead of requiring a Read, when multi-file mode is on\n\nSmall text files saved by Artifact tools can now return their contents inline, skipping a separate Read\n\n**What**\n\nWhen an Artifact tool saves output to a local file, its description now notes that for a small published text file, the file's contents come back directly in the tool's result data. This happens when `multiFileOn` is set, meaning a separate `Read` call to fetch the contents is no longer necessary. The same applies when reading a file's published path inside an artifact: the result now includes the small text file's contents directly rather than only its saved location.\n\n**Why**\n\nThis saves an extra step: instead of saving a file and then reading it back, small text output is available immediately in the same result.\n\n- Area: Artifacts\n- Names: `multiFileOn`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}