Resources and context overview

This article explains resources and context in Autify Genesis. Genesis runs tasks while referencing resources registered in a workspace. This article describes how registered resources are used.

Resources

Resources are information sources (such as code and documents) that the AI references when running tasks. They are managed centrally as a knowledge base in your workspace's Resources and Context tab.

Type	Description
Codebase	A GitHub repository or a ZIP file
Files	Files such as PRDs, specifications, and PDFs, as well as artifacts (outputs) generated by workflows

Using resources as context

Registered resources are used as context (background knowledge) when the AI runs tasks, in the following ways.

Resource search

The AI references codebases and text-based files registered in the workspace, and gathers the information it needs while running tasks.

Registered codebases and text-based files are indexed and stored in the knowledge base, so the AI uses file lookup and string search in combination with semantic search to retrieve relevant information.

What is semantic search?

Semantic search is a search method that finds related information based on context and semantic similarity, not just on the literal keywords. Even when expressions do not match exactly, it can surface code and files that are conceptually close.

For example, when you search for "I want to know the spec for the login feature," the AI can find not only places where the word login appears literally, but also specifications and implementations that contain conceptually related content such as sign-in, authentication, or user verification.

Specifying a file directly

You can also reference specific files directly by name. You can specify files from the AI Assistant chat or when running a workflow, and you can also reference a past version of a file by specifying its version.

Other context

In the Workflow feature, you can use the following information as context in addition to resources.

• Context variables — Text and number variables defined in the workflow definition.

• Output of upstream blocks — The processing results of upstream blocks within the workflow.

• Trigger information — Information provided when the workflow is triggered automatically, such as by a GitHub webhook.