Your profile and everything around it

Skills, MCP servers, marketing channels, OKRs, API keys, plans and support tickets — everything that lives under your Quodara profile.

These modules make the agent understand you better and save you repeating yourself. This page walks the feature list in order.

Where the profile is

Click the button with your name at the bottom of the sidebar, or open Me directly. The page has three parts:

Basics — avatar, user ID, display name, interface theme (warm or dark), active subscriptions, and the usage gauges beside them
Feature list — Apps, Works, Cloud drive, Marketing channels, Support tickets, My skills, My MCP servers, OKR, To-dos, API keys, Purchases, Changelog
Asset library — a group of its own, alongside the feature list; for now it holds the voice library

The sidebar itself keeps only four high-traffic entries — new chat, Explore, Schedule and Shop — everything else is reached from here.

Works

Entry: Works

Animated comics, AI short dramas and sticker packs run across many sessions and pile up a lot of assets, so they do not live loose inside a chat. Each one gets a work container: character sheets, episode structure, and every panel's artwork and voice-over hang off it. Pick it up in a different chat and the agent still works from the same settings, so this episode still looks like the last one.

See 13-works.md for how that is done.

Cloud drive

Entry: Cloud drive

Every file you have uploaded or generated across all your chats is collected here, newest first, regardless of type. The point is simple: when you want the image you made three weeks ago, you do not have to find that chat again.

Images and video preview in place; everything else is offered as a download
It reads an index, so it will not resurrect files from chats you have deleted
The output list at the bottom of a chat covers that one conversation; the cloud drive is the ledger across all of them

Asset library

The asset library sits alongside the feature list. It holds material you pick from while creating, rather than things you own. Right now it has one card:

Voice library — every voice the platform can use, each one playable. The large number on each card is its code: remember it and say "use voice 318" back in the chat. See 14-voice.md.

My skills

Entry: My skills

A skill is a capability pack for the agent: a document describing how to handle a class of task, plus optional scripts and reference files. Once installed, the agent follows it automatically when a matching task comes up.

Three ways to add one: import from GitHub, upload a SKILL.md, or upload a packaged zip.

My MCP servers

Entry: My MCP servers

MCP servers are external tool services the agent can call. Paste an mcpServers config, optionally alongside Python scripts.

Prefer a skill when you have the choice. A skill is only read when it is relevant, while an MCP server's tool definitions cost context on every single turn. Unless the capability is a sentence or two and needed everywhere, package it as a skill.

These two pages are for when you already have the files. You can also install, create and edit them without leaving a chat — paste a link and say "install this", or just describe what you want. See 12-skills-mcp.md.

Marketing channels

Entry: Marketing channels

Fill this in before asking for marketing content, and the agent will write to it instead of asking you the same questions every time. Two layers:

Shared profile — what you do, who you want to reach, what readers should do next, industry, voice, brand avatar. Filled once, used everywhere.
Per-platform profiles — one row per platform: handle, follower range, posting cadence, the formats that account actually publishes.

Available platforms include X (Twitter), LinkedIn, Instagram, TikTok, YouTube, Reddit, Substack, Facebook, Threads and Pinterest. Each shows a status — Not filled in, Incomplete or Ready for planning — and for a platform you have not filled in, the agent will not invent an account background.

The full field list, what the agent can produce from it, and the compliance rules applied to finished copy are in 07-marketing.md.

OKR and to-dos

Entries: OKR, To-dos

OKR holds the goals and key results you set for yourself; the agent takes them into account when deciding what matters most
To-dos is a plain checklist; the agent appends loose ends it finds while working, and you can add your own

Both can stay empty at first. Fill them in when you want the agent to plan more proactively.

API keys

Entry: API keys

Holds the tokens used to call the Quodara API. Do not paste one into a chat tool or a screenshot; if a key leaks, regenerate it here.

Store, redeem codes and purchases

Entries: Store, Purchases

The store lists the available plans, which set your app limit, chat quota and tool usage quota
Checkout is handled by a hosted payment page; once payment clears, a redeem code is emailed to you
Every plan card has a Redeem code button — enter the 32-character code and the order is created and activated automatically
Active plans show up under "Active subscriptions" on your profile, next to the usage gauge
Purchases lists order number, item, amount, type, status and expiry. There is no refund button on this page — use a support ticket for refunds.

How the quota works

Your plan carries one weekly usage quota, and everything draws on it:

Covers	How it is measured	When it comes back
Talking to the agent (writing code, changing your app, producing documents) as well as generating and editing images, reading images, music, video, voice-over and transcription	Actual usage, per calendar week, Monday 00:00 through Sunday 23:59 UTC	Resets at Monday 00:00 UTC

A few things worth knowing:

The quota is the full week every week — it is not pro-rated. Subscribe on a Wednesday and you still get the whole week.
The gauge on the right of your profile is a single "Usage this week" card showing the percentage used so far.
Different work costs very different amounts: video uses the most, images come next, and an ordinary chat far less — so counting "how many times" tells you little. To stretch the budget, let the agent draft first and only re-render the approved version at full quality — that is its default behaviour, and you can always just say "show me a rough version first".
When the weekly quota runs out the agent tells you plainly and says when it resets, rather than retrying.

Support tickets

Entry: Support tickets

Open a ticket to reach a human, and track everything you have filed below. The Support ticket button in a chat header carries that conversation along as context, which makes debugging much faster.

Open a ticket for: suspected platform outages, data anomalies, refunds and invoices, quota increases, and business enquiries.

Changelog

The last entry in the profile feature list, or /changelog.html directly. Every platform update in reverse chronological order, readable without signing in.