This guide explains how to run and use the current Tilo Console.
本文档说明如何启动和使用当前版本的 Tilo Console。
git clone https://github.com/adam2go/tilo-framework.git
cd tilo-framework
cp .env.example .env
docker compose up --buildOpen:
http://localhost:3000
Backend health check:
curl http://localhost:8000/api/healthThe current Console has three main areas:
当前 Console 主要分为三个区域:
Left : Agent Task input and demo prompts
Center : Generated Artifact result
Right : Context panel: Trace / Memory / Skills / Files + Inbox
Use this panel to send a task to the agent.
左侧用于输入任务或点击内置 Demo。
You can:
- click a demo prompt
- edit the prompt manually
- click
Send Message
This is where Tilo renders the final result.
中间区域是结果交付区,也就是 Tilo 的 Artifact 页面。
Depending on the prompt, it may render:
- contract review artifact
- dashboard artifact
- competitive analysis table
- document artifact
The right panel helps you understand and control the run.
右侧区域用于理解和控制 Agent 运行过程。
Tabs:
Trace: visible execution stepsMemory: confirmed memories and memory candidatesSkills: skills and skill candidatesFiles: reserved for future file-backed runs
The Inbox section shows pending human decisions.
Try this prompt:
Review this contract and flag risky clauses around liability, termination, and payment terms.
Click Send Message.
Expected result:
- Tilo creates a Task.
- Tilo creates a Run.
- Tilo recalls memory.
- Tilo selects skills.
- Tilo generates an artifact.
- Tilo creates confirmations if needed.
- Tilo creates memory candidates.
- The UI shows artifact, trace, inbox, and memory.
Open the Memory tab in the right panel.
You may see memory candidates.
Click Confirm to turn a candidate into confirmed long-term memory.
Why this matters:
- Candidate memory is not trusted by default.
- Confirmed memory can be recalled in future tasks.
- This is how Tilo starts to become personalized and project-aware.
The Inbox section shows pending decisions.
Click Approve to approve a confirmation.
Examples:
- approve a high-risk contract revision suggestion
- approve a recommended follow-up action
- approve a tool action in future versions
Tilo's philosophy is: agents execute, humans decide.
Review this contract and flag risky clauses around liability, termination, and payment terms.
Expected output:
- contract review artifact
- risk items
- suggested revisions
- confirmation action
Which customers should sales follow up with this week?
Expected output:
- dashboard artifact
- follow-up recommendations
- confirmation items
Create a competitive analysis for memory-native AI agent frameworks.
Expected output:
- comparison table
- structured insight artifact
- memory candidate
Tilo is still early.
Current limitations:
- UI is functional but not polished.
- Demo data is partly mocked.
- File upload is not fully implemented.
- Browser/MCP/real external tools are not production-ready yet.
- Memory recall is still evolving.
- Artifact pages are early but already schema-driven.
For framework maturity, the next improvements should be:
- Keep app scaffolding and validation deterministic.
- Add stronger contract tests for new runtime actions.
- Improve artifact editing/versioning without moving action semantics into the frontend.
- Expand example fixtures only when they exercise reusable runtime contracts.
- Capture real screenshots from the running
/demoonly.
Do not use Tilo like a normal chatbot.
不要把 Tilo 当成普通聊天机器人。
Use it like this:
I give a goal.
Tilo creates a task.
The agent runs.
The result becomes an artifact.
I approve key decisions.
Useful context becomes memory.
Next time, Tilo works better.
This is the key product loop.