There's a slate for that.
Build your tools. Get things done.
AGENT
CONNECTORS
slate. /sleɪt/. a new thing, built for the agent-first world.
it's part tool, part interface, part app, part agent. it's all of those things into one. it's filled with possibilities. it's fast to make and use. it's connected to all of your existing tools. it's secure and can be governed. you can share slates, with your team or publicly. you can use other people's slates. you can remix slates, you can fork slates. they come built-in with databases, folders, triggers, and more.
any problem. any workflow. anything you want to solve.
make a slate for it.
Tools that fit your workflows
Software built for everyone fits no one exactly. Or it's riddled with configuration. A slate is shaped to how you work with all the noise stripped away. When the work changes, the slate changes.
Agents build it with you.
Agents work alongside you.
Any agent can write the whole slate for you and adapt it to your needs. Then the same agents can work alongside you using the same tools and data. Slates will even run agents on a schedule or on triggers, keeping the slate up-to-date.
Works with your agent
It's just code, and you own it
Every slate is just a git folder of React and TypeScript. Read it, review it, change it, keep it — there's no magic. Well, there's some magic.
Connected to everything you already use.
Gmail, Office, Teams, Salesforce, and 1,400+ more: a slate can read and write them, through a shared connected account or each viewer's own, with permissions and authentication handled by the platform.
1,400+ connectors
Slates are meant to be shared
Share a slate with your team, or with anyone else. Everyone signs in as themselves, they can use shared accounts, or it can use their accounts, or you can mix and match.
Share
Send it to your team, or publish it for anyone. Nothing is shared until you say so.
Use
Open someone else's slate and sign in. It runs on your inbox and your calendar, not theirs.
Work together
The whole team in one slate, on the same records. What one person changes, everyone sees.
Slates are meant to be remixed
Start from someone else's slate and have your agent make it yours. Your version keeps getting the original's improvements.
Fork it
Copy any slate into your own repo. It's yours to run, change, and share.
Remix it
Tell your agent what to change: a new screen, another tool, your own rules.
Keep improvements
When the original gets better, your agent merges the update in and keeps your changes.
Focus on the problem, not the plumbing.
We wired up all the necessary bits so that you can focus on the important bits.
React app
Your agent writes ordinary React. Push to main and it's live at its own address.
MCP tools
The tools your slate defines, callable from Claude or any MCP client, signed in as you.
MCP UI
Give a tool its own screen, written in React and shown right in the conversation.
Connectors
Gmail, Slack, and 1,400+ more, on a shared account or each viewer's own.
Sign-in and members
Your team signs in with your organization. Each member uses their own accounts.
Database
Declare one and it's there, for the slate or for each person. Tables in plain SQL.
Agents
Describe a task in a few files. An agent runs it in a sandbox and returns the result.
Scheduled agents
Runs on its own with no one watching, and leaves its result in the slate.
Agents API
Post a prompt to any agent over HTTP and get a job back; read its result when it's done.
Folders
Files that belong to the slate, which your screens and agents read and write.
Workflows
Several steps and several agents in one run. Coming soon.
Triggers & cron
Start an agent when something happens, or on a schedule written as a cron line.
Open source. Self-hostable.
Every line of ContextLayer is on GitHub. Read it, fork it, and use it for free.
- Project
- ContextLayer
Any problem. Any workflow.
Make a slate for it.
- Drawn by
- Your coding agent
- Scale
- 1:1
- Rev
- A
- Page
- 12 / 12