Every time you start a monthly report, launch a campaign, or run a planning cycle, you may find yourself rebuilding context from scratch; explaining what you need, which agents to use, what format the output should take, and how all the pieces fit together.
Projects help solve this problem by capturing the living, evolving work you're doing right now and making it reusable. Instead of recreating your workflow every time, you build it once by chatting with elvex, and then trigger it by name whenever you need it again.
The Problem
Without projects, your most valuable workflows are invisible to elvex unless you build an agent. You might have a monthly update that requires:
Pulling financial data from your accounting system
Generating performance charts
Drafting narrative sections with a specific tone
Formatting everything into a branded template
Coordinating inputs from three different agents
Why This Matters
You may have multiple agents that are honed to accomplish different parts of the report. Or additional instructions that may not feel like they fit the mold of an agent.
Projects turn your workflows into something reusable. Once a project exists, a few words is all it takes to kick the whole thing off again. The real payoff comes on the second run, and the third, and the tenth, when what used to take an hour of hopping around, it now takes seconds.
Where Projects Fit
elvex maintains three types of context:
Personal context captures who you are—your role, responsibilities, goals, and working style. This stays consistent across your work.
Company context captures how the organization operates—terminology, processes, stakeholders, and standards. This is shared across your organization.
Projects capture what you're working on right now—a campaign launch, a quarterly planning cycle, a monthly investor update. This is specific to a particular initiative or recurring function.
Together, these three layers mean elvex understands not just what you're asking for in this conversation, but the broader context of your work, your organization, and your current projects.
How It Works
Projects capture three things: what you're working on, which agents are involved, and what outputs you need.
You build a project by chatting with elvex:
Attach a reference document that shows the format or structure you want
Describe the agents involved and what each one should do
Explain the outputs you need and how they should be structured
elvex generates the project context for you. From then on, it knows which agents to use, what to produce, and how to structure the result.
Practical Implications
Coordinated Workflows
Most of your work involves multiple stops: different tools, documents, agents, and handoffs. Projects handle that complexity by combining multiple specialized agents into a single coordinated workflow.
Instead of managing five separate conversations across five different tools, a project wires them together under shared context. The right agents fire at the right time, with the right inputs, without you having to orchestrate every step manually.
Evolving Over Time
Projects aren't static. As your work evolves, your project context evolves with it. Trigger a project by name to run the workflow, update it as requirements change, or refine it as you discover better approaches.
Common Questions
How is project context different from just saving a conversation?
A saved conversation is a record of what happened. Project context is a reusable workflow. It captures the pattern—which agents to use, what inputs they need, what outputs to produce—so you can run it again with new data, updated requirements, or different parameters.
When should I create a project instead of just chatting with an agent?
Create a project when you have a workflow you'll run more than once, especially if it involves multiple agents or complex coordination. One-off requests don't need projects. Recurring workflows, multi-step processes, and team-shared procedures do.
Can I have multiple projects active at the same time?
Yes. You might have a project for your monthly investor update, another for quarterly planning, and a third for campaign launches. Each project maintains its own context and can be triggered independently.
What happens if my workflow changes?
Update the project context by chatting with elvex about what's changed. The project evolves with your work, so you're always running the current version of your workflow, not a stale snapshot from six months ago.
What's Next
Ready to create your first project? Start by identifying a workflow you run regularly—something that involves multiple steps, specific outputs, or coordination between different agents. Then chat with elvex about what you're trying to accomplish, and let it build the project context for you.