Projects, tasks, and skills
A project is the folder above your sites: the place where standing instructions, files, skills, schedules, and work all live together, so the assistant never has to be re-taught what it is working on.
What a project holds
A project holds instructions, files and sources, connector overrides, skills, scheduled tasks, sites, and tasks. Every existing site was wrapped in a project automatically, so nobody starts empty.
Instructions are how you want the assistant to work in that project, and they are injected into every turn that belongs to it, task runs and plain chats alike. Write them once and stop re-explaining the project at the top of every conversation.
Files and sources are pages, notes, and text files the project keeps in mind. A link is fetched and its text extracted once, when you add it. Connector overrides let one project run with different tool permissions than the rest of the workspace: turning something off here leaves it on everywhere else.
Skills: your own slash commands
A skill is a named, reusable instruction you run by typing /slug in the composer. Typing / alone opens a picker of the project's skills. Any recipe you find yourself repeating, a weekly report format, a post structure, a review checklist, is worth saving as one: ask the assistant to make a skill out of it, and the same request becomes one word.
Tasks and their statuses
Tasks are the unit of work, and each has an owner. An AI-owned task runs a chat thread; a human-owned task is a to-do you tick off. Status runs todo, running, needs_input, done, plus queued for a task waiting on the background runner and blocked for a run that errored.
needs_input is the status to watch. A run that ends on a question, or parks on a confirmation, lands there rather than in done: the assistant never claims a task finished when it is actually waiting on you. Click the task to open its thread and answer.
Foreground, background, and scheduled
Running a task in the foreground opens it in the editor and streams normally, and that is free on every plan, as are projects, instructions, sources, and skills themselves.
Background runs and schedules are Pro. A background task queues for a runner that drains every 15 minutes and works while you do something else. Background runs cannot ask questions and cannot use confirm-gated tools: anything that needs your yes is refused and reported back for you to approve, so nothing irreversible ever happens while you are not looking.
Archiving, not deleting
There is no Mark done button on the project page, because the page is folder management, not a task tracker. Archiving is how a finished conversation leaves the page: the task disappears from every list, the background runner skips it, and nothing is deleted. The thread it owns survives.
When it does not work
A task sits in needs_input: it asked you something. Open it and answer; it cannot finish without you.
A task shows blocked: the run errored. Open the thread to see what happened and ask the assistant to run it again.
A background run reported it could not do something: it hit a question or a confirmation it is not allowed to answer for you. Run the task in the foreground, or give the approval it asked for, and it completes.
A task vanished from the list: it was archived, not deleted. Its conversation still exists, and archiving is reversible in the sense that nothing was lost with it.
adlens (adlens Pro, at adlens.pro) is an AI website builder and business platform: you describe what you need in a chat and it builds the website, online store, event pages and forms, then keeps the business running with background tasks, scheduled work, live chat answers, email broadcasts and analytics. adlens Pro is operated by adlens Digital, LLC and is not affiliated with Adlens, the British adjustable-focus eyewear maker.