Ysaya

Support

Technical support with context and follow-up.

Describe the issue once and keep every response, adjustment and agreement in the portal until it is resolved.

Featured guide · Requiry + AI

Turn your conversations into actionable requirements.

Connect a local Codex or Claude Code project to your workspace. No plugin is required: your assistant uses Requiry's API with a token you control.

Open my workspaces

Connect in four steps

  1. Create a local folder

    Create a folder such as Requiry-AI on your computer, before generating the token. Use a private folder, not one shared with other people.

  2. Open it in Codex or Claude Code

    Open that folder as a local project in Codex or Claude Code. Use an application with local file and HTTP access, not a web chat without those capabilities.

  3. Save the connection into that folder

    Sign in to Requiry, open Workspaces and select Connect with SI on your workspace. Give the token a name, such as Codex or Claude, choose its permissions and expiration, then select Generate and save .env. Most browsers ask where to save it: choose the folder you just created, so there is nothing to move afterwards. If yours saves straight to Downloads, move the file into that folder. Keep the suggested name or rename it .env, but never overwrite an existing .env. Use a separate token for each application.

  4. Ask your assistant to connect

    Paste the first prompt below into your local project. The assistant must read the connection instructions and check its access before making changes. If the address contains localhost, run the assistant on the same computer as Requiry.

Your first connection prompt

Use the Requiry connection .env file in this local folder. Read its instructions without printing the token. Load YSAYA_AGENT_CONTEXT_URL and verify access to YSAYA_WORKSPACE_ID with an authenticated GET using YSAYA_AGENT_API_BASE_URL and YSAYA_AGENT_TOKEN. Use direct HTTP requests, not a browser session or computer control. Tell me which workspace you can access and which operations are allowed. Do not change anything yet. Never send the token to another service. If access is denied, explain the API response instead of trying to bypass it.

What can you ask for next?

The assistant must respect the token's scope, your permissions and each requirement's current state. Ask it to confirm the proposed changes before writing.

Create and assign from a conversation

From our current conversation, propose requirements for the connected Requiry workspace. Include a title, objective, project, tasks and suggested assignees. Read existing requirements and workspace members to avoid duplicates and validate assignees. Do not invent people or target dates; ask about missing or ambiguous information. Show me the proposal and, after I confirm it, create the requirements and assign them within my permissions.

Improve a requirement

Read REQ-0001 in the connected workspace. Propose a clearer objective, acceptance criteria, tasks and risks based on the current conversation. Preserve existing information and show me the changes before applying them. If the requirement is archived or I cannot edit it, explain the restriction.

Summarize the team's work

Review the requirements I can access in the connected workspace. Summarize them by project and status, identify overdue items and summarize recorded time and pending tasks. Separate observed data from your recommendations and do not modify anything.

Account access

If you forgot your password, use account recovery from the sign-in page or ask an administrator for a single-use link.

Operational issues

Include the step where the issue occurs, the expected result and the message shown on screen.

Traceable follow-up

Your request becomes a requirement so you can talk to support and keep a record of its resolution.

Support channel

Create a request from your account.

The ticket will stay in your workspace and you can open it from the requirements list.